From: Rene Herman <rene.herman@gmail.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 4.19-rc4 released, an apology, and a maintainership note
Date: Mon, 17 Sep 2018 02:23:42 +0200 [thread overview]
Message-ID: <20180917002342.15342-1-rene.herman@gmail.com> (raw)
In-Reply-To: <CA+55aFy+Hv9O5citAawS+mVZO+ywCKd9NQ2wxUmGsz9ZJzqgJQ@mail.gmail.com>
Hi Linus.
I was "around linux-kernel" some 10 years ago and still to this date
sometimes check e.g. lkml.org where I happened upon this; felt it hard
to resist commenting on one specific bit...
Whereas you concentrate on net-positive effect on code quality of an at
times "crass" communication style, I believe there is or used to be an
actually larger net-positive on community: the very fact that you as
project leader feel/felt free to sometimes tell people off is and is I
believe widely taken to be a sign that the Linux project leader still
considers himself part of the community; is anti-hierarchical in that
sense, and as such a large positive for a community a significant
majority of which would not have (had) it any other way.
Now, Linux has of course long outgrown its hacker-beginnings; I would
expect that by now an overwhelming majority of developers is part of
a corporate hierarchy anyway and therefore not themselves free to respond
to you "on equal terms" even if they were personally inclined to do so.
The above may hence be somewhat obsolete in reality -- and I'm also
sure that this is for you more personal than for someone like me reading
it on LKML(.org), but hearing you describe your style up to now as
_wrong_ still feels quite, well, wrong.
At the very least historically it wasn't, and it if is more now it
at the very least still reflects quite positively on honesty and
openness.
Rene.
next prev parent reply other threads:[~2018-09-17 0:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 19:22 Linux 4.19-rc4 released, an apology, and a maintainership note Linus Torvalds
2018-09-16 21:42 ` [...] " Adam Borowski
2018-09-16 23:59 ` Moritz Obermeier
2018-09-17 0:18 ` Linux 4.19-rc4 released, " Rene Herman
2018-09-17 0:20 ` [...] " Andy Isaacson
2018-09-17 0:23 ` Rene Herman [this message]
2018-09-17 6:57 ` Linux 4.19-rc4 released, " opal hart
2018-09-17 7:57 ` […] " Martin Steigerwald
2018-09-17 8:53 ` Martin Steigerwald
2018-09-30 12:09 ` Re: Linux 4.19-rc4 released, " lkcl
2018-09-30 14:07 ` Martin Steigerwald
2018-09-30 16:27 ` Luke Kenneth Casson Leighton
2018-09-17 12:58 ` Guenter Roeck
2018-09-17 17:09 ` Joe Perches
2018-09-17 21:09 ` Michael Woods
2018-09-18 1:30 ` Pavel Snajdr
2018-09-21 22:13 ` Michael Woods
2018-10-04 14:57 ` Eric W. Biederman
2018-10-08 15:29 ` Enrico Weigelt, metux IT consult
2018-10-08 13:54 ` Enrico Weigelt, metux IT consult
2018-10-08 16:36 ` Enrico Weigelt, metux IT consult
2018-09-17 2:15 Luke Kenneth Casson Leighton
2018-09-18 2:10 ` Luke Kenneth Casson Leighton
2018-09-30 11:47 ` Luke Kenneth Casson Leighton
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=20180917002342.15342-1-rene.herman@gmail.com \
--to=rene.herman@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).