All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: olof@lxom.net, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH-TOPIC] Review - Code of Conduct: Let's revamp it.
Date: Mon, 24 Sep 2018 12:54:47 -0700	[thread overview]
Message-ID: <20180924195446.GB8484@localhost> (raw)
In-Reply-To: <20180924181138.GA16086@tuxdriver.com>

On Mon, Sep 24, 2018 at 02:11:39PM -0400, John W. Linville wrote:
> Some number of folks feel (at least indirectly) chided or silenced by
> the new Code of Conduct.

Such folks would do well to consider what *actual* behavior they're
engaged in would be affected, and how that behavior affects others.

> It seems likely to me that these folks are at least as likely to
> quit the community over their hurt feelings as have been the victims
> of Linus or any other grumpy maintainers.

I rather expect the number willing to complain to be quite different
from the number willing to leave rather than treat others decently. I'd
expect the latter to be vanishingly small. And ultimately, that's the
tradeoff here. You can't accommodate people who want to be treated
decently and people who refuse to treat others decently in the same
community. (You *can*, however, accommodate folks who grumble about
being required to treat others decently but nonetheless do so anyway.)

> If we really care about maximizing the pool of contributors, we need
> to accomodate even those that aren't particularly comfortable with
> 'playing nice'.

We really don't, any more than we need to accommodate those who insist
on not following the kernel coding style, or any other norm of the
kernel community. It doesn't have to be their *preferred* mode of
operation, just the one they use when interacting with the kernel
community.

  reply	other threads:[~2018-09-24 19:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24 14:24 [Ksummit-discuss] [TECH-TOPIC] Review - Code of Conduct: Let's revamp it Shuah Khan
2018-09-24 17:51 ` James Morris
2018-09-24 18:11   ` John W. Linville
2018-09-24 19:54     ` Josh Triplett [this message]
2018-09-24 20:46     ` Olof Johansson
2018-09-24 22:21       ` Thomas Gleixner
2018-09-25  4:26         ` Daniel Vetter
2018-09-25  6:21           ` Olof Johansson
2018-09-25  8:45             ` Thomas Gleixner
2018-09-25 16:42               ` Daniel Vetter
2018-09-25 20:03                 ` Shuah Khan
2018-09-25  6:46           ` Dan Williams
2018-09-24 19:31 ` Jason Cooper
2018-09-26 20:57   ` Mauro Carvalho Chehab
2018-09-24 23:15 ` James Bottomley
2018-09-25  1:35   ` Joe Perches
2018-09-26  6:54     ` Jani Nikula
2018-09-26  9:19       ` Jan Kara
2018-09-26  9:58         ` Hannes Reinecke
2018-09-26 12:35           ` Mauro Carvalho Chehab
2018-09-26 16:43         ` Mark Brown
2018-09-26 17:03           ` Tim.Bird
2018-09-26 12:30   ` Mauro Carvalho Chehab
2018-09-26 12:51     ` Geert Uytterhoeven
2018-09-26 14:01     ` Shuah Khan
2018-09-25 10:56 ` Jani Nikula
2018-09-25 13:38   ` Jonathan Corbet
2018-09-25 15:22     ` Shuah Khan
2018-09-25 16:51       ` Tim.Bird
2018-09-26  8:04         ` Laura Abbott
2018-09-26 14:47           ` Theodore Y. Ts'o
2018-09-27  8:30             ` Laura Abbott
2018-10-04 16:27 ` James Bottomley
2018-10-05 18:10   ` Shuah Khan
2018-10-06 21:39     ` James Bottomley
2018-10-07 15:27       ` Shuah Khan

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=20180924195446.GB8484@localhost \
    --to=josh@joshtriplett.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linville@tuxdriver.com \
    --cc=olof@lxom.net \
    /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.