ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <shuah@kernel.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: olof@lxom.net, Greg KH <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 14:03:18 -0600	[thread overview]
Message-ID: <41888741-906d-927c-8bfa-e239ff890bd7@kernel.org> (raw)
In-Reply-To: <CAKMK7uH7YMZ-3SHeJOwT=CVsOjHTMd97cGFf-e+3JCj8FOyQLA@mail.gmail.com>

On 09/25/2018 10:42 AM, Daniel Vetter wrote:
> On Tue, Sep 25, 2018 at 10:45 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>> On Tue, 25 Sep 2018, Olof Johansson wrote:
>>> 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.
>>
>> Let me put that straight.
>>
>> Surely everyone has to work on himself and I'm not expecting that the
>> person who got attacked reaches out to the one misbehaving. Obviously it
>> has to be the other way round and the one who misbehaved needs to reach
>> out.
>>
>> For me it's part of true excellence when the one who told me to stop it, or
>> a third person, reaches out to me as well.  John Stultz did that to me some
>> time ago, and I really appreciated it. It made a huge difference for me and
>> talking to him about it surely made me reflect deeper and helped me to see
>> where my own defense against my temper broke.
> 
> Fully agreed, having someone you can confide in and work through a
> complicated situation together in private helps greatly in
> understanding and improving long term. What really worried me here is
> that we brought this up in the context of a code of conduct -
> codifying the expectation that this should happen doesn't seem a good
> idea to me. The cleanups-after-explosions I've helped with were
> already tons of work, with typing a very carefully edited response in
> public (don't want to make it accidentally worse) and then lots
> chatting with recipients to make sure they're not running away.
> Loading up even more is not something I want to force on anyway. It's
> great though if it happens, maybe as some sort of informal peer
> maintainers group, since that's how we improve as a community.

Right. It would help when a third person points out. In general, what happens
is the receiving party either comes back with neutral tone (which is very tough,
and I have had to do that a few times), things calm down.

I worry about cases where the receiving party retreats and stops participating. I do
think that this CoC might help in those situations and fellow developers and/or
maintainers might be able to send a polite reminder in a private response to the
offending party and/or a polite public one to calm things. A public one could be
helpful in some cases, if it helps stop the hurting party to from retreating.

This is where we all have to be careful not overreact to perceived slights. I think
this is going be a lot harder in a global community such as ours. i.e one person's
joke could be another person's insult. Again, we have to be put some thought in when
responding which we should be doing anyway.

I am sincerely wishing for good outcomes with all of this.

thanks,
-- Shuah

  reply	other threads:[~2018-09-25 20:03 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
2018-09-25  8:45             ` Thomas Gleixner
2018-09-25 16:42               ` Daniel Vetter
2018-09-25 20:03                 ` Shuah Khan [this message]
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=41888741-906d-927c-8bfa-e239ff890bd7@kernel.org \
    --to=shuah@kernel.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=olof@lxom.net \
    --cc=tglx@linutronix.de \
    /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