public inbox for
 help / color / mirror / Atom feed
From: "Alexander Terekhov" <>
Subject: changing pthreads-win32 license
Date: Mon, 20 Oct 2003 10:06:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Ross Johnson wrote:
> But, before guessing, I have to ask you what your issue is 
> exactly with the LGPL. 

My issue with [L]GPL is that FSF "advocates" totally idiotic
("SCOish" so to speak) notion of "derivative work", to begin 
with. This is just one example:

"Subclassing is creating a derivative work. Therefore, the 
 terms of the GPL affect the whole program where you create 
 a subclass of a GPL'ed class. "

Of course, this doesn't make sense and is totally wrong.  The 
real problem with [L]GPL is that both try to go "way too far" 
with the reciprocity provision (quote taken from LGPL, emphasis
added): "the intent is to exercise the right to control the 
distribution of derivative or COLLECTIVE works based on the 
Library". This is what people call "viral effect". Even folks

The problems with [L]GPL are nicely illustrated here:

and also here:

Now, as for *L*GPL silliness, just read this:

> And especially which license you'd prefer to use. 

The CPL, of course.

I like this:

"The Lesser GPL used to be called the Library GPL. For 
 historical reasons this license still refers to the software 
 application as "the Library" which can be confusing for 
 licensees. Also, a licensee is allowed to convert the Lesser 
 GPL to a full GPL, after which their enhancements could not 
 be incorporated back into our version of the software. So, 
 for us, LGPL is out. "

Please read this:

> There have been a few expressions of interest in changing to 
> another license, such as the BSD license. 

Fine with me. Just take the CPL and remove the reciprocity 

"Reciprocal and non-reciprocal open source licenses ought to 
 be the same -- except with respect to provisions dealing with 

Well, I'd have no real problems with the AFL/OSL either, but 
to me, the CPL is better. I like the language/style, to begin 
with. ;-)

> In order to change, I think a concensus of [at least] the major 
> project contributors would be required. 

I think that all contributors will have to agree to license 
their contributions under the new terms in order to change the 

> It's certainly not up to me.

I understand. That's why I'm replying to the list.


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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2003-10-20 10:06 ` Alexander Terekhov [this message]
2003-10-30  7:03   ` Ross Johnson
2003-10-30  9:51     ` Alexander Terekhov
2003-10-30 10:49       ` Will Bryant
2003-10-30 11:17         ` changing pthreads-win32 license - Practical Comment James Ewing
2003-10-30 11:46         ` changing pthreads-win32 license Alexander Terekhov
2003-10-30 13:14           ` UNSUBCRIBE Geoffrey Atkinson
2003-10-31  7:00           ` changing pthreads-win32 license Ross Johnson
2003-10-31 10:56             ` Alexander Terekhov
2003-10-31 16:27             ` 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:

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

  git send-email \ \ \ \

* 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).