Re: [Qgis-developer] Possible plugin licensing problems

[Bernhard Ströbl]

As far as I understood the recent plugin licensing discussion on this 
list a plugin importing qgis.core or qgis.gui (or OS-pyQt) needs to be 
licenced compatible to GPL2, so even in a private repository a plugin 
author cannot claim a plugin to be for private use only(?). One could of 
course publish a limited-use plugin under GPL and sell the full blown 
plugin, but as it has to be GPL, too, after some sales it might be 
available for download somewhere.

Please correct me if I am wrong.

Bernhard

Am 26.05.2016 um 08:41 schrieb Paolo Cavallini:

It has been submitted, not approved pending our decision.
Thanks.

Il 26 maggio 2016 08:37:20 CEST, Andreas Neumann  ha 
scritto:

Hi Paolo,

Is this in our main public plugin repository?

I think we shouldn't have such plugins in our main repository. If it is

in a private repository, there is not much we can do, probably.

Andreas

On 26.05.2016 08:07, Paolo Cavallini wrote:

Hi all,
I'm unsure this is acceptable for us:
===
Please know that this Plugin is for own use purpose/evaluation but

not

for commercial. If you need it for commercial purpose please contact
***, and I will refer you to our marketing team to buy the commercial
*** key. At the same time, the non-commercial also has limitation on
number of calls and points.
===
Opinions?
Thanks.


___
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





__ Information from ESET Mail Security, version of virus signature 
database 13547 (20160526) __

The message was checked by ESET Mail Security.
http://www.eset.com


___
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

Re: [Qgis-developer] Possible plugin licensing problems

[Paolo Cavallini]

It has been submitted, not approved pending our decision.
Thanks.

Il 26 maggio 2016 08:37:20 CEST, Andreas Neumann  ha 
scritto:
>Hi Paolo,
>
>Is this in our main public plugin repository?
>
>I think we shouldn't have such plugins in our main repository. If it is
>
>in a private repository, there is not much we can do, probably.
>
>Andreas
>
>On 26.05.2016 08:07, Paolo Cavallini wrote:
>> Hi all,
>> I'm unsure this is acceptable for us:
>> ===
>> Please know that this Plugin is for own use purpose/evaluation but
>not
>> for commercial. If you need it for commercial purpose please contact
>> ***, and I will refer you to our marketing team to buy the commercial
>> *** key. At the same time, the non-commercial also has limitation on
>> number of calls and points.
>> ===
>> Opinions?
>> Thanks.
>
>___
>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

-- 
Paolo Cavallini
www.faunalia.eu___
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

Re: [Qgis-developer] Possible plugin licensing problems

[Andreas Neumann]

Hi Paolo,

Is this in our main public plugin repository?

I think we shouldn't have such plugins in our main repository. If it is 
in a private repository, there is not much we can do, probably.


Andreas

On 26.05.2016 08:07, Paolo Cavallini wrote:

Hi all,
I'm unsure this is acceptable for us:
===
Please know that this Plugin is for own use purpose/evaluation but not
for commercial. If you need it for commercial purpose please contact
***, and I will refer you to our marketing team to buy the commercial
*** key. At the same time, the non-commercial also has limitation on
number of calls and points.
===
Opinions?
Thanks.


___
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

Re: [Qgis-developer] Possible plugin licensing problems

[Tim Sutton]

Hi



> On 26 May 2016, at 08:07, Paolo Cavallini  wrote:
> 
> Hi all,
> I'm unsure this is acceptable for us:
> ===
> Please know that this Plugin is for own use purpose/evaluation but not
> for commercial. If you need it for commercial purpose please contact
> ***, and I will refer you to our marketing team to buy the commercial
> *** key. At the same time, the non-commercial also has limitation on
> number of calls and points.
> ===

Is the plugin available as Open Source / GPL? If it is there is actually no 
reason (even if it is not very sympathetic with our community norms and values) 
that I can think of why a company can’t do this. Though I guess circumventing 
their key restriction would then be trivia?

Regards

Tim

> Opinions?
> Thanks.
> -- 
> 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




