From: visionsofalice@redchan.it
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
rms@gnu.org, bruce@perens.com, moglen@columbia.edu,
bkuhn@sfconservancy.org, editor@lwn.net,
NeilBrown <neil@brown.name>, Laura Abbott <labbott@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
ksummit-discuss@lists.linuxfoundation.org,
Thomas Gleixner <tglx@linutronix.de>,
Olof Johansson <olof@lixom.net>, Chris Mason <clm@fb.com>,
Mishi Choudhary <mishi@linux.com>,
linux-kernel-owner@vger.kernel.org
Subject: Re: The linux devs can rescind their license grant.
Date: Fri, 26 Oct 2018 10:34:02 +0000 [thread overview]
Message-ID: <b97b01e9ff4e2e6f2c6878429f6153ac@redchan.it> (raw)
In-Reply-To: <20181025081911.GB11343@kroah.com>
Yes they can, greg.
The GPL v2, is a bare license. It is not a contract. It lacks
consideration between the licensee and the grantor.
(IE: They didn't pay you, Greg, a thing. YOU, Greg, simply have chosen
to bestow a benefit upon them where they suffer no detriment and you, in
fact, gain no bargained-for benefit)
As a bare license, (read: property license), the standard rules
regarding the alienation of property apply.
Therein: a gratuitous license is revocable at the will of the grantor.
The licensee then may ATTEMPT, as an affirmative defense against your
as-of-right action to claim promissory estoppel in state court, and
"keep you to your word". However you made no such promise disclaiming
your right to rescind the license.
Remeber: There is no utterance disclaiming this right within the GPL
version 2. Linus, furthermore, has chosen both to exclude the "or any
later version" codicil, to reject the GPL version 3, AND to publicly
savage GPL version 3 (he surely has his reasons, perhaps this is one of
them, left unstated). (GPLv3 which has such promises listed (not to say
that they would be effective against the grantor, but it is an attempt
at the least)).
The Software Freedom Conservancy has attempted to mis-construe clause 4
of the GPL version 2 as a "no-revocation by grantor" clause.
However, reading said clause, using plain construction, leads a
reasonable person to understand that said clause is speaking
specifically about the situation where an upstream licensee loses their
permission under the terms due to a violation of the terms; in that case
the down-stream licensee does not in-turn also lose their permission
under the terms.
Additionally, clause 0 makes it crystal clear that "You" is defined as
the licensee, not the grantor. Another issue the SFConservancy's public
service announcement chooses to ignore.
Thirdly, the SFConservancy banks on the ignorance of both the public and
the developers regarding property alienation. A license does not impinge
the rights of the party granting the license in a quid-pro-quo manner
vis a vis the licensee's taking. A license merely grants permission,
extended from the grantor, to the licensee, regarding the article of
property that is being impinged. A license is NOT a full nor is it a
permanent alienation of the article(property) in question. The impinged
property, being under a non bargained-for temporary grant, can be taken
back into the sole dominion of the owner - at his election to do so.
Now as to the 9th circuit appellate court's decision in Jacobsen v.
Katzer . While the court waxes eloquently about opensource licenses,
even mentioning the word "consideration" in it's long dicta, when it
comes time to make the binding decision the court found that the lower
(district) court was in _ERROR_ regarding the application of
contract-law principals to the Artistic License, regarding the case, and
instructed the lower court to instead construe said license as a
Copyright License.
The SFConservancy, and Bruce Perens have chosen to:
1) Rely on the dicta. (non-binding - "some things could be contracts -
opensource is great")
2) Ignore the actual ruling. (Binding - Copyright License - Not
Contract)
3) Ignore that this case was about the AL, not the GPLv2
4) Ignore the existence of different jurisdictions.
(Why file in the roll-the-dice 9th district if you can file in a
district that has personal-juristicion over the defendant and is much
more consistent in it's rulings?)
5) Ignore all established law regard property licensing, contract
formation, meeting of the minds, what consideration is etc.
Which is not surprising considering the desire of people like Bruce
Perens is to rob MEN of EVERY benefit of their Labour and every speck of
happiness in life and to transfer those benefits to WOMEN and those who
support women.
(This is why people who are like Bruce Perens, the SFConservancy
menbers, and the CoC supporters, banned men from taking female children
as brides: in contrivance to the law of YHWH (Devarim chapter 22 - -
verse 28 (na'ar (LXX: padia)), and continue to uphold that ban
world-wide, and seek to destroy ALL cultures that do no bend to their
will.... who are not idolators of Women)
Look, you may love your users, you may love the people who edit your
code in their home or office; but the fact of the matter is...
They have done nothing for you, they have promised nothing to you. They
CANNOT hold YOU.
You have the right to rescind at any time, and remove your work from any
future versions of Linux. And you might consider doing so if YOU are
done harm.
Don't let the insatiable, never-satisfied, public fool you into thinking
otherwise.
And, yes, I am a lawyer.
And, no, unlike the SFConservancy, I did not have to call upon outside
counsel to analyze the fact pattern. (And even then all they could come
up with was statements using weasel words "may" etc: not even wanting to
commit to their clearly-disingenuous publication)
(Note: If you would like to read a nice discussion on the topic, here is
one http://illinoisjltp.com/journal/wp-content/uploads/2013/10/kumar.pdf
)
On 2018-10-25 08:19, Greg Kroah-Hartman wrote:
> On Thu, Oct 25, 2018 at 07:56:26AM +0000, visionsofalice@redchan.it
> wrote:
>> The linux devs can rescind their license grant.
>
> No they can not, please do not keep spreading false information.
>
> greg k-h
next prev parent reply other threads:[~2018-10-26 10:34 UTC|newest]
Thread overview: 177+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 13:49 [Ksummit-discuss] [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document Greg Kroah-Hartman
2018-10-20 13:49 ` Greg Kroah-Hartman
2018-10-20 13:49 ` [Ksummit-discuss] [PATCH 1/7] Code of conduct: Fix wording around maintainers enforcing the code of conduct Greg Kroah-Hartman
2018-10-20 13:49 ` Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 2/7] Code of Conduct Interpretation: Add document explaining how the Code of Conduct is to be interpreted Greg Kroah-Hartman
2018-10-20 13:50 ` Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 3/7] Code of Conduct Interpretation: Properly reference the TAB correctly Greg Kroah-Hartman
2018-10-20 13:50 ` Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 4/7] Code of Conduct: Provide links between the two documents Greg Kroah-Hartman
2018-10-20 13:50 ` Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 5/7] Code of Conduct Interpretation: Put in the proper URL for the committee Greg Kroah-Hartman
2018-10-20 13:50 ` Greg Kroah-Hartman
2018-10-20 19:01 ` [Ksummit-discuss] " Geert Uytterhoeven
2018-10-20 19:01 ` Geert Uytterhoeven
2018-10-21 7:18 ` [Ksummit-discuss] " Greg KH
2018-10-21 7:18 ` Greg KH
2018-10-20 13:51 ` [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address Greg Kroah-Hartman
2018-10-20 13:51 ` Greg Kroah-Hartman
2018-10-20 18:28 ` [Ksummit-discuss] " Alan Cox
2018-10-20 18:28 ` Alan Cox
2018-10-20 18:45 ` [Ksummit-discuss] " Trond Myklebust
2018-10-20 18:45 ` Trond Myklebust
2018-10-20 19:14 ` jonsmirl
2018-10-20 19:14 ` jonsmirl
2018-10-21 8:27 ` Theodore Y. Ts'o
2018-10-21 8:27 ` Theodore Y. Ts'o
2018-10-21 9:23 ` Greg KH
2018-10-21 9:23 ` Greg KH
2018-10-20 19:24 ` Tim.Bird
2018-10-20 19:24 ` Tim.Bird
2018-10-20 20:07 ` Trond Myklebust
2018-10-20 20:07 ` Trond Myklebust
2018-10-21 0:13 ` Alan Cox
2018-10-21 0:13 ` Alan Cox
2018-10-21 6:19 ` Thomas Gleixner
2018-10-21 6:19 ` Thomas Gleixner
2018-10-20 20:13 ` James Bottomley
2018-10-20 20:13 ` James Bottomley
2018-10-20 13:51 ` [Ksummit-discuss] [PATCH 7/7] MAINTAINERS: Add an entry for the code of conduct Greg Kroah-Hartman
2018-10-20 13:51 ` Greg Kroah-Hartman
2018-10-21 21:20 ` [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document NeilBrown
2018-10-21 21:20 ` NeilBrown
2018-10-21 22:26 ` [Ksummit-discuss] " Josh Triplett
2018-10-21 22:26 ` Josh Triplett
2018-10-21 23:37 ` Theodore Y. Ts'o
2018-10-21 23:37 ` Theodore Y. Ts'o
2018-10-23 1:44 ` NeilBrown
2018-10-22 20:26 ` NeilBrown
2018-10-22 20:26 ` NeilBrown
2018-10-22 22:46 ` Theodore Y. Ts'o
2018-10-22 22:46 ` Theodore Y. Ts'o
2018-10-23 1:31 ` NeilBrown
2018-10-23 1:31 ` NeilBrown
2018-10-23 6:26 ` Dan Carpenter
2018-10-23 6:40 ` Al Viro
2018-10-23 6:40 ` Al Viro
2018-10-23 6:46 ` Dan Carpenter
2018-10-23 6:46 ` Dan Carpenter
2018-10-23 3:31 ` Al Viro
2018-10-23 3:31 ` Al Viro
2018-10-23 4:25 ` NeilBrown
2018-10-23 4:25 ` NeilBrown
2018-10-23 4:52 ` Al Viro
2018-10-23 4:52 ` Al Viro
2018-10-23 5:28 ` NeilBrown
2018-10-23 5:28 ` NeilBrown
2018-10-23 6:00 ` Al Viro
2018-10-23 6:00 ` Al Viro
2018-10-23 20:45 ` NeilBrown
2018-10-23 20:45 ` NeilBrown
2018-10-23 8:11 ` Theodore Y. Ts'o
2018-10-23 8:11 ` Theodore Y. Ts'o
2018-10-23 14:22 ` Rainer Fiebig
2018-10-23 14:22 ` Rainer Fiebig
2018-10-23 15:43 ` Theodore Y. Ts'o
2018-10-23 15:43 ` Theodore Y. Ts'o
2018-10-23 17:51 ` Rainer Fiebig
2018-10-23 21:14 ` NeilBrown
2018-10-23 21:14 ` NeilBrown
2018-10-24 12:16 ` Josh Triplett
2018-10-24 12:16 ` Josh Triplett
2018-10-25 21:14 ` NeilBrown
2018-10-25 21:14 ` NeilBrown
2018-10-27 1:10 ` Josh Triplett
2018-10-27 1:10 ` Josh Triplett
2018-10-28 21:48 ` NeilBrown
2018-10-28 21:48 ` NeilBrown
2018-11-01 16:45 ` Paul E. McKenney
2018-11-01 16:45 ` Paul E. McKenney
2018-11-01 21:11 ` Josh Triplett
2018-11-01 21:11 ` Josh Triplett
2018-11-02 13:13 ` Paul E. McKenney
2018-11-02 13:13 ` Paul E. McKenney
2018-11-01 21:50 ` NeilBrown
2018-11-02 13:33 ` Paul E. McKenney
2018-11-02 13:33 ` Paul E. McKenney
2018-11-03 8:36 ` NeilBrown
2018-11-03 8:36 ` NeilBrown
2018-11-03 17:37 ` Paul E. McKenney
2018-11-03 17:37 ` Paul E. McKenney
2018-11-03 21:06 ` NeilBrown
2018-11-03 21:06 ` NeilBrown
2018-11-03 22:23 ` Paul E. McKenney
2018-11-03 22:23 ` Paul E. McKenney
2018-11-02 13:52 ` James Bottomley
2018-11-03 9:19 ` Eric S. Raymond
2018-11-04 10:35 ` Geert Uytterhoeven
2018-11-04 10:35 ` Geert Uytterhoeven
2018-10-21 22:33 ` Joe Perches
2018-10-21 22:33 ` Joe Perches
2018-10-21 22:37 ` Randy Dunlap
2018-10-21 22:37 ` Randy Dunlap
2018-10-22 9:09 ` Rainer Fiebig
2018-10-22 9:09 ` Rainer Fiebig
2018-10-22 11:02 ` [Ksummit-discuss] " James Bottomley
2018-10-22 11:02 ` James Bottomley
2018-10-24 8:49 ` Laura Abbott
2018-10-24 8:49 ` Laura Abbott
2018-10-25 7:56 ` The linux devs can rescind their license grant visionsofalice
2018-10-25 8:19 ` [Ksummit-discuss] " Greg Kroah-Hartman
2018-10-25 8:19 ` Greg Kroah-Hartman
2018-10-25 19:39 ` Eric S. Raymond
2018-10-25 20:47 ` [Ksummit-discuss] " Theodore Y. Ts'o
2018-10-25 20:47 ` Theodore Y. Ts'o
2018-10-25 21:41 ` Eric S. Raymond
2018-10-25 22:12 ` [Ksummit-discuss] " NeilBrown
2018-10-25 22:12 ` NeilBrown
2018-10-25 22:38 ` Eric S. Raymond
2018-10-25 22:52 ` [Ksummit-discuss] " NeilBrown
2018-10-25 22:52 ` NeilBrown
2018-11-04 10:47 ` [Ksummit-discuss] " Geert Uytterhoeven
2018-11-04 10:47 ` Geert Uytterhoeven
2018-10-25 23:06 ` Al Viro
2018-10-25 23:06 ` Al Viro
2018-10-26 2:28 ` Eric S. Raymond
2018-10-26 5:49 ` [Ksummit-discuss] " Al Viro
2018-10-26 5:49 ` Al Viro
2018-10-27 6:52 ` visionsofalice
2018-10-27 7:32 ` [Ksummit-discuss] " Al Viro
2018-10-27 7:32 ` Al Viro
2018-10-27 16:18 ` [Ksummit-discuss] " Tim.Bird
2018-10-27 16:18 ` Tim.Bird
2018-10-27 22:09 ` Jiri Kosina
2018-10-27 22:09 ` Jiri Kosina
[not found] ` <CAK2MWOtNUTjWy5pTcGco5DNurqNCc=9CfDJ-Ko-K+6HDC55ikg@mail.gmail.com>
2018-10-27 23:07 ` Eric S. Raymond
2018-10-27 23:40 ` Al Viro
2018-10-27 23:40 ` Al Viro
2018-10-28 21:13 ` NeilBrown
2018-10-28 21:13 ` NeilBrown
2018-10-25 23:32 ` Iván Chavero
2018-10-26 13:15 ` Eben Moglen
2018-10-26 15:50 ` Eric S. Raymond
2018-10-26 15:53 ` Eben Moglen
2018-10-26 17:32 ` visionsofalice
2018-10-26 18:31 ` Eben Moglen
2018-10-27 7:12 ` visionsofalice
2018-12-18 18:53 ` The linux devs can rescind their license grant. - Analysis published? visionsofalice
2018-10-26 10:34 ` visionsofalice [this message]
2018-10-29 22:31 ` [Ksummit-discuss] The linux devs can rescind their license grant Bradley M. Kuhn
2018-10-29 22:31 ` Bradley M. Kuhn
2018-12-18 19:17 ` visionsofalice
2018-10-27 5:04 ` The linux devs can rescind their license grant. - Additional restrictive terms visionsofalice
2018-12-18 20:55 ` The CoC regime is a License violation " visionsofalice
2018-12-19 1:17 ` visionsofalice
2018-12-23 16:05 ` visionsofalice
2018-10-25 22:02 ` [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document NeilBrown
2018-10-25 22:02 ` NeilBrown
2018-10-25 8:06 ` [Ksummit-discuss] " Pavel Machek
2018-10-25 8:06 ` Pavel Machek
2018-10-25 11:20 ` Rainer Fiebig
2018-10-25 22:18 ` [Ksummit-discuss] " NeilBrown
2018-10-25 22:18 ` NeilBrown
2018-10-26 8:33 ` Rainer Fiebig
2018-10-26 22:40 ` [Ksummit-discuss] " NeilBrown
2018-10-26 22:40 ` NeilBrown
2018-10-27 11:49 ` Rainer Fiebig
2018-10-21 23:36 ` Eric S. Raymond
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=b97b01e9ff4e2e6f2c6878429f6153ac@redchan.it \
--to=visionsofalice@redchan.it \
--cc=bkuhn@sfconservancy.org \
--cc=bruce@perens.com \
--cc=clm@fb.com \
--cc=editor@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=labbott@redhat.com \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mishi@linux.com \
--cc=moglen@columbia.edu \
--cc=neil@brown.name \
--cc=olof@lixom.net \
--cc=rms@gnu.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.