ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors
Date: Mon, 8 Oct 2018 10:55:50 +0200	[thread overview]
Message-ID: <CAMuHMdVS6QVfg6=-a9+qgnhjT4f1aEMdEm54jKFy7MnSxCj_1g@mail.gmail.com> (raw)
In-Reply-To: <20181007113514.GA21217@localhost>

Hi Josh,

On Sun, Oct 7, 2018 at 1:35 PM Josh Triplett <josh@joshtriplett.org> wrote:
> On Sun, Oct 07, 2018 at 10:51:02AM +0200, 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.
> >
> > Avoid any ambiguity by removing the list, to ensure "a harassment-free
> > experience for everyone", period.
>
> I would suggest reading the commit message that added this in the first
> place. "Explicit guidelines have demonstrated success in other projects
> and other areas of the kernel." See also various comparisons of codes of

The first paragraph of the commit message (the "why" part) is exactly the
part we've been waiting for a clarification since the inception of the
commit...

> conduct, which make the same point. The point of this list is precisely
> to serve as one such explicit guideline; removing it would rather defeat
> the purpose.

Then (at least) the list should be marked containing examples, cfr. the other
examples in the document.

> In any case, this is not the appropriate place for such patches, any
> more than it's the place for patches to the GPL.

There are precedents:

Until recent, the file named "COPYING" (which you referred to in another
email related to patching the CoC), was a verbatim copy of the GPL, with
clarifications added at the top.

Documentation/process/code-of-conduct.rst is already a slightly modified
version of the original.

Now, if amending the CoC locally is not an option, I'm afraid a plain revert
is the only option, like for any other commit that breaks the userspace ABI
(Linux kernel developers are also users ;-), until the raised issues have
been resolved upstream.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  parent reply	other threads:[~2018-10-08  8:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-07  8:51 Geert Uytterhoeven
2018-10-07 11:35 ` 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 [this message]
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   ` Arnaldo Carvalho de Melo
2018-10-10 22:16   ` Josh Triplett
     [not found]     ` <20181010223319.GA31256@thyrsus.com>
2018-10-10 23:35       ` Frank Rowand
2018-10-17  7:19 Geert Uytterhoeven
2018-10-17  9:13 ` 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
2018-10-22 21:06 ` Pavel Machek

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='CAMuHMdVS6QVfg6=-a9+qgnhjT4f1aEMdEm54jKFy7MnSxCj_1g@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --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