All of lore.kernel.org
 help / color / mirror / Atom feed
From: unconditionedwitness@redchan.it
To: Willy Tarreau <w@1wt.eu>
Cc: Olof Johansson <olof@lixom.net>, Edward Cree <ec429@cantab.net>,
	Jonathan Corbet <corbet@lwn.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-kernel-owner@vger.kernel.org
Subject: Re: Code of Conduct: Let's revamp it.
Date: Thu, 20 Sep 2018 09:27:04 +0000	[thread overview]
Message-ID: <206423b0a199c1f12e61364d6e687e09@redchan.it> (raw)
In-Reply-To: <20180920041846.GA4418@1wt.eu>

Regarding those who are ejected from the Linux Kernel Community after 
this CoC:

Contributors can, at any time, rescind the license grant regarding their 
property via written notice to those whom they are rescinding the grant 
from (regarding their property (code)).

The GPL version 2 lacks a no-rescission clause (the GPL version 3 has 
such a clause: to attempt furnish defendants with an estoppel defense, 
the Linux Kernel is licensed under version 2, however, as are the past 
contributions).

When the defendants ignore the rescission and continue using the 
plaintiff's code, the plaintiff can sue under the copyright statute.

Banned contributors _should_ do this (note: plaintiff is to register 
their copyright prior to filing suit, the copyright does not have to be 
registered at the time of the violation however)

Additionally when said banned contributors joined the Linux team, they 
were under the impression that it was a meritocracy: in-fact this belief 
was stated or ratified by those within the governing body regarding 
Linux when the contributors began their work (whatever that body was at 
that time, it could have been simply Linus, or Linus and a few 
associates).

The remuneration for the work was implied to be, or perhaps stated, to 
be fame as-well as a potential increase in the contributors stature, in 
addition to membership in the Linux Kernel club or association, or 
whatever it is that the Linux Kernel Community actually is (which a 
court may determine... it is something, suffice to say).

Thusly for work, consideration was promised by (Linus? Others? There are 
years of mailing list archives with which to determine).

And now that consideration has been clawed-back and the contributors 
image has been tarnished.

Thus the worker did work, however the other side of the implied, or 
perhaps written (email memorandums), understanding has been violated 
(once the contributor has been banned under the new non-meritocratic 
"CoC").

Damages could be recovered under: breach of contract, quazi-contract, 
libel, false-light. (services rendered for the contractual claims, 
future lost income for the libel claims)

In addition to copyright claims. (statutory damages, profits)

For greatest effect, all rescission should be done at once in a bloc. 
(With other banned contributors).

Contributors: You were promised something, you laboured for that 
promise, and now the promise has become a lie. You have remedies 
available to you now, as-well as in the close future.

Additionally, regarding those who promoted the Code of Conduct to be 
used against the linux kernel contributors, knowing full well the effect 
it would have and desiring those effects; recovery for the ejected 
contributors via a tortious interference claim may be possible.

  reply	other threads:[~2018-09-20  9:27 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  6:00 Code of Conduct: Let's revamp it Edward Cree
2018-09-19 14:18 ` Jonathan Corbet
2018-09-19 23:35   ` Edward Cree
2018-09-20  1:16     ` Olof Johansson
2018-09-20  2:14       ` Edward Cree
2018-09-21  1:48         ` Rik van Riel
2018-09-21  2:16           ` unixing
2018-09-21 13:07           ` Frank Ch. Eigler
2018-09-21 16:34             ` \0xDynamite
2018-09-21 23:15               ` Theodore Y. Ts'o
2018-09-21 23:20                 ` Joey Pabalinas
2018-09-21 23:31                 ` jonsmirl
2018-09-21 23:59                   ` Bernd Petrovitsch
2018-09-24 18:59                     ` \0xDynamite
2018-09-24 19:45                       ` Bernd Petrovitsch
2018-09-25  2:24                         ` gratuitouslicensesarerevocable
2018-09-25 17:14                         ` \0xDynamite
2018-09-26  0:41                           ` Bernd Petrovitsch
2018-09-26 19:34                             ` \0xDynamite
2018-09-26 20:55                               ` Joey Pabalinas
2018-09-28 18:34                                 ` \0xDynamite
2018-09-28 15:56                             ` Alan Cox
2018-09-28 19:38                               ` jonsmirl
2018-09-29 12:44                               ` Eric S. Raymond
2018-09-29 12:46                               ` Eric S. Raymond
2018-09-22  0:05                   ` Joey Pabalinas
2018-09-22  0:24                     ` jonsmirl
2018-09-24 17:43                       ` Max Filippov
2018-09-24 18:07                         ` jonsmirl
2018-09-23 18:44                 ` \0xDynamite
2018-09-25 23:48                 ` Michael Woods
2018-09-24 17:25             ` unconditionedwitness
2018-09-25 11:28         ` Pavel Machek
2018-09-25 12:36           ` Christoph Conrads
2018-09-25 13:13             ` Eric S. Raymond
2018-09-25 13:41               ` Christoph Conrads
2018-09-25 17:38                 ` \0xDynamite
2018-09-25 13:28             ` Pavel Machek
2018-09-26 10:24               ` Martin Steigerwald
2018-09-25 15:14             ` Theodore Y. Ts'o
2018-09-25 22:30               ` Eric S. Raymond
2018-09-26 11:17               ` Christoph Conrads
2018-09-20  3:07       ` Theodore Y. Ts'o
2018-09-20  4:18       ` Willy Tarreau
2018-09-20  9:27         ` unconditionedwitness [this message]
2018-09-20 22:57           ` Edward Cree
2018-09-23 14:50             ` Christoph Conrads
2018-09-23 18:41             ` \0xDynamite
2018-09-24 17:21             ` unconditionedwitness
     [not found]               ` <c61eb2d545150d46428f4bc25843cd58@redchan.it>
     [not found]                 ` <201809241941.44460.dr.klepp@gmx.at>
     [not found]                   ` <20180924204809.GK23968@linuxmafia.com>
2018-09-25  2:09                     ` [DNG] Fwd: " gratuitouslicensesarerevocable
2018-09-20  9:29         ` unconditionedwitness
  -- strict thread matches above, loose matches on Subject: below --
2018-09-20 21:18 Christoph Conrads
2018-09-21  8:09 ` Martin Steigerwald
2018-09-21 11:36   ` Christoph Conrads
2018-09-17 11:48 Lukas Wunner
2018-09-17 12:24 ` Greg Kroah-Hartman
2018-09-18 19:16   ` Pavel Machek
2018-09-19 10:30     ` Mauro Carvalho Chehab
2018-09-18 20:16   ` Lukas Wunner
     [not found]     ` <61b4a3f9-ccd1-061c-1c1b-ec993b056c66@bosch-fellbach.de>
2018-09-20 10:57       ` Lukas Wunner

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=206423b0a199c1f12e61364d6e687e09@redchan.it \
    --to=unconditionedwitness@redchan.it \
    --cc=corbet@lwn.net \
    --cc=ec429@cantab.net \
    --cc=linux-kernel-owner@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=w@1wt.eu \
    /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.