public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Hugues Talbot <Hugues.Talbot@csiro.au>
To: pthreads-win32@sources.redhat.com
Subject: Re: License wars
Date: Mon, 20 Oct 2003 23:28:00 -0000	[thread overview]
Message-ID: <200310202328.h9KNSO0D017343@darkside-nh.nsw.cmis.csiro.au> (raw)
In-Reply-To: Your message of Mon, 20 Oct 2003 17:01:04 +0200. <OFE4CED3AF.97140388-ONC1256DC5.005001CC-C1256DC5.00527804@de.ibm.com>


Dear Alexander,

There is no point in getting angry like that. What you call
`collective work' is not what the FSF defines as collective, 
the LGPL lumps a great deal under the term `derivative work'. 
That term has not been tested in court with respect to the LGPL 
so there is no certainty about who is right, you or the FSF 
laywers. Straight logic does not apply necessarily in court 
decisions. A lot of people may not like it but that's the way 
it is. Whether or not the FSF has a leg to stand on is open 
to debate but this is not the point.

Yes I agree with you that the LGPL restricts more than the CPL
or the BSD or the Mozilla license, that much is obvious. My 
point is that the LGPL is a strong license which may not be
as business-friendly as other licenses, but it does have some
bite. My impression is that the CPL is unenforceable whereas
the LGPL has been enforced successfully several times already.
Most recently there was a article in Forbes magazine about it.

It's a bit like patents. There is zero point in taking a patent
if you are not willing to go to court to defend it. Same here.
If you are quite prepared for anybody to do anything they want
with your code then the choice of license does not matter.
If you want to defend your code against exploitation then 
as an individual or a collection of individuals with little means
there is little choice, and the CPL is probably not one of them,
although I would welcome news to the contrary.

Note that the BSD license is very business-friendly and has been
actually court-tested successfully, something the (L)GPL cannot
claim. However as you know the BSD license protects little.

Finally if the copyright holders of the pthread-win32 library 
decide the LGPL is unacceptable they can change it, but this is 
not for me or you to have the last word.

If you are trying to have a constructive debate about this 
treating people like idiots is not the way to go.



--------
Hugues Talbot, CSIRO Mathematical & Information Sciences
Locked Bag 17, Building E6B, Macquarie University  North Ryde  
NSW  2113  Australia           Ph: 61 2 9325 3208 Fax: 61 2 9325 3200

63% of all statistics are made up on the spot.

















  reply	other threads:[~2003-10-20 23:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20 12:45 Hugues Talbot
2003-10-20 15:01 ` Alexander Terekhov
2003-10-20 23:28   ` Hugues Talbot [this message]
2003-10-21 10:07     ` Alexander Terekhov
2003-10-20 15:10 ` Phil Frisbie, Jr.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200310202328.h9KNSO0D017343@darkside-nh.nsw.cmis.csiro.au \
    --to=hugues.talbot@csiro.au \
    --cc=pthreads-win32@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).