Bugtracker and code repo for plugin
Do you agree in making the code repo and bugtracker a requisite for plugin publication?
Paolo Cavallini Wed 27 May 2015 5:24PM
I would like to reopen the old vatation, and first agree on that, but I do not know if and how it is possible.
Anita Graser Wed 27 May 2015 6:40PM
Imho the original one is agreed on and is not affected by the new additional suggestion.
Paolo Cavallini Thu 28 May 2015 5:46AM
OK, thanks, proceeding.
Tim Sutton Fri 29 May 2015 4:05PM
What I would like to see is a short description as Anita has suggested.
Paolo Cavallini Fri 29 May 2015 4:34PM
An About would be nice; I always suggest plugin writer to add it. In some cases it is not an absolute necessity; I would not make it compulsory.
Anita Graser Fri 5 Jun 2015 11:17AM
It would be helpful if a trusted group of users of the plugin website could edit the plugin descriptions to add details. As far as I know, currently the description can only be changed in the metadata by uploading a new version of the plugin archive.
Paolo Cavallini · Wed 27 May 2015 5:24PM
I think we can go one step at a time: first the bugtracker and the code repo, then the documentation. I would like to be gentle with the plugin authors, especially the many newcomers.
Several plugins are so straightforward that a 2 line about is just fine.