Hi all.
I recently realized that even core QGISsers do not have the plugin situation
clear in
mind. No surprise, as I think we all find it quite complex. I think with a
reasonable
effort we can simplify it, with obvious advantages both for developers and
users.
These are the necessary steps. IMHO:
- when a plugin is loaded on the repo, a redmine instance should be created
automatically for bugtracking (if not present in metadata.txt)
- at the same time, a git instance should be initialized (if a repo is not
present in
metadata.txt)
- also, an autopackaging script should be activated (see other thread)
- add on individual plugin pages on http://plugins.qgis.org:
. more info
. user comments
. user rating
- add a "deprecated" tag on metadata.txt (by the webapp) and modify the
installer so
that deprecated plugins are hidden by default
- an utility should be added to send plugin bug reports (with python taceback)
directly from QGIS
- add a series of guidelines (and possibly some templates) to make plugins more
homogeneous (e.g. how and where to add an help page; if layers should be loaded
after
an analysis by clicking on a checkbox before the analysis, *or* clicking on OK
form a
popup after it, etc.)
- when all is ready, and in any case for 2.0, remove old repos from the
installer.
Opinions? If we agree, Faunalia can help in some of these steps.
All the best.
--
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
