<div dir="ltr"><br><br><div class="gmail_quote">On Thu, Oct 2, 2008 at 3:12 AM, Jeremy O'Donoghue <span dir="ltr"><<a href="mailto:jeremy.odonoghue@gmail.com">jeremy.odonoghue@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
On Tue, 30 Sep 2008 21:54:34 -0400, "Stefan Monnier"<br>
<<a href="mailto:monnier@iro.umontreal.ca">monnier@iro.umontreal.ca</a>> said:<br>
> > I am not allowed to use such an interpretation. The (expensive and very<br>
> > carefully researched) legal advice used to shape the use of Open Source<br>
> > code at my employer has resulted in a "no LGPL under any circumstances<br>
> > whatsoever" policy.<br>
> [...]<br>
> > That still leaves anyone free to use LGPL if they want to, but please<br>
> > don't assume that it allows commercial use by all potential users.<br>
><br>
> It *does* allow commercial use. Your example just shows that some<br>
> people may decide not to take advantage of it, based not on problematic<br>
> restrictions but just on paranoia.<br>
<br>
The LGPL does not state that a "work that uses the library" may be<br>
distributed<br>
in conjunction with a closed source commercial program, although I grant<br>
that<br>
many (presumably including some who have actually consulted lawyers)<br>
believe<br>
that such an interpretation is reasonable.</blockquote><div><br></div><div>I believe the LGPL states that mere aggregation doesn't indicate derivative works. In fact commercial video games have been distributed for linux that used the SDL library that I used to work with myself in a former life.</div>
<div><br></div><div>So I think we should all speak to our lawyers before assuming how it can be used. The GPL and LGPL are needlessly difficult for mere mortals to understand in their entirety, and as you've alluded to, many lawyers would interpret it differently. I suspect many different judges would too.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<br>
However, the policy in place in my workplace was designed by lawyers<br>
familiar<br>
with contract law in multiple jurisdictions worldwide. I may not<br>
personally<br>
agree with their conclusions in every respect, but I'd be hard pressed<br>
to<br>
consider them "paranoid" - they are simply doing their job, and have<br>
concluded<br>
that the potential risk of a court somewhere in the World taking an<br>
aggressive<br>
view of the provisions of clause 5 is unacceptable.<br>
<br>
I guess what I really mean is that if you choose LGPL as a license, some<br>
people<br>
who would like to use it in commercial products will do so, but others<br>
(who would<br>
have chosen to use the work if differently licensed) will not. Not a<br>
question of<br>
paranoia so much as corporate appetite for license risk.</blockquote><div><br></div><div>Yes, there's enough anti-GPL or GPL derived momentum in many places that I must say that using the LGPL or GPL would be highly frowned upon at my workplace as well. </div>
<div><br></div><div>That said, I'm a huge fan of apache, BSD, MIT and Perl's licenses :-)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<br>
Regards<br>
Jeremy<br>
<font color="#888888">--<br>
Jeremy O'Donoghue<br>
<a href="mailto:jeremy.odonoghue@gmail.com">jeremy.odonoghue@gmail.com</a><br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</div></div></blockquote></div><br></div>