linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Frank Rowand <frowand.list@gmail.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Tomi Valkeinen <tomi.valkeinen@iki.fi>,
	Bart Van Assche <bvanassche@acm.org>, Pavel Machek <pavel@ucw.cz>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] code-of-conduct: Remove explicit list of discrimination factors
Date: Mon, 3 Dec 2018 12:05:06 +0100	[thread overview]
Message-ID: <20181203110506.GA7485@kroah.com> (raw)
In-Reply-To: <20181202093257.3918-1-geert@linux-m68k.org>

On Sun, Dec 02, 2018 at 10:32:57AM +0100, Geert Uytterhoeven wrote:
> Providing an explicit list of discrimination factors may give the false
> impression that discrimination based on other unlisted factors would be
> allowed.
> 
> Furthermore, this list is already overly long, polarizing,
> politically-laden, and reinstating the concept of human races.
> None of these is related to the goals of the Linux kernel project.
> 
> Avoid any ambiguity or political undertone by removing the list, to
> ensure "a harassment-free experience for everyone", period.

I understand the reason you and others are proposing this change,
however for now, let us stick with the text that we have.  As Linus and
I said just over a month ago, let's sit with the text we have until
something comes up that requires a change to happen.

Also, I recommend you work with the upstream developers of this text to
see if they agree with your changes here.  If they do, and update their
version, I will be glad to revisit this text at that time.

But everyone, please note that there are very specific reasons for
listing things like this.  You might not agree with those reasons, but
many other people do so each "camp" can not be happy in the end.  As we
did have 3 years without such a list of factors, perhaps it is time to
have 3 years with the list to provide a fair balance. :)

So I'm not going to accept this patch at this point in time, sorry.

thanks,

greg k-h

  parent reply	other threads:[~2018-12-03 11:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-02  9:32 [PATCH v3] code-of-conduct: Remove explicit list of discrimination factors Geert Uytterhoeven
2018-12-02  9:55 ` Joey Pabalinas
2018-12-02 11:42 ` Mike Rapoport
2018-12-03 11:05 ` Greg Kroah-Hartman [this message]
2018-12-03 11:53   ` Geert Uytterhoeven
2018-12-03 14:17     ` Greg KH
2018-12-03 12:15   ` Pavel Machek
2018-12-03 16:49     ` Linus Torvalds
2018-12-08 20:31       ` Michael Tirado

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=20181203110506.GA7485@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=acme@kernel.org \
    --cc=bvanassche@acm.org \
    --cc=corbet@lwn.net \
    --cc=frowand.list@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=tomi.valkeinen@iki.fi \
    /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).