Hello, Le jeudi 13 février 2014 12:15:24, Richard Duivenvoorde a écrit : ...[snip]... > Approval: > > 1) your plugin will not be public until it is approved by a set of > community approvers > 2) give approvers some time to do this (after 2 weeks just email to...) > 3) to approve we check that (checklist): [...] > - has a proper license (???? which one? and info about that??)
There is no choice on the licence a plugin can be distributed under : a python import is considered a link, therefore the "import qgis.core" is enough to propagate the GPL licence to the plugin. There may be some other files under different licences though, namely sample data, documentation or whatever else is not concerned by the link and GPL "contamination". Vincent > - supports english language > - does not duplicate of existing functionality or plugin, unless there > is a very good reason (plz provide this reason in the description or > metadata) > > For the first point (orange block) can we standardize on Github? Can we > ask from the average plugin author to put his code on Github? Because > then an author has both an issuetracker and either a README or a wiki. > > Then here: > > http://www.qgis.org/en/docs/pyqgis_developer_cookbook/plugins.html#plugin-m > etadata-table > > AND in the plugin code, make repository a required property, and keep > homepage and tracker optional. BUT that should be enforced in the plugin > repo code then. > > > Is this clear enough? > Please comment/rewrite in a way that I can copy it into the website. > > Regards, > > Richard Duivenvoorde > > > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
