Hi, On 25/05/2016 12:39, Even Rouault wrote: [...] > The only cases where it makes sense in practice to have a plugin under a > permissive license are : [...] > - a more reasonable use case would be a plugin that would be compatible of > QGIS and another proprietary GIS through some abstraction layer of their > different APIs. The core of your plugin could then be permissively licensed > to > be compatible of both licensing models.
Another thing to keep in mind is that PyQt is also GPLv2. Therefore if you want to make any call to PyQt, you would also have to do the same work of having an abstraction layer on top of it, which would be a pain. This use case therefore makes less sense when you base your work on PyQt. Or you have to buy a commercial licence from Riverbank for PyQt. Using PySide to ease licence issues in this case may be something we would have to think about, now that there will be support for it again. Vincent > > </my ow opinion, not pretending this is the project one> > >> >> On Wed, 25 May 2016 8:01 pm Paolo Cavallini <cavall...@faunalia.it> wrote: >>> Il 25/05/2016 11:42, Tom Chadwin ha scritto: >>>> I guess I am just sceptical that GPL's requirement for GPL licensing of >>>> a product, purely by virtue of importing the first product as a >>>> library, is likely to hold much legal weight. >>> >>> We asked for legal advice, and that was the official response. >>> All the best. >>> >>> -- >>> Paolo Cavallini - www.faunalia.eu >>> QGIS & PostGIS courses: http://www.faunalia.eu/training.html >>> _______________________________________________ >>> Qgis-developer mailing list >>> Qgis-developer@lists.osgeo.org >>> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer >>> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
