From: "Eric S. Raymond" <esr@thyrsus.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
ksummit-discuss@lists.linuxfoundation.org,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors
Date: Wed, 10 Oct 2018 18:33:19 -0400 [thread overview]
Message-ID: <20181010223319.GA31256@thyrsus.com> (raw)
In-Reply-To: <20181010221611.GA5711@localhost>
Josh Triplett <josh@joshtriplett.org>:
> > The words removed by this patch are a political statement.
>
> Choosing not to say those words is a political statement.
The situation is not symmetrical. Choosing the protected classes
in the CoC is a *change* in its implied politics.
It's a change that is, obviously from LKML traffic, very contentious.
If this were a tpurely technical matter, it would be described as
not backwards-compatible.
It's a change that, I submit, should not have been made without a clear
consensus *in favor* of the change.
Our culture has a process for this. It's called RFCs. If we want to
designate protected classes to be called out in conductt guidelines,
an RFC should be floated first and the change should be made only
if rough consensus has been achieved.
--
<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-10 22:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 8:51 [PATCH] code-of-conduct: Remove explicit list of discrimination factors Geert Uytterhoeven
2018-10-07 11:35 ` [Ksummit-discuss] " Josh Triplett
2018-10-07 17:18 ` Laurent Pinchart
2018-10-08 2:29 ` Josh Triplett
2018-10-08 14:12 ` Tim.Bird
2018-10-08 14:27 ` Laurent Pinchart
2018-10-08 14:36 ` Tim.Bird
2018-10-08 14:30 ` Geert Uytterhoeven
2018-10-08 15:43 ` Geert Uytterhoeven
2018-10-08 8:55 ` Geert Uytterhoeven
2018-10-08 12:02 ` Mark Brown
2018-10-08 15:42 ` Alan Cox
2018-10-08 16:14 ` Josh Triplett
2018-10-10 20:55 ` Frank Rowand
2018-10-10 21:15 ` [Ksummit-discuss] " Arnaldo Carvalho de Melo
2018-10-10 22:16 ` Josh Triplett
2018-10-10 22:33 ` Eric S. Raymond [this message]
2018-10-10 23:35 ` Frank Rowand
2018-10-11 8:12 ` Rainer Fiebig
2018-10-11 6:36 ` Tomi Valkeinen
2018-10-17 7:19 Geert Uytterhoeven
2018-10-17 9:13 ` [Ksummit-discuss] " Josh Triplett
2018-10-17 9:31 ` Geert Uytterhoeven
2018-10-17 13:32 ` Guenter Roeck
2018-10-17 15:22 ` Josh Triplett
2018-10-17 15:21 ` Josh Triplett
2018-10-17 15:49 ` James Bottomley
2018-10-17 16:00 ` Josh Triplett
2018-10-17 18:36 ` Mark Brown
2018-10-17 13:45 ` Guenter Roeck
2018-10-17 16:18 ` Joe Perches
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=20181010223319.GA31256@thyrsus.com \
--to=esr@thyrsus.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=frowand.list@gmail.com \
--cc=geert@linux-m68k.org \
--cc=josh@joshtriplett.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--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).