[Qgis-developer] Re: Complicate the plugin situation

[Giuseppe Sucameli]

Hi all,

On Fri, Jan 20, 2012 at 9:40 AM, Alessandro Pasotti <apasotti at gmail.com> wrote:
> 2 - there is no agreement on important topics, the main was if plugins
> without a tracker and a public code repository and a public homepage
> can be accepted on plugins.qgis.org

IMHO they must have both a tracker and a repository, instead a
public homepage I think shouldn't be mandatory.

> 3 - there is not a single place for documentation

The main documentation source for creating/uploading a
python plugins is the pyQGis cookbook, of course it has to
be updated but remember that the new plugin repo is
available since few months only.

> 5 - the plugins website has nothing to do with Redmine instance
> running on hub.qgis.org and there is no bridge between the two (except
> for authentication)

sites doesn't need a really strong integration IMHO, but
of course some kind of joining points between the two would
make life easier to plugin authors.

> 6 - there is not an approval workflow for plugins: I'm not going to
> approve any plugin anymore, somebody  else must do that

In this moment the new repo is available only from QGis master,
and also the plugins site is under testing.
If there isn't a workflow then it's time to define it.

> * all plugins should have a public issue tracker
> * all plugins should should a SNV/GIT core repository

IMOH all plugins *must* have a public tracker and repository.

> * all plugins should have a public homepage
Instead a public page should be strongly recommended.

> "Some important informations are missing from the plugin metadata
> (homepage, tracker or repository). Please consider creating a project
> on hub.qgis.org and filling the missing metadata."

I've seen that warning, but the link should point to a new project creation
(not the hub homepage) and the form should be populated yet (name,
description, set as subproject of "User plugins")

Regards.

-- 
Giuseppe Sucameli