From: Edward Cree <ec429@cantab.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Code of Conduct: Let's revamp it.
Date: Thu, 20 Sep 2018 00:35:10 +0100 [thread overview]
Message-ID: <72dadc76-44fe-ecb5-e142-0a9129082c93@cantab.net> (raw)
In-Reply-To: <20180919081812.020f19e3@lwn.net>
On 19/09/18 15:18, Jonathan Corbet wrote:
> I'd like to address just this part, speaking only for myself.
> The LF is not in the position of arbitrating anything here. The body
> charged with that is the LF Technical Advisory Board, which is a
> different thing.
Thank you for clarifying that.
Jon, you're a good person, and I trust you not to harass developers.
I'm not expecting you, or gregkh, or hpa to launch a dastardly plot
to boot an innocent developer off the project.
But there are too many ways this can go wrong, maybe not now or next
week but in five or ten years, when maybe a different kind of person
is on the TAB, or maybe external pressure is brought to bear on TAB
members. (Some people are speculating that pressure has already
been brought to bear on Linus, although I'd like to stress that if
he feels that changing the way he communicates is best for the
project then I for one thoroughly respect that.)
Or maybe some manipulative extrovert will manage to whip up a media
storm about some developer's innocuous remarks, the court of public
opinion will immediately convict, other developers will be caught
in a preference falsification cascade as no-one wants to take the
risk of defending them. Are you, and the other members of the TAB,
strong enough to hold back the lynch mobs when you know the guy
hasn't done anything wrong? Do you really want to take on the
responsibility to do that, perhaps time and time again? And can
you be sure that you won't fall for a misleading framing by some
charismatic sociopath of a fight you missed the start of?
Given that possibility, I think it is important for the kernel
community to continue to send a strong signal that divisive identity
politics are not welcome here; and I think that to adopt a Code of
Conduct that contains in its opening sentence a laundry-list of
protected classes (and was written by a, shall we say, divisive
figure with a history of identity politics advocacy) sends precisely
the opposite signal.
Linux is too important to civilisation to allow it to be turned into
just another battlefield for the American culture war; commit
8a104f8b5867 seems like an invitation to both armies to take up
positions on our fertile farmland. The only rule that gives no
comfort to discriminatory political abusers (on either side) is—
ye shall judge by their code alone.
next prev parent reply other threads:[~2018-09-19 23:35 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 [this message]
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
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=72dadc76-44fe-ecb5-e142-0a9129082c93@cantab.net \
--to=ec429@cantab.net \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.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 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).