---

Tim Sutton
QGIS Project Steering Committee Chair
t...@qgis.org




___
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] Possible plugin licensing problems

[Paolo Cavallini]

Hi all,
I'm unsure this is acceptable for us:
===
Please know that this Plugin is for own use purpose/evaluation but not
for commercial. If you need it for commercial purpose please contact
***, and I will refer you to our marketing team to buy the commercial
*** key. At the same time, the non-commercial also has limitation on
number of calls and points.
===
Opinions?
Thanks.
-- 
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] Plugin [663] QuickMapServices approval notification.

[noreply]

Plugin QuickMapServices approval by nextgis.
The plugin version "[663] QuickMapServices 0.17" is now approved
Link: http://plugins.qgis.org/plugins/quick_map_services/
___
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] Plugin [1008] TomTom POI Reader unapproval notification.

[noreply]

Plugin TomTom POI Reader unapproval by pcav.
The plugin version "[1008] TomTom POI Reader 1.0" is now unapproved
Link: http://plugins.qgis.org/plugins/PoiReader/
___
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] Plugin [663] QuickMapServices approval notification.

[noreply]

Plugin QuickMapServices approval by nextgis.
The plugin version "[663] QuickMapServices 0.17" is now unapproved
Link: http://plugins.qgis.org/plugins/quick_map_services/
___
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

Re: [Qgis-developer] Qt4->Qt5 timeline: Qt4's status and Qt4's webkit removal in Stretch

[Sebastiaan Couwenberg]

On 12/07/2015 07:42 PM, Sebastiaan Couwenberg wrote:
> On 02-05-15 10:19, Luigi Pirelli wrote:
>> http://perezmeyer.blogspot.com.es/2015/05/qt4s-status-and-qt4s-webkit-removal-in.html
> 
> As reported in Debian Bug #784514 [0], the WebKit support will be
> removed from python-qt4 in earlier 2015 (but not before January 7th, one
> month from now).
> 
> [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784514#43

It took longer than expected, because the Qt maintainers were waiting
for QGIS to move away from its reliance on WebKit in Qt4.

Because that wasn't going to happen before the WebKit support was
actually no longer available, I asked the Qt maintainers to stop waiting
for QGIS and go ahead and break it with the python-qt4 upload initially
planned for earlier this year.

QGIS now shows lovely stacktraces informing the user about the missing
QtWebKit modules.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
___
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

Re: [Qgis-developer] make error

[Paolo Cavallini]

Il 25/05/2016 17:54, Paolo Cavallini ha scritto:
> Hi all,
> I'm now compiling qgis with qt5+py3 support on a clean machine.
> Unfortunately build fails with:

qt5-default was missing, needed, and not required by cmake


-- 
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] make error

[Paolo Cavallini]

Hi all,
I'm now compiling qgis with qt5+py3 support on a clean machine.
Unfortunately build fails with:

...
[ 80%] Built target t2tdoc
[ 80%] Generating ../output/i18n/qgis_ar.qm
lrelease: could not find a Qt installation of ''
i18n/CMakeFiles/translations.dir/build.make:98: recipe for target
'output/i18n/qgis_ar.qm' failed
make[2]: *** [output/i18n/qgis_ar.qm] Error 1
CMakeFiles/Makefile2:4019: recipe for target
'i18n/CMakeFiles/translations.dir/all' failed
make[1]: *** [i18n/CMakeFiles/translations.dir/all] Error 2
Makefile:160: recipe for target 'all' failed
make: *** [all] Error 2

I'd appreciate any hint on how to solve this.
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] Plugin [1000] Qdraw approval notification.

[noreply]

Plugin Qdraw approval by pcav.
The plugin version "[1000] Qdraw 1.0 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/qdraw/
___
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] Plugin [1000] Qdraw approval notification.

[noreply]

Plugin Qdraw approval by pcav.
The plugin version "[1000] Qdraw 1.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/qdraw/
___
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] Plugin [922] CKAN-Browser approval notification.

[noreply]

