Ok, going through hyopthesis things are getting clear. I have answered Vincent o the other thread:<div>my plugin is ok until it doesn't load something proprietary in its process space. As soon as it happens I must be able to provide the source of every code running in the same process.</div>
<div><br></div><div>giovanni</div><br><div class="gmail_quote">2012/3/26 G. Allegri <span dir="ltr"><<a href="mailto:giohappy@gmail.com">giohappy@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><br><div class="gmail_quote"><div class="im">2012/3/26 Alex Mandel <span dir="ltr"><<a href="mailto:tech_dev@wildintellect.com" target="_blank">tech_dev@wildintellect.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
More specifically here's the compatibility list:<br>
<a href="http://www.gnu.org/licenses/license-list.html" target="_blank">http://www.gnu.org/licenses/license-list.html</a><br>
<br>
"MIT" -Expat or X11, most BSD, Apache 2, LGPL are all on the ok list.<br>
<br>
^^^ This does not apply to plugins of QGIS which as a technical<br>
necessity must import QGIS. It does apply to libraries that QGIS wishes<br>
to include and import into QGIS.<br></blockquote><div><br></div></div><div>Exactly, indeed my plugin will be GPL, and will be distributed as it is. How could someone argue that it's illegal? I don't ditribute non-GPL code with it...</div>
<div><br></div><div>giovanni</div><div><div class="h5"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Enjoy,<br>
Alex<br>
<div><div><br>
On 03/26/2012 12:40 PM, Alex Mandel wrote:<br>
> SEXTANTE just needs to be a GPL compatible license, it does not need to<br>
> be GPL itself, though the copy distributed with QGIS will be treated as<br>
> GPL. (In effect it ends up being like a dual license).<br>
><br>
> See the diagram on <a href="http://www.gnu.org/licenses/quick-guide-gplv3.html" target="_blank">http://www.gnu.org/licenses/quick-guide-gplv3.html</a><br>
><br>
> I would recommend LGPL otherwise people writing the SEXTANTE plugin for<br>
> Arc might run into trouble. This would provide flexibility in what<br>
> applications can use the library (much the way gdal/ogr shows up<br>
> everywhere).<br>
><br>
> This is quite different than the other issue being discussed which is<br>
> the import of Arc into a QGIS plugin. To be clear yes people can do such<br>
> things, and could import proprietary applications into their plugins,<br>
> they just can't legally distribute it outside their company.<br>
><br>
> Thanks,<br>
> Alex<br>
><br>
> On 03/26/2012 05:26 AM, G. Allegri wrote:<br>
>> I would keep it LGPL. I'm not interested in wrapping it in proprietary<br>
>> code, but to use proprietary code through SEXTANTE...<br>
>><br>
>> giovanni<br>
>><br>
>> 2012/3/26 Peter Borissow <<a href="mailto:peter.borissow@yahoo.com" target="_blank">peter.borissow@yahoo.com</a>><br>
>><br>
>>> Do you need to GPL all of SETANTE or just the glueware (e.g. QGIS plugin)?<br>
>>> In otherwords, is there a way to keep the SEXTANTE core MIT or LGPL?<br>
>>><br>
>>><br>
>>> ------------------------------<br>
>>> *From:* Victor Olaya <<a href="mailto:volayaf@gmail.com" target="_blank">volayaf@gmail.com</a>><br>
>>> *To:* <a href="mailto:cavallini@faunalia.it" target="_blank">cavallini@faunalia.it</a><br>
>>> *Cc:* <a href="mailto:qgis-developer@lists.osgeo.org" target="_blank">qgis-developer@lists.osgeo.org</a><br>
>>> *Sent:* Monday, March 26, 2012 6:10 AM<br>
>>> *Subject:* Re: [Qgis-developer] Directions needed for GSOC Proposal<br>
>>><br>
>>> Then, I guess there is no discussion. As I said, in this case there is<br>
>>> no difference from my point of view, so GPL is a good option for<br>
>>> SEXTANTE<br>
>>><br>
>>> Regards<br>
>>><br>
><br>
> _______________________________________________<br>
> Qgis-developer mailing list<br>
> <a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</div></div></blockquote></div></div></div><br>
</blockquote></div><br>