linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	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 13:02:36 +0100	[thread overview]
Message-ID: <20181008120236.GD5684@sirena.org.uk> (raw)
In-Reply-To: <20181007113514.GA21217@localhost>

[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]

On Sun, Oct 07, 2018 at 04:35:14AM -0700, Josh Triplett 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
> 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.

The Debian code of conduct also omits the explicit list of factors.  In
their case it was a deliberate decision due to a real fear that people
involved in and adjacent to the project would try to rules lawyer an
explict list and wanting to make the code of conduct robust against
that.  The communities seem similar enough that it's worth thinking
about for the kernel as well, Debian has had to deal with some serious
problems in the past so there's some experience behind the decisions
there.

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

We do need some way to talk about what we're trying to do here.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2018-10-08 12:02 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 [this message]
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
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=20181008120236.GD5684@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=James.Bottomley@hansenpartnership.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).