Plugin CKAN-Browser approval by pcav.
The plugin version "[922] CKAN-Browser 0.3.1" is now approved
Link: http://plugins.qgis.org/plugins/CKANBrowser/
___
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

Re: [Qgis-developer] crash when adding relation with incomplete parameters

[Matthias Kuhn]

Implemented the solution with disabling the ok button until all required
fields are there.

Can you check and give a feedback?

If it's ok, I'll backport to 2.14

Best
Matthias

On 23/05/16 14:40, Neumann, Andreas wrote:
>
> Hi Lauri,
>
> I had the same just recently. I would also appreciate if QGIS would
> not crash in this situation. Can you please provide a bug report?
>
> Thanks,
> Andreas
>
> On 2016-05-23 14:30, Lauri Kajan wrote:
>
>> Hi all,
>>
>> When creating a new relation between two layers in project settings I
>> accidentally pressed enter after giving just a name of the relation.
>> QGIS crashed and I got the minidump window.
>>  
>> Can you confirm?
>>  
>> I think the OK button should be disabled until all needed parameters
>> are given.
>>  
>>  
>> I filed a bug http://hub.qgis.org/issues/14869
>>  
>>  
>> Thanks,
>>  
>> Lauri
>>
>> ___
>> 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

___
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

Re: [Qgis-developer] Plugin licence

[Greg Troxel]

"Vincent Picavet (ml)"  writes:

> Hello,
>
> On 25/05/2016 11:42, Tom Chadwin wrote:
>> Vincent Picavet (ml) wrote
>>> I may be wrong, but if qgis2web is like qgis2three, it generates
>>> projects containing OL3 or leaflet code ?
>>> In this case, there is no code link between the Python plugin and
>>> Leaflet nor OL3
>> 
>> Yes, this is how it works. However, the code it generates *does* link to the
>> other libraries in code. I think it would therefore be egregious to say no
>> link exists between the Python code and the third-party JS libraries.
>
> The term "link" is very subtle, and is key to the issue here. There is
> absolutely no "link" in the sense of the GPL between your Python module
> and the code you generate. The generated code can be considered as data
> for your plugin ( template, replacement values).

Programmers focus on link, but it's really not the point.  The question
in copyright law is "derived work" or "a work based on the program".  So
the typical view among hard-core licensing nerds is that the source of a
plugin -- because it is fundamentally an extension to the main program
-- is a derived work.  Thus one needs permission from the original
copyright holders to distribute it.  The GPL only grants such permission
if the plugin is licensed under the GPL.

As to being derived works of multiple things at once, yes, that may well
be true.  One needs permission from all.  That doesn't mean matching
license.  It means that given the plugin license, the copyright holders
of all underlying programs must be willing to grant permission.  For BSD
licenses, there is no issue (other than preserving the notice, more or
less).


signature.asc
Description: PGP signature
___
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

Re: [Qgis-developer] Plugin licence

[Vincent Picavet (ml)]

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


> 
> 
> 
>>
>> On Wed, 25 May 2016 8:01 pm Paolo Cavallini  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

Re: [Qgis-developer] Plugin licence

[Even Rouault]

Le mercredi 25 mai 2016 13:26:02, Vincent Picavet (ml) a écrit :
> Hi,
> 
> On 25/05/2016 12:39, Even Rouault wrote:
> [..]
> 
> > 
> > 
> > Technically you could licence the plugin with any license you want, but
> > as soon you execute it against QGIS, it must be compatible of GPL v2+,
> > since it is a derived work of QGIS GPLv2 code, and thus it must convey
> > the same rights and obligations offered and constrained by the GPLv2
> > license.
> > So you could also licence it under X/MIT, BSD 2/3 clauses or which ever
> > other free licences that are compatible with GPLv2+.
> > It cannot be under a proprietary license, because GPLv2 would impose to
> > have access to the source code.
> > 
> > The only cases where it makes sense in practice to have a plugin under a
> > permissive license are :
> > - imagine that someone would reimplement a QGIS alternative that would
> > have the same API as QGIS but would be more permissively licensed, then
> > it could make sense to have your plugin under that permissive license.
> > - 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.
> > 
> > 
> 
> I do agree with this analysis.
> 
> Note that as for the Nvidia case mentionned, the Linux kernel has an
> exception to GPL for proprietary modules. Not sure it plays a role on
> the issue you mentionned, but it may be a strong difference with other
> software which do not have this exception.

