From: Josh Triplett <josh@joshtriplett.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ksummit-discuss@lists.linuxfoundation.org, tomi.valkeinen@iki.fi
Subject: Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors
Date: Wed, 17 Oct 2018 08:21:02 -0700 [thread overview]
Message-ID: <20181017152101.GA17531@localhost> (raw)
In-Reply-To: <CAMuHMdX0G767xYYcd8TDMLBp3cY9+fz_aJFAuz8OxgmCmhbNrg@mail.gmail.com>
On Wed, Oct 17, 2018 at 11:31:35AM +0200, Geert Uytterhoeven wrote:
> Hi Josh,
>
> Thanks for your comments!
>
> On Wed, Oct 17, 2018 at 11:13 AM Josh Triplett <josh@joshtriplett.org> wrote:
> > On Wed, Oct 17, 2018 at 09:19:01AM +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.
> >
> > This impression is, in fact, false, as has already been discussed
> > elsewhere. I had hoped that discussion would suffice.
>
> The CoC FAQ is not part of the CoC, and not part of the Linux kernel.
I wasn't referring just to that; I'm referring to the discussion we've
already had on this exact point.
> > refers to. Listing explicit cases to cover does not imply other cases
> > are not covered;
>
> It does, if not accompanied by "examples of...", like in the other sections.
"for everyone, regardless of ..." still says "for everyone", making the
"regardless of ..." inherently a non-exhaustive list of factors.
> > it does, however, ensure that the listed cases *are*,
> > and helps people know that they're covered.
>
> So you agree people cannot know if the unlisted cases are covered or not?
People in underrepresented and commonly marginalized groups, especially
those more commonly overlooked, don't always know if a given group has
taken their particular group into account or given any thought to it.
Explicit inclusion helps, and this is a standard guideline often cited
for good codes of conduct.
That doesn't make other groups *not* covered. But *if* there is a
particular commonly marginalized group that you feel this should
*explicitly* cover and doesn't, I'd suggest *adding* that group rather
than deleting the existing effort to be explicitly inclusive. (And
again, I'd suggest doing so upstream first.)
> > This patch is not OK, and defeats one of the purposes of the original
> > change.
>
> So the purpose of the original change was to list a number of factors,
> without saying that it was just a list of examples?
You seem to be actively trying to read something more into what I said.
One of the key purposes of the original change was to make the kernel a
"a welcoming environment to participate in", and to provide "explicit
guidelines".
WARNING: multiple messages have this Message-ID (diff)
From: Josh Triplett <josh@joshtriplett.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: ksummit-discuss@lists.linuxfoundation.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
tomi.valkeinen@iki.fi
Subject: Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors
Date: Wed, 17 Oct 2018 08:21:02 -0700 [thread overview]
Message-ID: <20181017152101.GA17531@localhost> (raw)
In-Reply-To: <CAMuHMdX0G767xYYcd8TDMLBp3cY9+fz_aJFAuz8OxgmCmhbNrg@mail.gmail.com>
On Wed, Oct 17, 2018 at 11:31:35AM +0200, Geert Uytterhoeven wrote:
> Hi Josh,
>
> Thanks for your comments!
>
> On Wed, Oct 17, 2018 at 11:13 AM Josh Triplett <josh@joshtriplett.org> wrote:
> > On Wed, Oct 17, 2018 at 09:19:01AM +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.
> >
> > This impression is, in fact, false, as has already been discussed
> > elsewhere. I had hoped that discussion would suffice.
>
> The CoC FAQ is not part of the CoC, and not part of the Linux kernel.
I wasn't referring just to that; I'm referring to the discussion we've
already had on this exact point.
> > refers to. Listing explicit cases to cover does not imply other cases
> > are not covered;
>
> It does, if not accompanied by "examples of...", like in the other sections.
"for everyone, regardless of ..." still says "for everyone", making the
"regardless of ..." inherently a non-exhaustive list of factors.
> > it does, however, ensure that the listed cases *are*,
> > and helps people know that they're covered.
>
> So you agree people cannot know if the unlisted cases are covered or not?
People in underrepresented and commonly marginalized groups, especially
those more commonly overlooked, don't always know if a given group has
taken their particular group into account or given any thought to it.
Explicit inclusion helps, and this is a standard guideline often cited
for good codes of conduct.
That doesn't make other groups *not* covered. But *if* there is a
particular commonly marginalized group that you feel this should
*explicitly* cover and doesn't, I'd suggest *adding* that group rather
than deleting the existing effort to be explicitly inclusive. (And
again, I'd suggest doing so upstream first.)
> > This patch is not OK, and defeats one of the purposes of the original
> > change.
>
> So the purpose of the original change was to list a number of factors,
> without saying that it was just a list of examples?
You seem to be actively trying to read something more into what I said.
One of the key purposes of the original change was to make the kernel a
"a welcoming environment to participate in", and to provide "explicit
guidelines".
next prev parent reply other threads:[~2018-10-17 15:21 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 7:19 [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors Geert Uytterhoeven
2018-10-17 7:19 ` Geert Uytterhoeven
2018-10-17 9:13 ` [Ksummit-discuss] " Josh Triplett
2018-10-17 9:13 ` Josh Triplett
2018-10-17 9:31 ` Geert Uytterhoeven
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:22 ` Josh Triplett
2018-10-17 15:21 ` Josh Triplett [this message]
2018-10-17 15:21 ` Josh Triplett
2018-10-17 15:49 ` James Bottomley
2018-10-17 16:00 ` Josh Triplett
2018-10-17 16:00 ` Josh Triplett
2018-10-17 18:36 ` Mark Brown
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
2018-10-22 21:06 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2018-10-07 8:51 [Ksummit-discuss] " Geert Uytterhoeven
2018-10-07 11:35 ` Josh Triplett
2018-10-07 11:35 ` Josh Triplett
2018-10-07 17:18 ` Laurent Pinchart
2018-10-07 17:18 ` Laurent Pinchart
2018-10-08 2:29 ` Josh Triplett
2018-10-08 2:29 ` Josh Triplett
2018-10-08 14:12 ` Tim.Bird
2018-10-08 14:12 ` Tim.Bird
2018-10-08 14:27 ` Laurent Pinchart
2018-10-08 14:27 ` Laurent Pinchart
2018-10-08 14:36 ` Tim.Bird
2018-10-08 14:36 ` Tim.Bird
2018-10-08 14:30 ` Geert Uytterhoeven
2018-10-08 14:30 ` Geert Uytterhoeven
2018-10-08 15:43 ` Geert Uytterhoeven
2018-10-08 15:43 ` Geert Uytterhoeven
2018-10-08 8:55 ` Geert Uytterhoeven
2018-10-08 8:55 ` Geert Uytterhoeven
2018-10-08 12:02 ` Mark Brown
2018-10-08 12:02 ` Mark Brown
2018-10-08 15:42 ` Alan Cox
2018-10-08 15:42 ` Alan Cox
2018-10-08 16:14 ` Josh Triplett
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 21:15 ` Arnaldo Carvalho de Melo
2018-10-10 22:16 ` Josh Triplett
2018-10-10 22:16 ` Josh Triplett
2018-10-10 22:33 ` Eric S. Raymond
2018-10-10 23:35 ` Frank Rowand
2018-10-11 8:12 ` Rainer Fiebig
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=20181017152101.GA17531@localhost \
--to=josh@joshtriplett.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=geert@linux-m68k.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.