RE: [binarycloud-dev] LGPL

[Andrew <an...@sa...>]

Alex,

We've run into problems with LGPL adoption with one of our products (iODBC).
This got so bad with larger companies eyeing it suspiciously (because its
legal language is vague as far as how it differs from the GPL, and it could
impose the same 'viral' licensing) that we finally released iODBC under a
BSD license as well.  Not that the situations are identical by any means,
but you may run into problems in the long run with bc adoption in large
companies with legal departments that find LGPL unacceptable.

Best regards,
Andrew Hill
Director of Technology Evangelism
OpenLink Software  http://www.openlinksw.com
Universal Data Access & Data Integration Technology Providers


> -----Original Message-----
> From: bin...@li...
> [mailto:bin...@li...]On Behalf Of alex
> black
> Sent: Thursday, June 14, 2001 12:15 AM
> To: binarycloud-dev
> Subject: [binarycloud-dev] LGPL
>
>
> hi all,
>
> I'm leaning heavily towards releasing all r2 code under the LGPL:
>
> http://www.gnu.org/copyleft/lesser.html
>
> does anyone have opinions on that?
>
> note some stuff:
>     -the r1 license header will be much smaller:
> * -License    LGPL     (http://www.gnu.org/copyleft/lesser.html)
>
>     -all contributors of _complete_ components retain copyright on those
> components. (i.e. you don't get copyright for fixing a bug, :)
>     -all authors who are responsible for 20% or more of a document will be
> credited
>     -all individual authors retain copyright on work
>     -all corporations retain copyright on work.
>
> obviously that assumes that the work is published under the LGPL under the
> auspices of the binarycloud consortium.
>
> -------
>
> The above has a number of ramifications:
>     -modifications to binarycloud core, and some user stuff, if
> distributed,
> must be free (per lgpl)
>     -BUT, unlike r1, no permission from turing is required for
> use, and all
> of the code may be integrated into commercial products _so_long_ as proper
> credit is given. the credit will be to the binarycloud consortium, not
> specific organizations (to avoid the whole
> original-bsd-license-credit-nightmare-list problem.)
>
> this is a significant change, but I think it's appropriate given the
> evolution of the sysem.
>
> please, any and all comments/flames/rants/etc...
>
> _alex
>
>
>
>
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>