Are you really sure of that ? If that was the case there would not be all 
those debates regarding whether proprietary kernel modules are allowed or not.

My understanding of 
https://en.wikipedia.org/wiki/Linux_kernel#Loadable_kernel_modules is that all 
the subtelty resides in whether a module is a derived work of another one. 
There's no special explicit exception. The folks that put proprietary modules 
say they are not derived works from the kernel, hence not bound to GPL.

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
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

Re: [Qgis-developer] Plugin licence

[Vincent Picavet (ml)]

Hi,

On 25/05/2016 14:07, Tom Chadwin wrote:
> Vincent Picavet (ml) wrote
>> A grey area would be for example if you were using a QWebEngine
>> component in your Python Plugin, directly calling javascript functions
>> of the Javascript library from your Python code.
>> In that case I really do not know if it would be considered a link in
>> the GPL sense.
>>
>> But for your use case with code generation it is really clear.
> 
> A QWebView is used in the GUI as a preview window, and loads in the
> libraries. So it directly uses them, in that the generated output JS is
> loaded by Python into the QWebView. That sounds potentially like a "link" to
> me (apologies for not thinking of that before - I didn't appreciate its
> relevance).

I would say that while you just load the HTML in a QWebView, this is not
a link : the embedded web client loads the HTML file and interprets it,
independently of your code. I'd say you are still safe here, and I would
still consider the generated pages as data for from your plugin point of
view.

If you would call a javascript function from Python through a direct
code binding I would say it may be considered a link. But this is my own
personal interpretation. This is where we enter a grey zone, and I do
not have any online resource to point to in this case.
If you want to know more on this, I know some IP lawyers specialized in
OpenSource who may help.

For me your use case is still safe and non-binding. Furthermore, it is
pretty common with all softwares loading HTML documentation from within
an embedded browser, and I have never seen any licence trouble arising
with this.

Vincent

___
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

Re: [Qgis-developer] Plugin licence

[Tom Chadwin]

Vincent Picavet (ml) wrote
> A grey area would be for example if you were using a QWebEngine
> component in your Python Plugin, directly calling javascript functions
> of the Javascript library from your Python code.
> In that case I really do not know if it would be considered a link in
> the GPL sense.
> 
> But for your use case with code generation it is really clear.

A QWebView is used in the GUI as a preview window, and loads in the
libraries. So it directly uses them, in that the generated output JS is
loaded by Python into the QWebView. That sounds potentially like a "link" to
me (apologies for not thinking of that before - I didn't appreciate its
relevance).

Tom



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/License-Summary-tp5006354p5268146.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
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

Re: [Qgis-developer] Plugin licence

[Vincent Picavet (ml)]

Hello,

On 25/05/2016 11:42, Tom Chadwin wrote:
> Vincent Picavet (ml) wrote
>> I may be wrong, but if qgis2web is like qgis2three, it generates
>> projects containing OL3 or leaflet code ?
>> In this case, there is no code link between the Python plugin and
>> Leaflet nor OL3
> 
> Yes, this is how it works. However, the code it generates *does* link to the
> other libraries in code. I think it would therefore be egregious to say no
> link exists between the Python code and the third-party JS libraries.

The term "link" is very subtle, and is key to the issue here. There is
absolutely no "link" in the sense of the GPL between your Python module
and the code you generate. The generated code can be considered as data
for your plugin ( template, replacement values).

For compiled code, the definition of a link is quite easy, and much more
complicated for script languages. The Plone project has done a deep
analysis some time ago and concluded that a "import" in Python is
considered a link in the sense of the GPL.

A grey area would be for example if you were using a QWebEngine
component in your Python Plugin, directly calling javascript functions
of the Javascript library from your Python code.
In that case I really do not know if it would be considered a link in
the GPL sense.

