ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Olof Johansson <olof@lixom.net>
Cc: olof@lxom.net,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH-TOPIC] Review - Code of Conduct: Let's revamp it.
Date: Tue, 25 Sep 2018 10:45:03 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1809250837370.1398@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAOesGMjYT0pCtms8LeoKCWLXyEzRQ+=7AczWz07m0YpQyHBq9w@mail.gmail.com>

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.

There is a - not completely unjustified - fear in the wider community that
the CoC could be turned into thought policing. Especially those who grew up
in the eastern part of Europe or under any other form of repressive state,
those who have second hand experience through relatives and friends and
those have been exposed to that in some other context, are very sensitive
to this and sentences like:

 "- we crack down hard on anything that might drive away contributors."

certainly do not make them more comfortable. Adding the unclarified
provisions of the CoC to it doesn't help either.

We're all human and it is part of human nature to fail. Repression does not
make that go away. Quite the contrary.

Thanks,

	tglx

  reply	other threads:[~2018-09-25  8:45 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 [this message]
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=alpine.DEB.2.21.1809250837370.1398@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=olof@lixom.net \
    --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