From: "Eric S. Raymond" <esr@thyrsus.com>
To: Eben Moglen <moglen@columbia.edu>
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 11:50:01 -0400 [thread overview]
Message-ID: <20181026155001.GA6327@thyrsus.com> (raw)
In-Reply-To: <849-Fri26Oct2018091533-0400-eben@harlan.sflc-vpn>
Eben Moglen <moglen@columbia.edu>:
> reputational damage is *specifically* recognized as grounds for relief.
>
> No. Reputational damage is not mentioned at all, let alone
> specifically recognized.
I have no difficulty in finding the word "reputation" in the brief in
in proximity with the phrase "increasing [the programmer's] recognition in
his profession". In fact the brief notes " The Eleventh Circuit has
recognized the economic motives inherent in public licenses, *even
where profit is not immediate*" (Emphasis mine.)
And "The attribution and modification transparency requirements
directly serve to drive traffic to the open source incubation page and
to inform downstream users of the project, which is a significant
economic goal of the copyright holder *that the law will enforce.*"
(Emphasis mine.)
You seem to be denying that the brief says what it actually says. It
not only qualifies reputational gain as a kind of economic
gain - and thus losses as damage - but cites the Eleventh Circuit as a
previous authority for the proposition, and affirms that these gains
and losses can be a matter for the law.
This disinclines me to trust the rest of your analysis or assertions.
I think you are advocating for your interest in the perceived
irrevocability of the GPL, and where this implies being less than fully
forthcoming about the actual risks in *this* situation you are committing
something perilously close to suppressio veri. This is not helpful.
I've lived with a practising attorney since about the time she was one
of the first-line legal reviewers for the original GPL back in the
1980s - we probably still have the draft printout with her scribbled
annotations on it somewhere. "Only lawyers can interpret this voodoo"
is not a good line to pull on me when it comes to open-source
licensing; I don't buy it and she wouldn't either.
Here's another sentence from the brief that I had forgotten:
"Copyright holders who engage in open source licensing have the right
to control the modification and distribution of copyrighted material."
- a particularly telling sentence in regard to the current
controversy, and one I had forgotten.
That there could be enough to win the day for the license
revokers - they don't actually have to revoke, just assert that
control. Pretty much equivalent to what the the Berne Convention's
moral-rights provision does in Europe - they could claim that the
CoC is a defacement of their work to which they refuse assent
and have a case.
I am not at all doubtful that the dissidents know these things; some
of the language in the broadsides to lkml so indicates. Which is why
I'm trying to get the kernel leadership to repair its unnecessarily
high-handed behavior before somebody gets pissed off enough to
actually drop a bomb.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.
next prev parent reply other threads:[~2018-10-26 15:50 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 [this message]
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 ` [Ksummit-discuss] " 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=20181026155001.GA6327@thyrsus.com \
--to=esr@thyrsus.com \
--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 \
--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 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.