In my experience Paulo has been doing  good job of encouraging developers
to do just that.

If we want to formalize it further it might be a good idea to set the
requirements lower for experimental plugins as it happens to be a helpful
means of facilitating testing plugins on different platforms.

TSW
On Feb 23, 2015 4:26 AM, "Jonathan Moules" <j.mou...@hrwallingford.com>
wrote:

> Hi Paulo,
> Surely this can be "enforced" by having requirements for acceptance on the
> official plugin repository. If a plugin doesn't fulfil all the
> requirements, it doesn't get included.
>
> Possible requirements (to give an idea):
> - Brief description of plugin,
> - Detailed explanation of plugin.
> - "How to use" documentation.
> - Useful, consistent tags.
> - Homepage/tracker/repository links (that work and go somewhere relevant).
> - Author
> - Changelog
> - Date of last plugin release
> - Supported QGIS Versions
>
> This may (will) mean fewer plugins, however the plugins that don't get
> included would be ones with poor user documentation. Most plugins fail
> quite badly at making it clear what they do, let alone how to use them.
> That lot wouldn't take much more than half an hour to do for any given
> plugin (with only a few very-complex exceptions) and would make plugins
> much more useable.
>
> Cheers,
> Jonathan
>
>
> -----Original Message-----
> From: qgis-developer-boun...@lists.osgeo.org [mailto:
> qgis-developer-boun...@lists.osgeo.org] On Behalf Of Paolo Cavallini
> Sent: Friday, February 20, 2015 1:12 PM
> To: Lynton Cox
> Cc: qgis-user; qgis-developer
> Subject: Re: [Qgis-developer] [Qgis-user] Better tags for plugins
>
> Hi Lynton,
>
> Il 19/02/2015 19:21, Lynton Cox ha scritto:
> > Please don't forget the newbies need to know exactly what plugins
> > might be used for - some have hardly any description. Once out of the
> > basic QGIS manual finding one's way around isnt that easy. Many
> > amateurs in areas such as local studies realise how useful GIS but see
> > that jargon and acronyms can fog the path.
>
> Yes, the About is often neglected. I invite plugin authors to add a
> reasonable description, but I cannot enforce this.
> A very good idea would be for the user to write a short note and add it to
> a feature request, through the plugin bugtracker; even better, this could
> be added as a Pull Request on the plugin repository.
> All the best, and thanks.
>
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> *New course* "QGIS for naturalists":
> http://www.faunalia.eu/en/nat_course.html
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> This message has been scanned for viruses by MailControl -
> www.mailcontrol.com
>
>
>
> Click
> https://www.mailcontrol.com/sr/SVGcvJSn6gnGX2PQPOmvUizKrmxxhcEGGlzw3ci4oH!oYUmIc3YrHGSGHzny8KZlOXtgio1tB25zr!jqbv!p6A==
> to report this email as spam.
>
> ________________________________
>
> HR Wallingford and its subsidiaries uses faxes and emails for confidential
> and legally privileged business communications. They do not of themselves
> create legal commitments. Disclosure to parties other than addressees
> requires our specific consent. We are not liable for unauthorised
> disclosures nor reliance upon them.
> If you have received this message in error please advise us immediately
> and destroy all copies of it.
>
> HR Wallingford Limited
> Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom
> Registered in England No. 02562099
>
> ________________________________
> _______________________________________________
> 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

Reply via email to