From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Charles Cazabon <linux@discworld.dyndns.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: GPL version, "at your option"?
Date: Wed, 17 Nov 2004 15:07:00 +0000 [thread overview]
Message-ID: <1100704019.32698.24.camel@localhost.localdomain> (raw)
In-Reply-To: <20041116144029.GA6740@discworld.dyndns.org>
On Maw, 2004-11-16 at 14:40, Charles Cazabon wrote:
> Also note that the only valid version of the GPL as far as the kernel
> is concerned is _this_ particular version of the license (ie v2, not
> v2.2 or v3.x or whatever), unless explicitly otherwise stated.
Version 2 explicitly states
| Each version is given a distinguishing version number. If the Program
| specifies a version number of this License which applies to it and
"any
| later version", you have the option of following the terms and
conditions
| either of that version or of any later version published by the Free
| Software Foundation. If the Program does not specify a version number
of
| this License, you may choose any version ever published by the Free
Software
| Foundation.
The use of this by some kernel people is to issue "this version only"
licenses is unfortunate, ill advised and potentially harmful. Firstly it
isn't remotely clear what it means because the license itself never
talks about this case, only the "or later" case. Secondly it may force
code chunks to be rewritten if the GPL is modified to fix a legal
problem in future and the original author or their estate or company [*]
cannot be traced. Thirdly it may actually be meaningless anyway - the
GPL doesn't talk about "this version only" in any of its text so it may
be an "additional restriction" and thus a void clause.
Think very hard before you use such a statement and if you do please
ensure it has some kind of "unlocking" clause so that if you can't be
contacted someone you trust (eg Linus) is authorised to make that
decision for you. It would be good if other people who've used this
would also execute such a change with Linus.
Alan
[*] This isn't that silly a situation the kernel community is large
enough that more than one of its contributors is sadly deceased. The
company case is even worse. Tracing company owned code from a defunct
company is nigh on impossible and if you do trace it to an official
receiver or the equivalent (such as a bankruptcy court) they may be
legally obliged to extort as much money as possible from the person
wanting to relicense it.
next prev parent reply other threads:[~2004-11-17 16:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 14:08 GPL version, "at your option"? Fruhwirth Clemens
2004-11-16 14:35 ` Erik Mouw
2004-11-16 14:58 ` Fruhwirth Clemens
2004-11-16 14:40 ` Charles Cazabon
2004-11-17 15:07 ` Alan Cox [this message]
2004-11-17 16:33 ` Michael Poole
2004-11-17 16:09 ` Alan Cox
2004-11-16 14:48 ` Tim Schmielau
2004-11-16 15:46 ` Linus Torvalds
2004-11-17 15:09 ` Alan Cox
2004-11-17 16:28 ` Linus Torvalds
2004-11-17 16:16 ` Alan Cox
2004-11-17 17:59 ` Linus Torvalds
2004-11-17 21:11 ` Jesper Juhl
2004-11-16 15:38 ` James Morris
2004-11-18 1:04 ` David Schwartz
2004-11-18 2:12 ` Kyle Moffett
2004-11-18 2:50 ` Dmitry Torokhov
2004-11-18 3:11 ` Kyle Moffett
2004-11-18 4:54 ` Dmitry Torokhov
2004-11-18 15:46 ` David Schwartz
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=1100704019.32698.24.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@discworld.dyndns.org \
/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