[OSGeo-Discuss] GIS_Libraries

Tue May 5 10:02:39 PDT 2009

On Tue, May 05, 2009 at 11:55:47AM -0500, P Kishor wrote:
> On Tue, May 5, 2009 at 11:33 AM, Daniel Ames <amesdani at isu.edu> wrote:
> > IANAL either, but I do read wikipedia. So by way of clarification...
> > Everything I've read makes a clear distinction between GPL and LGPL such
> > that GPL code can not be embedded in or linked to a closed source
> > application. Period. Whereas L-GPL licensed code can be linked to a closed
> > source application.
> > See: http://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License
> > So if the individual wants to link to GPL licensed code/libraries and is
> > willing to make his code GPL then fine. He can still run a commercial
> > business based on this code, as many people do.
> > But if he wants to keep his code under some closed-source license then he
> > can not link to or embed any GPL licensed code or library.
> 
> Thanks Dan (and Christopher and others), I see the distinction now
> between GPL and LGPL. However, I am reading the actual GPL text and
> its extensive FAQ, instead of Wikipedia's interpretation of it, to try
> and sift through all the variations and exceptions to better
> understand this now. Hopefully I will come out better informed from
> this process. In the meantime, the distinction that you point out
> between GPL and LGPL makes sense.

http://www.fsf.org/licensing/licenses/gpl-faq.html#LinkingWithGPL

"The combination itself is then available under those GPL versions."

-- Chris

> All that said, please note that GPL does not prevent anyone from
> commercializing any technology, and that was the thrust of the
> original question, if I recall correctly, although, the OP
> specifically asked for only LGPL technology, so GPL was out anyway. In
> that sense, LGPL is compatible with GPL, but GPL is not compatible
> with LGPL.
> 
> In any case, all the more reason to consult an actual lawyer before
> setting out to do a commercial venture, or, be prepared to make money
> while openly sharing your code. Nothing to hide is always the better
> policy, or, at least the more headache-free policy.
> 
> 
> 
> 
> 
> > - Dan
> >
> >
> > On Tue, May 5, 2009 at 10:24 AM, P Kishor <punk.kish at gmail.com> wrote:
> >>
> >> On Tue, May 5, 2009 at 11:06 AM, Daniel Ames <amesdani at isu.edu> wrote:
> >> > Nenad,
> >> > The OSGeo projects use a variety of licenses. You'll see LGPL, MPL, GPL,
> >> > MIT, and others. If you are developing commercial tools, you'll need to
> >> > avoid GPL (someone correct me if I'm wrong.)
> >>
> >> ----
> >> Disclaimer: IANAL. Get legal advice from your lawyer before embarking
> >> on your million dollar enterprise.
> >> ----
> >>
> >> I'll correct you, because, as stated above, you are misrepresenting at
> >> best, and wrong at worst. ;-)
> >>
> >> GPL does not prevent you from making money. GPL only requires that if
> >> you modify the code that is under GPL, then you must redistribute the
> >> modified code under GPL. Granted this may not be easy to figure out in
> >> real world scenarios, but consider the following --
> >>
> >> Let's say ShapeLib is published under GPL (I don't know whether or not
> >> it is; this is only for illustration purpose). Let's say, MapServer
> >> utilizes ShapeLib, but doesn't modify ShapeLib, but uses ShapeLib as
> >> is. Let's say, MapServer's creator decides to make millions off of
> >> MapServer, Inc. He is under no obligation to release the source code
> >> of MapServer, but he is obligated to release the source code of
> >> ShapeLib, which is no big deal, because the source code of ShapeLib is
> >> already available to anyone.
> >>
> >> On the other hand, let's say, ShapeLib is modified to perform better,
> >> or differently, for MapServer. Now, there is an obligation to release
> >> the source code to the modified version of ShapeLib no matter what the
> >> value of that value-added might be. That is what the GPL obligates.
> >> MapServer itself is still governed by whatever license that its
> >> creator decides to apply.
> >>
> >>
> >> > Also take into consideration development platform/language.
> >> > My group (MapWindow project) has a number of people using our GIS SDK
> >> > for
> >> > commercial applications in the .NET platform. MapWindow is licensed
> >> > under
> >> > MPL 1.1 which supports commercial usage.
> >> > Dan
> >> >
> >> > On Tue, May 5, 2009 at 7:07 AM, Nenad Milasinovic
> >> > <nenad.milasinovic at zesium.com> wrote:
> >> >>
> >> >> Hello,
> >> >>
> >> >> I am interested is there any reliable open source, LGPL licensed GIS
> >> >> SDK
> >> >> or library suited for building commercial, platform independent GIS
> >> >> application on top of it.
> >> >> I am also interested for commercial solutions but only as SDK or
> >> >> library.
> >> >> I will appreciate any help.
> >> >>
> >> >> Best regards.
> >> >>
> >> >> --
> >> >> Nenad Milasinovic
> >> >> Software Development and Testing
> >> >>
> >> >> ---
> >> >>
> >> >> "ZESIUM mobile" d.o.o.
> >> >> Valentina Vodnika 8/9
> >> >> 21000 Novi Sad
> >> >> Serbia
> >> >> Tel: +381 (0)21 472 15 48
> >> >> Fax: +381 (0)21 472 15 49
> >> >> Mob: +381 (0)61 231 41 20
> >> >> E-mail: nenad.milasinovic at zesium.com
> >> >>
> >> >> _______________________________________________
> >> >> Discuss mailing list
> >> >> Discuss at lists.osgeo.org
> >> >> http://lists.osgeo.org/mailman/listinfo/discuss
> >> >
> >> >
> >> > _______________________________________________
> >> > Discuss mailing list
> >> > Discuss at lists.osgeo.org
> >> > http://lists.osgeo.org/mailman/listinfo/discuss
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Puneet Kishor http://www.punkish.org/
> >> Carbon Model http://carbonmodel.org/
> >> Charter Member, Open Source Geospatial Foundation http://www.osgeo.org/
> >> Science Commons Fellow, Geospatial Data http://sciencecommons.org
> >> Nelson Institute, UW-Madison http://www.nelson.wisc.edu/
> >> -----------------------------------------------------------------------
> >> collaborate, communicate, compete
> >> =======================================================================
> >> Sent from Madison, WI, United States
> >> _______________________________________________
> >> Discuss mailing list
> >> Discuss at lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/discuss
> >
> >
> _______________________________________________
> Discuss mailing list
> Discuss at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/discuss

-- 
Christopher Schmidt
Web Developer