[Qgis-developer] Python plugins mandatory metadata

[Alessandro Pasotti]

2014-08-27 9:40 GMT+02:00 Matthias Kuhn <matthias.kuhn at gmx.ch>:
> I would also prefer to keep the entry barrier low.
>
> I.e. if a hobby-programmer does not add these fields to his plugin but
> will happily make (the missing bits) of the source code available on
> request (GPL states on request IIRC) it should be possible for him to
> just upload the plugin, but get warned that he could make people a lot
> more happier if he would set these fields. I can imagine people
> struggle with git, do bugtracking by email or on an internal tracker,
> don't have a homepage... But still make good plugins which could
> eventually evolve into projects with all these parts included. There
> are a lot of other things people can fail at. And just make these
> things hard requirement because they are easy to check does not feel
> right for me.
>
> I would also vote for the solution of having different repos (
> recommended, bood, creepy )
>
> Matthias


Hello Mathias,

We already have the "experimental" flag for not production-ready
plugins, do we really need different repos?


-- 
Alessandro Pasotti
w3:   www.itopen.it