<div><font>+1 on both infrastructure suggestions and guidelines.<br></font></div><div><font><br></font></div><div><font>Both will help users and developers alike. Users will get more consistent plugins and they should be able to report bugs/crashes much more easily than is currently possible.</font><font><br>
</font></div><div><font>Developers should get better feedback, nice automation (such as the autopackaging script) and general guidelines to follow, which will especially help beginners.<br></font></div><div><font><br></font></div>
<div><font>Regards,<br></font></div><div><font><br></font></div><div><font>Anita<br></font></div><div><font><br></font></div><br><div class="gmail_quote">On Wed, Dec 28, 2011 at 5:15 PM, Paolo Cavallini <span dir="ltr"><<a href="mailto:cavallini@faunalia.it">cavallini@faunalia.it</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all.<br>
I recently realized that even core QGISsers do not have the plugin situation clear in<br>
mind. No surprise, as I think we all find it quite complex. I think with a reasonable<br>
effort we can simplify it, with obvious advantages both for developers and users.<br>
These are the necessary steps. IMHO:<br>
- when a plugin is loaded on the repo, a redmine instance should be created<br>
automatically for bugtracking (if not present in metadata.txt)<br>
- at the same time, a git instance should be initialized (if a repo is not present in<br>
metadata.txt)<br>
- also, an autopackaging script should be activated (see other thread)<br>
- add on individual plugin pages on <a href="http://plugins.qgis.org" target="_blank">http://plugins.qgis.org</a>:<br>
. more info<br>
. user comments<br>
. user rating<br>
- add a "deprecated" tag on metadata.txt (by the webapp) and modify the installer so<br>
that deprecated plugins are hidden by default<br>
- an utility should be added to send plugin bug reports (with python taceback)<br>
directly from QGIS<br>
- add a series of guidelines (and possibly some templates) to make plugins more<br>
homogeneous (e.g. how and where to add an help page; if layers should be loaded after<br>
an analysis by clicking on a checkbox before the analysis, *or* clicking on OK form a<br>
popup after it, etc.)<br>
- when all is ready, and in any case for 2.0, remove old repos from the installer.<br>
Opinions? If we agree, Faunalia can help in some of these steps.<br>
All the best.<br>
<span class="HOEnZb"><font color="#888888">--<br>
Paolo Cavallini - Faunalia<br>
<a href="http://www.faunalia.eu" target="_blank">www.faunalia.eu</a><br>
Full contact details at <a href="http://www.faunalia.eu/pc" target="_blank">www.faunalia.eu/pc</a><br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</font></span></blockquote></div><br>