<div>I already tried the LGPL thing a while back [0] :)</div><div><br></div><div>[0] <a href="http://www.osgeo.org/pipermail/qgis-developer/2011-November/016741.html">http://www.osgeo.org/pipermail/qgis-developer/2011-November/016741.html</a></div>
<div><br></div><div>- Nathan</div><br><div class="gmail_quote">On Mon, Mar 26, 2012 at 9:02 PM, Vincent Picavet <span dir="ltr"><<a href="mailto:vincent.ml@oslandia.com">vincent.ml@oslandia.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Giovanni,<br>
<br>
Le lundi 26 mars 2012 12:45:39, G. Allegri a écrit :<br>
<div><div class="h5">> I had to create a python plugin to obatin some interactions with the ESRI<br>
> ArcGIS Geoprocessing python framework. To do that, I need to import ESRI's<br>
> libraries in my plugin, which are clearly not GLP'd :)<br>
> Following a previous thread on this topic, I wonder if it's legal from the<br>
> side of QGis (obviously it is ok from the ArcGIS's side having a licence<br>
> for it).<br>
<br>
</div></div>From my point of view, after researches about this specific issue, you can't<br>
legally :<br>
<a href="http://gis.stackexchange.com/questions/19646/issues-with-osgeo-qgis-core-and-
arcpy-modules/19661#19661" target="_blank">http://gis.stackexchange.com/questions/19646/issues-with-osgeo-qgis-core-and-<br>
arcpy-modules/19661#19661</a><br>
<br>
GPL is a copyleft licence, therefore «contamining» other libraries. All<br>
software piece which is linked to a GPL library must have a licence compatible<br>
with GPL.<br>
An python «import» is considered as a link.<br>
<br>
I would advise you to change your software to adopt a loose coupling strategy<br>
between the qgis part and the esri part, either through web services, data<br>
exchange over a file or a database or something else not considered as a link<br>
in the GPL sense.<br>
<br>
I personnaly consider that libraries should not be under a GPL licence but a<br>
LGPL one, which keeps the opensource aspect while facilitating mixing with<br>
other softwares. GPL is fine with end user software built on top of LGPL libs.<br>
That said, it would require to relicence all qgis source code as LGPL with all<br>
contributors agreeing to the change.<br>
And this is only my personal view, I do not want to start a licence troll<br>
thread.<br>
<br>
Vincent<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">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>
</blockquote></div><br>