From: clarityabovecompulsion@firemail.cc
To: linux-kernel@vger.kernel.org
Subject: On default rules, and license given.
Date: Tue, 02 Oct 2018 06:14:18 +0000 [thread overview]
Message-ID: <62cb727b231c4c9f257ed1656476d7d3@firemail.cc> (raw)
> by jd ( 1658 ) <`imipak' `at' `yahoo.com'> on Saturday September 29,
> 2018 @02:38PM (#57395698) Homepage Journal
> The author has no right granted by the GPL to revoke the freedoms of
> others. Indeed, the GPL is explicit. Nobody, not even the author, can
> remove the freedom of another.
You're completely wrong. The rule is not "If the GPL doesn't grant the
copyright holder this, he may not do it".
The rule is "The licensee only has the privileges bestowed upon him that
the owner of the property has granted"
Do you understand that? No. Thought not.
Version 2 of the GPL bares no "irrevocability by grantor" clause,
specifies no duration, and the "You" it speaks of (cited by the
SFConservancy.org) is explicitly declared to be the licensee in section
0 (not the copyright holder, as the SFConservancy tries to argue).
Here's some lay-mans reading for you:
Licenses and revocability, in a paragraph or less.
As has been stated in easily accessible terms elsewhere:
"Most courts hold that simple, non-exclusive licenses with unspecified
durations that are silent on revocability are revocable at will. This
means that the licensor may terminate the license at any time, with or
without cause." +
Version 2 of the GPL specifies no duration, nor does it declare that it
is non-revocable by the grantor.
(Also note: A perpetual license may violate the rule against
perpetuities in various jurisdictions where it is applied not only to
real property but additionally to personal property (and the like),
which is why the GPL-3's term of duration is set as the duration of
copyright on the program (and not "forever"))
+[https://www.sidley.com/en/insights/newsupdates/2013/02/the-terms-revocable-and-irrevocable-in-license-agreements-tips-and-pitfalls]
reply other threads:[~2018-10-02 6:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=62cb727b231c4c9f257ed1656476d7d3@firemail.cc \
--to=clarityabovecompulsion@firemail.cc \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).