Hi Luigi, While a bugtracker and a code repository are definitely a good thing to have I do not think that it should be mandatory from the beginning.
It should be required that a way to contact the developer (mail), the source code and license are there. At the beginning (experimental) state of a plugin the dev may be worried about other things than the bugtracker and telling him by mail about possible defects is fine (it's him who has to deal with this). Plugins need to be open source, but the way they handle project management and community should be up to the plugin author. So the best thing we can do is send him a notice with "what has been tested by and proven helpful for others in the past". Putting too many requirements in place may scare people off. I think being minimal with regard to requirements is important for experimental plugins and IMHO I would treat it the same way for stable plugins but there is a bit more space to discuss requirements I think. How do others feel? Best regards, Matthias On 02/18/2015 11:42 AM, Luigi Pirelli wrote: > Hi > > today I found a new plugin > > http://plugins.qgis.org/plugins/VerticalHorizon/ > > set as experimental, but without code repo and bugtrack > > It is assumed that for published but experimental plugin this data > could not be set? > > in my opinion, at least bugtrack would be set. If a plugin creates > malfunctions we need a way to trace and notify these errors to the > author. > > regards, Luigi Pirelli > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