But for your use case with code generation it is really clear.

> Also, as I say, qgis2web redistributes those other libraries.
No problem neither, keep them with the original licence.

> I appreciate that, as you say, the other libs are largely licensed more
> permissively, and compatibly with QGIS - MIT/two-clause BSD.

Yes, this leads to much lesser complications.

> 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.
> 
> Anyway, to clarify, the advice is that GPLv2+ is the only acceptable licence
> - not even v3+?

As even noted, you could use a more permissive licence ( MIT, BSD ), but
the real use cases are rare.
As for using GPLv3 ( or later, which is the same right now ), it is more
complicated. QGIS being GPLv2+, it would be compatible. But you would
not be allowed to distribute that package ( QGIS & your GPLv3 plugin)
with any other piece of software which would be GPLv2 only, as GPLv2 and
GPLv3 are not compatible. Bad idea therefore.

Usual disclaimer : I'm not a lawyer, but still studied these issues a lot.

Vincent

> 
> Thanks for your patience and opinions
> 
> Tom
> 
> 
> 
> --
> View this message in context: 
> http://osgeo-org.1560.x6.nabble.com/License-Summary-tp5006354p5268117.html
> Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
> ___
> 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

Re: [Qgis-developer] Plugin licence

[Vincent Picavet (ml)]

Hi,

On 25/05/2016 12:39, Even Rouault wrote:
[..]
> 
> 
> Technically you could licence the plugin with any license you want, but as 
> soon you execute it against QGIS, it must be compatible of GPL v2+, since it 
> is a derived work of QGIS GPLv2 code, and thus it must convey the same rights 
> and obligations offered and constrained by the GPLv2 license.
> So you could also licence it under X/MIT, BSD 2/3 clauses or which ever other 
> free licences that are compatible with GPLv2+.
> It cannot be under a proprietary license, because GPLv2 would impose to have 
> access to the source code.
> 
> The only cases where it makes sense in practice to have a plugin under a 
> permissive license are :
> - imagine that someone would reimplement a QGIS alternative that would have 
> the same API as QGIS but would be more permissively licensed, then it could 
> make sense to have your plugin under that permissive license.
> - 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.
> 
> 

I do agree with this analysis.

Note that as for the Nvidia case mentionned, the Linux kernel has an
exception to GPL for proprietary modules. Not sure it plays a role on
the issue you mentionned, but it may be a strong difference with other
software which do not have this exception.

Vincent



> 
>>
>> On Wed, 25 May 2016 8:01 pm Paolo Cavallini  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

Re: [Qgis-developer] Plugin licence

[Even Rouault]

> - 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.

Actually this point is quite interesting since for example NVidia claims that 
their proprietary code for their video drivers is not a derived work of the 
Linux kernel since it is used in the drivers of other OS. So only the 
adaptation layer between their generic driver and the Linux kernel is GPL. 
This is of course a much disputable point of view, but nobody has cared enough 
to challenge NVidia in front of a court. What it shows is that the concept of 
what is a derived work or not can be somewhat fuzzy.

> 
> 
> 
> > On Wed, 25 May 2016 8:01 pm Paolo Cavallini  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

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
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

Re: [Qgis-developer] Plugin licence

[Saber Razmjooei]

Apologies Tom, my comment was a reference to a discussion a number of years ago 
when the same topic was raised.

Not sure the answer to your question about licensing of your plugin. In your 
case, you are still making the source code available. The ones I have in mind 
are distributing the closed source version of their plugins.

Cheers,
Saber

-Original Message-
From: Qgis-developer [mailto:qgis-developer-boun...@lists.osgeo.org] On Behalf 
Of Tom Chadwin
Sent: 25 May 2016 11:08
To: qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Plugin licence

Saber Razmjooei wrote
> GPL licensing [...] potentially discourages the uptake of QGIS amongst 
> uniformed users/organisations.

Also my concern, but not for the uninformed, but the very informed - ie those 
not in favour of GPL's restrictions.



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/License-Summary-tp5006354p5268126.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
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


