linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: visionsofalice@redchan.it
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: esr@thyrsus.com, "Theodore Y. Ts'o" <tytso@mit.edu>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	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: Sat, 27 Oct 2018 06:52:44 +0000	[thread overview]
Message-ID: <75eb4a46c8a2c1d4a927760fd1f2009d@redchan.it> (raw)
In-Reply-To: <20181025230656.GJ32577@ZenIV.linux.org.uk>

Al: the FSF was so insistent on the adoption of the GPL version 3
because the GPL version 2 is not operative against the grantor.

This deficiency was, in their eyes, so fatal to the purposes that they
envisioned that they, as you have pointed out, elected to employ
enhanced means of converting projects to version 3.

Eben Moglen's contention that the GPL 3 exists to internationalize the
GPL is a lie of omission.

It is true that that is a partial reason-to-be for the GPL version 3
but it is not the main nor most important reason for the insistence on
version 3 or "v2 or any later version".

The very heart of the GPLv3 is the addition of the "irrevocable by
grantor" clause and the "term of years" clause.

Additionally the contention by the FSF and, as I recall, Eben Moglen
that the reason the FSF only accepts code where the copyright is
transferred to the FSF - is so they may have standing to sue - is
another lie by omission.

Yes, standing to sue is vital, if you are going to sue.
But the real beating heart of the copyright assignment policy is to
prevent a programmer from rescinding license-to-use regarding his
freely given code.

Without copyright assignment, any contributor to the GNU project could
elect to rescind the gratis license grant at his pleasure, at any
time, as of right.

Without an "irrevocable by grantor" clause (as seen in the GPL version
3, but omitted in GPL version 2 due to a mis-assumption on the part
of the drafter) there is not even an affirmative defense of promissory
estoppel.

We come to lie number three. (Neccecitated by:)
The incorrect assumption made by the
drafter of version 2 of the GPL and memorandized by Eben Moglen in
this very thread in an attempt to protect the error in drafting.
Lie number three: If terms regarding termination are proffered in a
copyright license they are the only means of termination.

This is true... If those terms are supported by bargained-for
consideration.
That is: the words Eben Moglen wrote were true; as regards to
commercial software, where the licensee has paid valuable
consideration for the terms offered.

The drafter of version 2 of the GPL was familiar with such commercial
licensing agreements. He failed in his due-diligence if RMS did
indeed request an irrevocable-by-grantor license. The drafter stopped
his research at the typical copyright license stage, and did not
research further into what underlays the construction there-of.

And thus we have the lie of omission number 3.

(All, naturally, to protect Eben Moglen's former client and to
discourage litigation where there is, indeed, good and sufficient
cause for such litigation) (Which is all part of an attorney's
duties, I can assure you)


On 2018-10-25 23:06, Al Viro wrote:
> On Thu, Oct 25, 2018 at 05:41:23PM -0400, Eric S. Raymond wrote:
> 
>> I do not have any facts with which to dispute this specific claim.
>> However, I do notice that a significant number of long-time
>> contributors have put themselves in the anti-CoC camp. I note Al Viro
>> as a recent example.
> 
> *snort*
> 
> For the record:
> 	* CoC is a piss-poor match for the structure of community
> 	* Linus had essentially tossed a live grenade into an outhouse on
> his way to vacation, with quite predictable results - all kinds of
> interesting coprophagous fauna dropping by to feed, including 
> cartooneys
> of the sort I hadn't seen since NANAE days.
> 	* As idiotic gambits go, "try and revoke the license on my
> contributions, so that they'll have to revoke CoC" is... impressive.
> Sadly, my command of English has turned out to be woefully inadequate,
> and I can't even blame that on not being a native speaker; I'm just as
> incapable of producing a coherent (let alone printable) description of
> that cunning plan in any language, Russian included.  I've tried.  
> Really.
> 	* in case it needs to be spelled out: I am not at all interested
> in that kind of stunts.  One of the reasons I thoroughly despise RMS
> and his bunch is the leverage game they tried to play with GPLv3;
> damned if I'm going to lower myself to their level.

  parent reply	other threads:[~2018-10-27  6:54 UTC|newest]

Thread overview: 104+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-20 13:49 [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document Greg Kroah-Hartman
2018-10-20 13:49 ` [PATCH 1/7] Code of conduct: Fix wording around maintainers enforcing the code of conduct Greg Kroah-Hartman
2018-10-20 13:50 ` [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 ` [PATCH 3/7] Code of Conduct Interpretation: Properly reference the TAB correctly Greg Kroah-Hartman
2018-10-20 13:50 ` [PATCH 4/7] Code of Conduct: Provide links between the two documents Greg Kroah-Hartman
2018-10-20 13:50 ` [PATCH 5/7] Code of Conduct Interpretation: Put in the proper URL for the committee Greg Kroah-Hartman
2018-10-20 19:01   ` Geert Uytterhoeven
2018-10-21  7:18     ` [Ksummit-discuss] " Greg KH
2018-10-20 13:51 ` [PATCH 6/7] Code of Conduct: Change the contact email address Greg Kroah-Hartman
2018-10-20 18:28   ` Alan Cox
2018-10-20 18:45     ` [Ksummit-discuss] " Trond Myklebust
2018-10-20 19:14       ` jonsmirl
2018-10-21  8:27         ` Theodore Y. Ts'o
2018-10-21  9:23           ` Greg KH
2018-10-20 19:24     ` Tim.Bird
2018-10-20 20:07       ` Trond Myklebust
2018-10-21  0:13       ` Alan Cox
2018-10-21  6:19         ` Thomas Gleixner
2018-10-20 20:13     ` James Bottomley
2018-10-20 13:51 ` [PATCH 7/7] MAINTAINERS: Add an entry for the code of conduct Greg Kroah-Hartman
2018-10-21 21:20 ` Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document NeilBrown
2018-10-21 22:26   ` [Ksummit-discuss] " Josh Triplett
2018-10-21 23:37     ` Theodore Y. Ts'o
2018-10-23  1:44       ` NeilBrown
2018-10-22 20:26     ` NeilBrown
2018-10-22 22:46       ` Theodore Y. Ts'o
2018-10-23  1:31         ` NeilBrown
2018-10-23  6:26         ` Dan Carpenter
2018-10-23  6:40           ` Al Viro
2018-10-23  6:46             ` Dan Carpenter
2018-10-23  3:31       ` Al Viro
2018-10-23  4:25         ` NeilBrown
2018-10-23  4:52           ` Al Viro
2018-10-23  5:28             ` NeilBrown
2018-10-23  6:00               ` Al Viro
2018-10-23 20:45                 ` NeilBrown
2018-10-23  8:11           ` Theodore Y. Ts'o
2018-10-23 14:22             ` Rainer Fiebig
2018-10-23 15:43               ` Theodore Y. Ts'o
2018-10-23 17:51                 ` Rainer Fiebig
2018-10-23 21:14             ` NeilBrown
2018-10-24 12:16       ` Josh Triplett
2018-10-25 21:14         ` NeilBrown
2018-10-27  1:10           ` Josh Triplett
2018-10-28 21:48             ` NeilBrown
2018-11-01 16:45             ` Paul E. McKenney
2018-11-01 21:11               ` Josh Triplett
2018-11-02 13:13                 ` Paul E. McKenney
2018-11-01 21:50               ` NeilBrown
2018-11-02 13:33                 ` Paul E. McKenney
2018-11-03  8:36                   ` NeilBrown
2018-11-03 17:37                     ` Paul E. McKenney
2018-11-03 21:06                       ` NeilBrown
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-10-21 22:33   ` Joe Perches
2018-10-21 22:37     ` Randy Dunlap
2018-10-22  9:09   ` Rainer Fiebig
2018-10-22 11:02   ` [Ksummit-discuss] " James Bottomley
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       ` Greg Kroah-Hartman
2018-10-25 19:39         ` Eric S. Raymond
2018-10-25 20:47           ` Theodore Y. Ts'o
2018-10-25 21:41             ` Eric S. Raymond
2018-10-25 22:12               ` NeilBrown
2018-10-25 22:38                 ` Eric S. Raymond
2018-10-25 22:52                   ` NeilBrown
2018-11-04 10:47                 ` [Ksummit-discuss] " Geert Uytterhoeven
2018-10-25 23:06               ` Al Viro
2018-10-26  2:28                 ` Eric S. Raymond
2018-10-26  5:49                   ` Al Viro
2018-10-27  6:52                 ` visionsofalice [this message]
2018-10-27  7:32                   ` Al Viro
2018-10-27 16:18                     ` [Ksummit-discuss] " Tim.Bird
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-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         ` The linux devs can rescind their license grant visionsofalice
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     ` Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document NeilBrown
2018-10-25  8:06   ` Pavel Machek
2018-10-25 11:20   ` Rainer Fiebig
2018-10-25 22:18     ` NeilBrown
2018-10-26  8:33       ` Rainer Fiebig
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=75eb4a46c8a2c1d4a927760fd1f2009d@redchan.it \
    --to=visionsofalice@redchan.it \
    --cc=bkuhn@sfconservancy.org \
    --cc=bruce@perens.com \
    --cc=clm@fb.com \
    --cc=editor@lwn.net \
    --cc=esr@thyrsus.com \
    --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 \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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).