I don't mean to object to the reg-required plugin you are working on.
But I would draw a line between
plugin author and reg-required-entity are the same thing - not really ok
plugin author and reg-required-entity are distinct - ok
I don't see that can work. So the mere fact of subcontracting the
development of your plugin would make it suddenly OK.
And I don't think that's desirable either. We mostly need better tagging
to potentially help filtering things in the UI.
By the way we'd probably need some sort of geography base tagging. A
number of plugins are specific to users of a given country typically.
So, when applicable:
country=comma-separed list of 2-letter country ISO 3166 A-2 code
(https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes)
Ex: country=fr,be
and also:
language=comma-separted list of local names (as in
https://doc.qt.io/qt-5/qlocale.html#uiLanguages)
Ex: language=en-US,fr-FR
--
http://www.spatialys.com
My software is free, but my time generally not.
Butcher of all kinds of standards, open or closed formats. At the end, this is
just about bytes.
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer