2015-02-23 16:18 GMT+01:00 Frank M. Howell :
> My two cents...I understand the validation requirements. But I think the
> fundamental problem is those plugin authors who submit a plugin for X and
> then describe it thusly: "This is a plugin for X" where X is the same name as
> the plugin. The pr
My two cents...I understand the validation requirements. But I think the
fundamental problem is those plugin authors who submit a plugin for X and then
describe it thusly: "This is a plugin for X" where X is the same name as the
plugin. The problem is that this one word or very brief phrase isn'
2015-02-23 15:41 GMT+01:00 Trevor Wiens :
> 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 f
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.
- "
Il 20/02/2015 08:13, Alessandro Pasotti ha scritto:
> Would you mind writing a short sentence that summarize the rules for
> an ideal tag?
> I could add them into http://plugins.qgis.org website and maybe they
> can also be added to the plugin builder.
This would be a very good enhancement.
Pleas
2015-02-20 1:47 GMT+01:00 Trevor Wiens :
> I took a look through the list and if you wany to make a consistent set of
> tags to use then the list will need to be short and obvious.In this light I
> would make the following suggestions:
>
> 1. The is comprised of items that could be used to make com
