From: missingterms@redchan.it
To: linux-kernel@vger.kernel.org, debian-user@lists.debian.org
Cc: rms@gnu.org, bruce@perens.com, esr@thyrsus.com,
moglen@columbia.edu, bkuhn@sfconservancy.org, editor@lwn.net,
torvalds@osdl.org, tcallawa@redhat.com
Subject: The GPLv2 is not a contract, it is a revocable license.
Date: Sun, 14 Oct 2018 21:35:15 +0000 [thread overview]
Message-ID: <70c37b00a9e93567059fdc55629ddbd5@redchan.it> (raw)
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
The GPLv2 is not a contract, it is a revocable license.
Enjoy the read:
http://illinoisjltp.com/journal/wp-content/uploads/2013/10/kumar.pdf
(With full citations).
(PDF attached)
Page 12 starts the relevant discussion.
Page 16 gives the rundown on all the ways the GPL is not a contract.
Later there is a short gloss of state law promissory estopple doctrines,
but remember: in the case of the linux kernel it, unlike other projects,
omitted the "or any later version" codicil, and is only under version 2
of the GPL, which makes no promise of irrevocability by grantor.
(Note: The SFConservancy conflates clauses that clarify that if a
licensee's license is automatically revoked for a GPL violation, that
sub-licensees licenses are not-in-turn automatically revoked)
(Additionally: Clause 0 of GPLv2 specifically defines the "you" in said
clauses as referring to the licensee (not the grantor), so the
SFConservancy's conflation is shown to be ever more disengenious)
(Little more that a hope and a prayer to the wind)
So: Not a contract. Is a bare license akin to a property license. And
there is no "irrevocable by grantor" promise in v2. .: Can be rescinded
at will.
[-- Attachment #2: kumar-gpl-licenses.pdf --]
[-- Type: application/pdf, Size: 261499 bytes --]
next reply other threads:[~2018-10-14 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-14 21:35 missingterms [this message]
2018-10-15 8:32 svasthree
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=70c37b00a9e93567059fdc55629ddbd5@redchan.it \
--to=missingterms@redchan.it \
--cc=bkuhn@sfconservancy.org \
--cc=bruce@perens.com \
--cc=debian-user@lists.debian.org \
--cc=editor@lwn.net \
--cc=esr@thyrsus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moglen@columbia.edu \
--cc=rms@gnu.org \
--cc=tcallawa@redhat.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®