[Qgis-psc] Licenses stuff was: Re: [Qgis-developer] one email address for plugin approvers

[Richard Duivenvoorde]

On 13-02-14 12:22, Vincent Picavet wrote:

> [...]
>> - has a proper license (???? which one? and info about that??)
> 
> There is no choice on the licence a plugin can be distributed under : a python 
> import is considered a link, therefore the "import qgis.core" is enough to 
> propagate the GPL licence to the plugin.
> There may be some other files under different licences though, namely sample 
> data, documentation or whatever else is not concerned by the link and GPL 
> "contamination".

Hi Vincent,

I've seen license related questions before on lists, and you seem to be
pretty into this :-)

Is it an idea, and do you have some time, to write a some text about this.

We often been asked questions like:

-1- can we build a custom QGIS installer with our own logo

-2- can we create a Python plugin and make it (commercially) available

-3- can we create a plugin which in turn calls a proces on a
(commercial) application

- ... some more examples here

It would be good if we had a page in the website for this. So we are
clear that (I think):

- You can create a QGIS installer and even sell it as long as you make
installer sources available (as these become also GPL ??)

- You can create a commercial plugin, BUT the code is GPL and should be
available (import qgis.core == propagation)

- You can create a QGIS plugin which in turn calls webservices or native
apps via subprocess.call (as this is not linking)

With some additional information so the average manager does not get
scared...

If you do not have time, I'll put text above in the website somewhere.
Please correct me if I'm wrong there.

Regards,

Richard Duivenvoorde