ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
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: Tue, 25 Sep 2018 08:21:15 +0200	[thread overview]
Message-ID: <CAOesGMjYT0pCtms8LeoKCWLXyEzRQ+=7AczWz07m0YpQyHBq9w@mail.gmail.com> (raw)
In-Reply-To: <CAKMK7uFczn2KHrKEbUan-E1adXKs24LZFY3Re4UHsXyfjB6byw@mail.gmail.com>

On Tue, Sep 25, 2018 at 6:26 AM Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>
> Thomas Gleixner <tglx@linutronix.de> schrieb am Di., 25. Sep. 2018, 00:22:
>>
>> On Mon, 24 Sep 2018, Olof Johansson wrote:
>> > 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.
>>
>> That's the important point here: we are _all_ humans. That includes those
>> who occasionally lose their temper (I know what I'm talking about and I
>> know for sure that it is a life long struggle to control it).
>>
>> If someone puts that person in his place, that's absolutely correct and
>> necessary. Most people immediately react, regret and apologize and they
>> mean it.

Minor note: "put in place" can be interpreted as someone standing up
and yelling even louder back at the person who's already aggravated.
That's not how things should have to work.

>>
>> Now if someone gets put in his place and the person who does that then goes
>> one step further and asks (privately) what's wrong and what caused that
>> pointless explosion, in other words deeply cares about the other person who
>> failed, then a way deeper change happens than just using the Code of
>> Conflict/Conduct as a one edged sword.
>
>
>
> All this coc asks you to do is stop putting yourself first and start considering others. Instead of lashing out and then expecting your recipients to also handle the fallout for, plus showing deep empathy for the harassment they just received.
>>
>>
>> Then 'be excellent to each other' becomes what it's really meant to be.
>
> Seems rather one way instead of mutual, what you have in mind.

I don't think anyone is in disagreement about the base case: That
everybody will work on changing, and that it's considered OK and
expected to call out when someone is starting to get out of line. Also
that we're all expecting things to converge on "excellent to each
other" very quickly even if there ends up being a couple of stumbles
along the way. Nobody gets free passes.

The second part I think there are two ways to interpret, and I read it
differently than you (but I might be the one who missed Thomas'
intention):

Reaching out to the one who's misbehaving I see more as something
friends will do to each other, not what the community as such is
expected to do. I.e. if I enjoy having Thomas around (I do, but I'm
also looking forward to him not blowing up ever so often), it's worth
checking in to see if everything is OK and if there's anything I can
do to help. Not before someone has checked in with the person at the
receiving end, and I definitely would never expect that person to be
the one checking in with Thomas.


-Olof

  reply	other threads:[~2018-09-25  6:21 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
2018-09-24 22:21       ` Thomas Gleixner
2018-09-25  4:26         ` Daniel Vetter
2018-09-25  6:21           ` Olof Johansson [this message]
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='CAOesGMjYT0pCtms8LeoKCWLXyEzRQ+=7AczWz07m0YpQyHBq9w@mail.gmail.com' \
    --to=olof@lixom.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --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