linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eben Moglen <moglen@columbia.edu>
To: esr@thyrsus.com
Cc: gregkh@linuxfoundation.org, visionsofalice@redchan.it,
	linux-kernel@vger.kernel.org, rms@gnu.org, bruce@perens.com,
	bkuhn@sfconservancy.org, editor@lwn.net, neil@brown.name,
	labbott@redhat.com, torvalds@linux-foundation.org,
	ksummit-discuss@lists.linuxfoundation.org, tglx@linutronix.de,
	olof@lixom.net, clm@fb.com, mishi@linux.com,
	linux-kernel-owner@vger.kernel.org
Subject: Re: The linux devs can rescind their license grant.
Date: Fri, 26 Oct 2018 09:15:33 -0400	[thread overview]
Message-ID: <849-Fri26Oct2018091533-0400-eben@harlan.sflc-vpn> (raw)
In-Reply-To: Eric S. Raymond's message of Thu, 25 Oct 2018 15:39:01 -0400 <20181025193901.GD26403@thyrsus.com>

On Thursday, 25 October 2018, Eric S. Raymond wrote:

  Under Jacobsen vs. Katzer (535 f 3d 1373 fed cir 2008) authors of
  GPLed software have a specific right to relief (including injunctive
  relief) against misappropriation of their software. That ruling (which
  was the case of first impression on the binding status of the GPL)
 
No, Eric, _Jacobsen_ v. _Katzer_ has nothing to do with GPL.  The
license terms on the software at issue were Artistic 1.0.  The GPL is
mentioned in an informational footnote only.  The case has little
legal weight, for procedural reasons, and is most certainly not "the
case of first impression on the binding status of the GPL."

 reputational damage is *specifically* recognized as grounds for relief.
  
No.  Reputational damage is not mentioned at all, let alone
specifically recognized.  The District Court opinion that was
overturned in the Court of Appeals had held that licenses that don't
require payment of royalties are unenforceable, which was not
copyright law of any kind.  The CAFC, guessing about the content of
Ninth Circuit law under the jurisdictional rules of the appeal (a
state of affairs which leaves no real precedential weight at all
behind the opinion) rightly discovered that there are "economic
interests" furthered by free licensing.  Reputational interests are
not among those mentioned.  This is a <a
href="https://caselaw.findlaw.com/us-federal-circuit/1189790.html">public
document</a> anyone can read.  I'm a little surprised you didn't check
before asserting.

  The anti-CoC dissidents don't have to rescind their license grant to
  cause a great deal of trouble. Instead they can invoke the doctrine
  established in Jacobsen vs. Katzer, seeking restraining orders.

They can do neither.  There is no "doctrine established in Jacobsen."
The license terms of the GPLv2, GPLv3, and all related licenses
provide a mode of termination---for imposition of additional
restrictions or violation of other terms.  This termination provision,
being explicit, is therefore the sole form of termination recognized
under the terms of the Copyright Act.

  The line of argument is so simple that I could probably brief it
  myself, and I'm not a lawyer

Law school exists to give people who are not yet lawyers a healthy
respect for what they cannot do.  This discussion has been a riot of
amateur opining, but practicing law without a license is always a bad
idea.

  For that matter, I don't think the question of whether the GPL can be
  rescinded is settled - nor does my wife Cathy Raymond, Esq., a practicing
  attorney who has also studied the relevant law.

It is settled.  Indeed, it was never in doubt.  When Jerry Cohen made
GPLv2 he was of course asked by Richard to make an irrevocable
license.  He did so.  The US law provides that this license cannot be
terminated except on its stated terms.  But the basis of that rule,
which is statutory, was not reliable under non-US law, so in GPLv3 I
"codified" the US result in the license terms, as we did with various
other features in which GPLv2 assumed the US law background.

What the discussion set off by the present CoC controversy showed me
was that there was no accessible, legally-accurate description of US
copyright license termination law as it affects the various FOSS
licenses in particular.  I wrote such an article and began preparing
it for publication, but was interrupted in that work by my mother's
last illness and death.

In the meantime everything said on all sides, for and against, has
been wrong.  The correct legal analysis has been offered nowhere.  As
I am beginning to return to work, I will publish the article soon.
For now, the headline is that Greg is correct.  There is nothing in
the repeated assertions that some form of withdrawal of licensed rights
or attacks on the copyright status of the kernel are a possible
response to disagreement over changes in internal project governance.

It's a small point---and like all the other supposed points raised so
far, irrelevant---but I should say in passing, after years of teaching
the basic Property course at Columbia and Harvard law schools, that
Bruce Perens gave as succinct a description of the "rule against
perpetuities" as I ever hear from a beginner in the classroom.  In the
English legal history course that I also teach (almost the only place
in a modern law school in which the law of future interests is
seriously considered), more is said.  But the key point is that the
"rule against perpetuities" is not a rule against perpetuities.  The
confusion on this point is one of the clearest signs that the writer
or writers using various pseudonyms is/are not, whatever s/he claims,
a US or UK lawyer at all.

Eben

-- 
 Eben Moglen                            v: 212-461-1901 
 Professor of Law, Columbia Law School  f: 212-854-7946       moglen@
 435 West 116th Street, New York City, NY 10027            columbia.edu
 Founding Director, Software Freedom Law Center        softwarefreedom.org
 

  parent reply	other threads:[~2018-10-26 13:22 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
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 [this message]
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=849-Fri26Oct2018091533-0400-eben@harlan.sflc-vpn \
    --to=moglen@columbia.edu \
    --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=neil@brown.name \
    --cc=olof@lixom.net \
    --cc=rms@gnu.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=visionsofalice@redchan.it \
    /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).