public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: "Alexander Terekhov" <TEREKHOV@de.ibm.com>
To: pthreads-win32@sources.redhat.com
Subject: Re: License wars
Date: Mon, 20 Oct 2003 15:01:00 -0000	[thread overview]
Message-ID: <OFE4CED3AF.97140388-ONC1256DC5.005001CC-C1256DC5.00527804@de.ibm.com> (raw)
In-Reply-To: <20031020124511.BA246D8@murray.nsw.cmis.CSIRO.AU>

Hugues Talbot wrote:
[...]
> The CPL does not spell what a derivative work is.

Because that's defined in the copyright statute and, to some 
extent, in the case law.

> Is it anyone's guess ? do you have to be a copyright laywer 
> to have some opinion on this?

It surely won't hurt. ;-)

http://digital-law-online.info/lpdi1.0/treatise27.html
http://www.pbwt.com/Attorney/files/ravicher_1.pdf
http://www.rosenlaw.com/html/GL18.pdf

> You may not agree with the LGPL definition of a derivative 
> work but at least it's there.

Really?

<quote source=http://www.gnu.org/licenses/lgpl.txt>

A "work based on the Library" means either the Library or any 
derivative work under copyright law: that is to say, a work 
containing the Library or a portion of it, either verbatim or 
with modifications and/or translated straightforwardly into 
another language.

</quote>

Translation: "we're going to impose restrictions on BOTH 
derivative AND COLLECTIVE works (if you distribute them) and 
now see the copyright statute and check also the case law if 
you don't understand the legal meaning of 'derivative works' 
and 'collective works' in software".

What do you NOT understand here? My problem is NOT related
to the "share-alike" provisions for derivative works. The
CPL does have it too. My problem with [L]GPL is that [L]GPL 
imposes restrictions on the "entire" COLLECTIVE works... 
including non-derivative "constituents". Do you get it now?

regards,
alexander.

P.S. I'm NOT speaking for IBM here. "My own opinions; and in 
no way reflect official opinion or policy of IBM Corp". Okay?


Sent by:        pthreads-win32-owner@sources.redhat.com
To:     pthreads-win32@sources.redhat.com
cc:      
Subject:        License wars



Dear Alexander,

The LGPL's intention is to let people use Free software into
proprietary code as long as they go through some slightly annoying
hoops, while ensuring that the Free software itself remains Free. I
think this is what we want (in broad terms).

Now I've scanned through the CPL and it does not seem to protect the
Free software in any way that is clearly spelled.  The LGPL says that
if you modify the original Free software then your modification must
also be Free. The CPL does not spell what a derivative work is. Is 
it anyone's guess ? do you have to be a copyright laywer to have some
opinion on this?

You may not agree with the LGPL definition of a derivative work but at
least it's there.

I don't want to go into any kind of religious war on licenses, but the
(L)GPL has been enforced several times by the FSF, so far no one has
dared or found it worthwhile to go to court, maybe it is `idiotic' in
your own words but it seems to be somewhat effective.

The FSF has stated several times that they would help anyone wishing
to enforce the (L)GPL on their own software. Can we expect the same
service from IBM, should someone infringe on the CPL?

The point of a Free Software license is to grand some rights and have
some protection. The CPL does the first part all right, I'm not
sure about the second, sorry.


--------
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

Verbing weirds language -- Calvin


  reply	other threads:[~2003-10-20 15:01 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 [this message]
2003-10-20 23:28   ` Hugues Talbot
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=OFE4CED3AF.97140388-ONC1256DC5.005001CC-C1256DC5.00527804@de.ibm.com \
    --to=terekhov@de.ibm.com \
    --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).