[Qgis-developer] Python plugins mandatory metadata

Matthias Kuhn matthias.kuhn at gmx.ch
Wed Aug 27 00:40:32 PDT 2014


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


More information about the Qgis-developer mailing list