ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: olof@lxom.net, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH-TOPIC] Review - Code of Conduct: Let's revamp it.
Date: Mon, 24 Sep 2018 22:46:29 +0200	[thread overview]
Message-ID: <CAOesGMi3rRZj-qJ03HbSctPVZybHoaapQnffhj5eP+w7RdKDRw@mail.gmail.com> (raw)
In-Reply-To: <20180924181138.GA16086@tuxdriver.com>

On Mon, Sep 24, 2018 at 8:15 PM John W. Linville <linville@tuxdriver.com> wrote:
>
> On Tue, Sep 25, 2018 at 03:51:14AM +1000, James Morris wrote:
> > On Mon, 24 Sep 2018, Shuah Khan wrote:
> >
> > > This decision to change the existing "Code of Conflict" signed off by a large number of developers,
> > > has been changed and committed with a few people signing off on it.
> > >
> > > It would be good to know the circumstances that necessitated the decision to include this patch
> > > without the proper review process. if that isn't possible, it is important to follow the review
> > > process now for v2. Also, discussing this in the Maintainer summit and/or kernel summit will not
> > > make the community feel like it is a community approved decision. At least, kernel community should
> > > be given a chance to discuss this change just like any other change.
> >
> > Not speaking on behalf of my employer, I agree with all of the above.
>
> +1
>
> Some number of folks feel (at least indirectly) chided or silenced by
> the new Code of Conduct. Many of those folks have expressed themselves
> ineloquently in a variety of venues. Much as one may disagree with
> some of their expressed sentiments, those expressions of frustration
> represent the feelings of some number of people in the real world.
>
> 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. If we really care about
> maximizing the pool of contributors, we need to accomodate even those
> that aren't particularly comfortable with 'playing nice'. Giving them
> some say in establishing the rules seems extremely reasonable to me.

Ah yes, Popper's Paradox. The answer is not that we have to be
tolerant of the intolerant -- or at least not infinitely. We also all
know that people need a bit of time to adjust to new habits and I
think we should focus more on (quick) improvement over time than
absolutes. We're all humans.

I'd like to make a couple of personal opinions clear here (for
whatever it's worth):

1) The CoC was clear that we're using this _from now on_. I.e. let
bygones be bygones even if bad things might have happened (there are
extreme exceptions to this, but let's not go there).

2) Some seem to be focused on worst-case scenarios of the culture
changing to be something completely different from what it is today. I
don't think anyone involved wants this, and we shouldn't implement
something that strict here. I still want people to argue over and care
about code. I still look forward to everybody participating, and we
shouldn't be doing anything along the lines of lowering the quality
bar or prioritizing things differently from today.

However, I hope that when we do have disagreements, we won't reach
shouting in all caps and name-calling stage. If someone gets a bit too
tempered, people should feel free to reach out and talk about it --
and that said people are willing to listen and maybe take a few deep
breaths before considering if it's useful to continue communicating
like they were and tone it down. If we can get that far, that'd make a
huge difference.

The old Code of Conflict said "be excellent to each other", but people
weren't. Hopefully with this change, we can end up a whole lot closer
to that state.


-Olof

  parent reply	other threads:[~2018-09-24 20:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24 14:24 Shuah Khan
2018-09-24 17:51 ` James Morris
2018-09-24 18:11   ` John W. Linville
2018-09-24 19:54     ` Josh Triplett
2018-09-24 20:46     ` Olof Johansson [this message]
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=CAOesGMi3rRZj-qJ03HbSctPVZybHoaapQnffhj5eP+w7RdKDRw@mail.gmail.com \
    --to=olof@lixom.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox