public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: Christoph Conrads <contact@christoph-conrads.name>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Code of Conduct: Let's revamp it.
Date: Fri, 21 Sep 2018 10:09:07 +0200	[thread overview]
Message-ID: <2808315.UYOVJ65Qvk@merkaba> (raw)
In-Reply-To: <20180920231823.46d282ce40c91f39988bd34e@christoph-conrads.name>

Hello Christoph.

Christoph Conrads - 20.09.18, 23:18:
> The CoC is extremely ambiguously written for an enforceable document,
> any behavior disliked by the maintainers can be punished, and the
> level of naivete of the maintainers defending it is suprising for
> such a far reaching document.

For me the most important point is this:

Let Linus have his own experience and insights. It is not up to me 
telling him that he might be making this all up or may be completely 
right in his assessment. I do not know how he got to that experience and 
insights and what talks in person may have contributed to it. And its 
frankly simply not my business. I just congratulated him for his 
insights and his courage to speak up like this, seeing the potential in 
it.

Not my business is also the CoC Linux kernel developers and contributors 
may or may not give themselves. I am mostly a by-stander. Sure I test rc 
kernels and give (limited, as I usually do not bisect issues) feedback, 
report bugs. But that is about it.

What I see here is that a lot of people who are not even contributing to 
the Linux kernel in a major way apparently want to make their opinion 
about Code of Conduct heard loudly.

I ask myself: What the point of it?

Apparently at least some of the major contributors to the Linux kernel 
see an issue with communication culture on this mailing list and 
elsewhere. Whether it has been a wise move to just change the CoC to a 
different text, I read some major contributors opposing this move … I am 
all for letting people who contribute significantly to the Linux kernel 
have their own experience and insights.

It is simply not my business to interfere with whether they give 
themselves and the wider community a Code of Conduct and what would be 
the content of it. They do the work, one of them cares for the 
infrastructure that serves this mailing list. Even in case someone would 
now censor every post I do on LKML or even ban me from using it… I do 
not think it is to up to me to change or control that behavior. Sure, 
even small contributions count and I even have a tiny, little commit to 
kernel documentation, but still for me the major point is:

Some of the major contributors apparently see that the way of 
communicating here and elsewhere sometimes (!) does not serve Linux 
kernel development and the community. By just continuing the way it is, 
it is unlikely to receive a different outcome. So it is important to 
change *something*.

There is a kernel developer summit where they like to discuss exactly 
things like this. I do not see it up to me to try to control the outcome 
of that process.


KDE.org has a code of conduct¹. While at the same time they really have 
a rather friendly and welcoming environment – if you ask me one of the 
most friendly and welcoming ones I have ever witnessed so far. I also 
still see honest discussions there where people share their point of 
view and agree to disagree. They are very productive as well. Plasma and 
KDE applications become better and more usable with every release – yes, 
Linus in case you did not decide not to read mails on this list for now, 
I won´t CC your address, KDE stuff is getting better and better. And 
they work on making the project even more welcoming for newcomers. I´d 
say I even found friends within that project. They may not even need the 
CoC, but I do not see it doing any harm either.

I really don´t see the point of most of the discussion here. What 
happened now won´t be the end of Linux and that´s about it. There is no 
point for predicting doom unless you want it to happen.

[1] https://www.kde.org/code-of-conduct/

Thanks,
-- 
Martin



  reply	other threads:[~2018-09-21  8:09 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20 21:18 Code of Conduct: Let's revamp it Christoph Conrads
2018-09-21  8:09 ` Martin Steigerwald [this message]
2018-09-21 11:36   ` Christoph Conrads
  -- strict thread matches above, loose matches on Subject: below --
2018-09-19  6:00 Edward Cree
2018-09-19 14:18 ` Jonathan Corbet
2018-09-19 23:35   ` Edward Cree
2018-09-20  1:16     ` Olof Johansson
2018-09-20  2:14       ` Edward Cree
2018-09-21  1:48         ` Rik van Riel
2018-09-21  2:16           ` unixing
2018-09-21 13:07           ` Frank Ch. Eigler
2018-09-21 16:34             ` \0xDynamite
2018-09-21 23:15               ` Theodore Y. Ts'o
2018-09-21 23:20                 ` Joey Pabalinas
2018-09-21 23:31                 ` jonsmirl
2018-09-21 23:59                   ` Bernd Petrovitsch
2018-09-24 18:59                     ` \0xDynamite
2018-09-24 19:45                       ` Bernd Petrovitsch
2018-09-25  2:24                         ` gratuitouslicensesarerevocable
2018-09-25 17:14                         ` \0xDynamite
2018-09-26  0:41                           ` Bernd Petrovitsch
2018-09-26 19:34                             ` \0xDynamite
2018-09-26 20:55                               ` Joey Pabalinas
2018-09-28 18:34                                 ` \0xDynamite
2018-09-28 15:56                             ` Alan Cox
2018-09-28 19:38                               ` jonsmirl
2018-09-29 12:44                               ` Eric S. Raymond
2018-09-29 12:46                               ` Eric S. Raymond
2018-09-22  0:05                   ` Joey Pabalinas
2018-09-22  0:24                     ` jonsmirl
2018-09-24 17:43                       ` Max Filippov
2018-09-24 18:07                         ` jonsmirl
2018-09-23 18:44                 ` \0xDynamite
2018-09-25 23:48                 ` Michael Woods
2018-09-24 17:25             ` unconditionedwitness
2018-09-25 11:28         ` Pavel Machek
2018-09-25 12:36           ` Christoph Conrads
2018-09-25 13:13             ` Eric S. Raymond
2018-09-25 13:41               ` Christoph Conrads
2018-09-25 17:38                 ` \0xDynamite
2018-09-25 13:28             ` Pavel Machek
2018-09-26 10:24               ` Martin Steigerwald
2018-09-25 15:14             ` Theodore Y. Ts'o
2018-09-25 22:30               ` Eric S. Raymond
2018-09-26 11:17               ` Christoph Conrads
2018-09-20  3:07       ` Theodore Y. Ts'o
2018-09-20  4:18       ` Willy Tarreau
2018-09-20  9:27         ` unconditionedwitness
2018-09-20 22:57           ` Edward Cree
2018-09-23 14:50             ` Christoph Conrads
2018-09-23 18:41             ` \0xDynamite
2018-09-24 17:21             ` unconditionedwitness
2018-09-20  9:29         ` unconditionedwitness
2018-09-17 11:48 Lukas Wunner
2018-09-17 12:24 ` Greg Kroah-Hartman
2018-09-18 19:16   ` Pavel Machek
2018-09-19 10:30     ` Mauro Carvalho Chehab
2018-09-18 20:16   ` Lukas Wunner
     [not found]     ` <61b4a3f9-ccd1-061c-1c1b-ec993b056c66@bosch-fellbach.de>
2018-09-20 10:57       ` Lukas Wunner

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=2808315.UYOVJ65Qvk@merkaba \
    --to=martin@lichtvoll.de \
    --cc=contact@christoph-conrads.name \
    --cc=linux-kernel@vger.kernel.org \
    /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