--
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately
by e-mail if you have received this e-mail by mistake and delete this e-mail 
from your system. If you are not the intended recipient you are notified
that disclosing, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited.

Whilst reasonable care has been taken to avoid virus transmission, no 
responsibility for viruses is taken and it is your responsibility to carry out
such checks as you feel appropriate.

If this email contains a quote or offer to sell products, carry out work or 
perform services then our standard terms and conditions (which can be found at 
http://www.lutraconsulting.co.uk/downloads/Lutra%20Consulting%20Standard%20Terms%20and%20Conditions.pdf
 shall apply unless explicitly stated otherwise.

Saber Razmjooei and Peter Wells trading as Lutra Consulting.
___
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

Re: [Qgis-developer] Plugin licence

[Even Rouault]

Le mercredi 25 mai 2016 12:03:58, Nathan Woodrow a écrit :
> >>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.
> 
> That is one of the main things with GPL and why a lot of people do tend to
> avoid it I guess.  Not much we can do for it now all plugins are GPL.



Technically you could licence the plugin with any license you want, but as 
soon you execute it against QGIS, it must be compatible of GPL v2+, since it 
is a derived work of QGIS GPLv2 code, and thus it must convey the same rights 
and obligations offered and constrained by the GPLv2 license.
So you could also licence it under X/MIT, BSD 2/3 clauses or which ever other 
free licences that are compatible with GPLv2+.
It cannot be under a proprietary license, because GPLv2 would impose to have 
access to the source code.

The only cases where it makes sense in practice to have a plugin under a 
permissive license are :
- imagine that someone would reimplement a QGIS alternative that would have 
the same API as QGIS but would be more permissively licensed, then it could 
make sense to have your plugin under that permissive license.
- 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.



> 
> On Wed, 25 May 2016 8:01 pm Paolo Cavallini  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

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
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

Re: [Qgis-developer] Plugin licence

[Tom Chadwin]

Saber Razmjooei wrote
> GPL licensing [...] potentially discourages the uptake of QGIS amongst
> uniformed users/organisations.

Also my concern, but not for the uninformed, but the very informed - ie
those not in favour of GPL's restrictions.



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/License-Summary-tp5006354p5268126.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
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

Re: [Qgis-developer] Plugin licence

[Paolo Cavallini]

Il 25/05/2016 12:10, Saber Razmjooei ha scritto:

> Can we have a page on the website explaining the licensing of plugins and the 
> reasons behind it?
> 
> We have come across a couple of plugins all with pyc and no code provided to 
> the end users. 

Please let me know which.
Thanks.

-- 
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

Re: [Qgis-developer] Plugin licence

[Saber Razmjooei]

Hi,
Can we have a page on the website explaining the licensing of plugins and the 
reasons behind it?

We have come across a couple of plugins all with pyc and no code provided to 
the end users. 

I understand at the beginning the GPL licensing of the plugins was not enforced 
as it potentially discourages the uptake of QGIS amongst uniformed 
users/organisations. But I think it is the right time to have a clear guideline 
on that before things get out of hand.

Cheers,
Saber



-Original Message-
From: Qgis-developer [mailto:qgis-developer-boun...@lists.osgeo.org] On Behalf 
Of Paolo Cavallini
Sent: 25 May 2016 11:01
To: qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Plugin licence

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


--
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately
by e-mail if you have received this e-mail by mistake and delete this e-mail 
from your system. If you are not the intended recipient you are notified
that disclosing, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited.

Whilst reasonable care has been taken to avoid virus transmission, no 
responsibility for viruses is taken and it is your responsibility to carry out
such checks as you feel appropriate.

If this email contains a quote or offer to sell products, carry out work or 
perform services then our standard terms and conditions (which can be found at 
http://www.lutraconsulting.co.uk/downloads/Lutra%20Consulting%20Standard%20Terms%20and%20Conditions.pdf
 shall apply unless explicitly stated otherwise.

Saber Razmjooei and Peter Wells trading as Lutra Consulting.
___
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

Re: [Qgis-developer] Plugin licence

[Nathan Woodrow]

>>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.

That is one of the main things with GPL and why a lot of people do tend to
avoid it I guess.  Not much we can do for it now all plugins are GPL.


On Wed, 25 May 2016 8:01 pm Paolo Cavallini  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

Re: [Qgis-developer] Plugin licence

[Paolo Cavallini]

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

Re: [Qgis-developer] Plugin licence

[Tom Chadwin]

Vincent Picavet (ml) wrote
> I may be wrong, but if qgis2web is like qgis2three, it generates
> projects containing OL3 or leaflet code ?
> In this case, there is no code link between the Python plugin and
> Leaflet nor OL3

Yes, this is how it works. However, the code it generates *does* link to the
other libraries in code. I think it would therefore be egregious to say no
link exists between the Python code and the third-party JS libraries. Also,
as I say, qgis2web redistributes those other libraries.

I appreciate that, as you say, the other libs are largely licensed more
permissively, and compatibly with QGIS - MIT/two-clause BSD.

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.

Anyway, to clarify, the advice is that GPLv2+ is the only acceptable licence
- not even v3+?

Thanks for your patience and opinions

Tom



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/License-Summary-tp5006354p5268117.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
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] Plugin [1006] TomTom POI Reader unapproval notification.

[noreply]

Plugin TomTom POI Reader unapproval by pcav.
The plugin version "[1006] TomTom POI Reader 1.0" is now unapproved
Link: http://plugins.qgis.org/plugins/PoiReader/
___
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

Re: [Qgis-developer] Plugin licence

[Vincent Picavet (ml)]

Hello,

On 25/05/2016 10:41, Tom Chadwin wrote:
> Of course, since qgis2web is middleware, its licence also has to be
> compatible with Leaflet, Openlayers 3, and their respective plugins, none of
> which are GPL. Since the plugin bundles and distributes these libraries, I
> would say complying with their licences is of greater importance than
> complying with QGIS, which is not distributed with the plugin.
> 
> Not trying to start an argument - I just want to do the right thing by the
> creators of all the software on which mine is built.

I may be wrong, but if qgis2web is like qgis2three, it generates
projects containing OL3 or leaflet code ?
In this case, there is no code link between the Python plugin and
Leaflet nor OL3, and therefore no compatibility problem. You can keep
the original licences for these libraries and their respective plugins.

But the Python code for your plugin has to be GPLv2 as soon as you do an
"import qgis.core" and you distribute the plugin.

Furthermore, since OL3 and LeafLet are BSD-licenced, there actually is
no issue since this licence is compatible with GPL. You can link GPL
code to MIT or BSD without problem.

Vincent
___
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

Re: [Qgis-developer] Plugin licence

[Nathan Woodrow]

I'm sure you have much choice when it gets to GPL. Your plugin is still GPL
regardless. It does get a bit slippery once you include other libraries but
I think it's fine in this case.  They are all open source so no harm
really.

Same as use using GDAL with it being MIT

On Wed, 25 May 2016 6:56 pm Tom Chadwin  wrote:

> Of course, since qgis2web is middleware, its licence also has to be
> compatible with Leaflet, Openlayers 3, and their respective plugins, none
> of
> which are GPL. Since the plugin bundles and distributes these libraries, I
> would say complying with their licences is of greater importance than
> complying with QGIS, which is not distributed with the plugin.
>
> Not trying to start an argument - I just want to do the right thing by the
> creators of all the software on which mine is built.
>
>
>
> --
> View this message in context:
> http://osgeo-org.1560.x6.nabble.com/License-Summary-tp5006354p5268102.html
> Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
> ___
> 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

Re: [Qgis-developer] Plugin licence

[Tom Chadwin]

Of course, since qgis2web is middleware, its licence also has to be
compatible with Leaflet, Openlayers 3, and their respective plugins, none of
which are GPL. Since the plugin bundles and distributes these libraries, I
would say complying with their licences is of greater importance than
complying with QGIS, which is not distributed with the plugin.

Not trying to start an argument - I just want to do the right thing by the
creators of all the software on which mine is built.



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/License-Summary-tp5006354p5268102.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
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