[Qgis-developer] Python plugins mandatory metadata

Trevor Wiens tsw.web at gmail.com
Mon Aug 25 13:07:29 PDT 2014


Since I'm not a contributor to the main project, just some plugins, I'm not
sure my voice will count for much but I think Tim hits on an important
point.

As as a developer of plugins for my company, I have created repos and bug
trackers for the plugins I created because I was asked to but they are not
regularly used, watched or maintained. If anything they are worse than none
at all.

I understand the interest in standard documentation, but even that is often
less than ideal from a companies perspective. Speaking generally companies
provide plugins for two reasons. First, they are something the company
needs and is willing to share with others. Second, they are useful tools
for the company's clients to use with the companies commercial tools or
services. In both cases plugins are, to some extent, a means to promote the
company so hosting documentation on the company site is more valuable to
the company then distributing all of it with the plugin.

I would encourage QGIS developers to try to keep balanced requirements to
ensure that corporate, academic and volunteer contributors and users can
all benefit.

TSW


On Mon, Aug 25, 2014 at 1:38 PM, Tim Sutton <tim at kartoza.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> On 25/08/2014 17:46, Vincent Picavet wrote:
> > Hello,
> >
> >> Hi all.
> >>
> >> Il 25/08/2014 17:06, Tim Sutton ha scritto:
> >>> I agree they should remain optional for now.
> >>
> >> After a few months of managing the plugin approval queue, I still
> >> do not understand what is the advantage of having plugins without
> >> a repo and bugtracker. I agree that a home page is not a
> >> necessity.
> >
> > +1 Moreover, plugins are GPL licenced, hence the source code should
> > be shared when a plugin is distributed. Python is a script
> > language, but still there are some source which should not go into
> > the final plugin package (.ui files typically). Therefore, a plugin
> > _must_ have a full source code available somewhere, and a
> > repository is a logical place for this.
> >
> > Globally it is about improving the global quality of the software,
> > and these steps are the basics a plugin developer should provide.
> >
>
> Yes but there are always going to be exceptions to this and I dont
> believe we should make having these items a sticking point e.g.:
>
> * some one in a corporate environment can't easily make a website for
> the plugin they write
> * Someone in a coprporate environment works in a repo behind a firewall
> * a bug tracker is behind a corporate firewall
>
> As Ale says, its not that we should encourage people not to have these
> things, but we should not penalise them for it unduly if they don't.
>
> I think there are other things that would be more interesting to
> mandate e.g.:
>
> * standardised documentation
> * HIG compliance
> * Including a license file
>
> etc.
>
> I would still like to see us reach a point where we have 'best of
> breed', 'sanctioned' plugins, and the 'wild west' differentiated for
> the users.
>
> Regards
>
> Tim
>
>
> > Vincent _______________________________________________
> > Qgis-developer mailing list Qgis-developer at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
>
> - --
> - ------------------------------------------------------
>
> Tim Sutton
> Visit http://kartoza.com to find out about open source:
>  * Desktop GIS programming services
>  * Geospatial web development
>  * GIS Training
>  * Consulting Services
> Skype: timlinux Irc: timlinux on #qgis at freenode.net
> Tim is a member of the QGIS Project Steering Committee
> - ------------------------------------------------------
> Kartoza is a merger between Linfiniti and Afrispatial
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlP7kLsACgkQqk07qZdiYjd3oQCfXty1OR7OcrPqMpeEDL81E9Sz
> 1UwAnRMiQ++zIK9lgFXN4uOSVY2lCpFd
> =OYHU
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>



-- 
Trevor Wiens
Apropos Information Systems
aproposinfosystems.com
Calgary, Alberta
Ph. 403-973-5901
Fax 780-666-4580
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20140825/124f685d/attachment.html>


More information about the Qgis-developer mailing list