On 12/19/2016 03:04 PM, Luigi Pirelli wrote: > I also agree, pragmatic solution 1) leave to the user to trust. => a > big orange message warning the user! > > btw I would add some requirements for plugin devs. e.g list at least > the following points: > > 1) the reason to have compiled parts (I had to look for a foss4g > presentation to knwow the reason) > 2) the list of shared or executable (I casually discovered them) > 3) the link to the source code (in the plugin or external)... I had to > grep the code to understand that code was available. > 4) guide to build. This can be optional, but I would trust more a user > that expose how to reproduce the build. > 5) checksums x plugin version > > All these info can be contained in the plugin homepage in a standard > way (template). In this way we don't have to add tags in metadata > other than "BEWARE binary inside!" > > opinions? > Luigi Pirelli
This sounds very reasonable to me. Thank you Matthias _______________________________________________ Qgis-developer mailing list [email protected] List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
