linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 4.19-rc4 released, an apology, and a maintainership note
Date: Mon, 17 Sep 2018 03:15:48 +0100	[thread overview]
Message-ID: <CAPweEDwKzoxoVFSNbSnsHtqNhxB+AbdjD9XMXW0MEwNPGdr3Xg@mail.gmail.com> (raw)

hi linus,

just saw the note on slashdot.  i just wanted to say how amazed,
relieved and delighted i was to see what you wrote.  that you
recognised that you needed to reflect, *sought feedback*, and, most
importantly, were willing and able to discuss that and ask publicly.
as the longest-serving contributor with the highest expertise, on
*the* world's largest software project by a long, long margin, your
words have a staggeringly-high "weight", so it is absolutely inspiring
(and a huge relief).

you therefore deserve a thoughtful answer.  however, i thought it best
to also provide some "immediate" feedback, as well.  as someone who
has had... *deep breath*... an extremely difficult time in the
software libre world due to holding strict ethical values with high
integrity, i have had to do one hell of a lot of research into
resources to help with communication and dealing with conflict.
whilst they are not actually the real underlying concept, they're
guides and tools that are at least intellectually understandable, if
that makes any sense:

* the bill of ethics - https://www.titanians.org/the-bill-of-ethics/
* the titanian's "code of honour" -
https://www.titanians.org/titanian-code-of-honor/
* the "conflict resolution network" - http://www.crnhq.org/ (see "12
skills summary")
* powerful non-defensive communication - http://pndc.com/
* "Invisible Dynamics" - https://www.amazon.co.uk/dp/3896704915
  (specifically the page outlining the 6 systemic laws of organisations:
   page 23 i *think*.  my copy unfortunately is in storage).
* the "MASH" actor who is teaching scientists to communicate:
https://motherboard.vice.com/en_us/article/mgbwkn/how-a-former-mash-actor-is-teaching-scientists-to-be-extroverts

last on the list (and i prefer not to provide a link as it may need
explanation, and the website is too specific / slightly mis-directing)
if you're specifically considering some sort of "coach" to work with,
do contact me off-list and i can recommend someone who has helped me,
who also has experience helping businesses and organisations, not just
individuals.

it's very late here, so i will put some thought into a more
comprehensive reply over the next couple of days: the main thing that
i wanted to get across straight away was that i am responding
precisely because your message resonates with, and is basically
indicative of, ethical behaviour.  as in, just the very act of asking
for constructive feedback is an absolute and fundamental requirement
for anyone wishing to call their behaviour "ethical".  why? because if
you're not asking others for *outside* help in evaluating if you are
acting ethically, how the hell can you ever tell if your behaviour is
"good" or "bad"??

as in: you absolutely cannot tell if you are "on-target" to reach a
goal if you don't have any kind of feedback loop!  it's real simple,
and yet so many people go through life completely unconscious of,
unaware of, and unable to discuss or even think about, this absolutely
simple and fundamental requirement!

and that alone is really, *really* important.  we have way, *way* too
many software libre projects increasing in importance that are also
operating completely unethically, yet they *genuinely* believe that
just because the source is "open", everything must automatically be
"fine".  i won't give examples: there's just simply too many.

so what you've said that you intend to do, here, is not just about
you: you've created a key pivotal moment that will show other projects
why it's not just about the code: it's about people, and
communication.  it always has been.

*thumbs-up*.

l.

             reply	other threads:[~2018-09-17  2:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17  2:15 Luke Kenneth Casson Leighton [this message]
2018-09-18  2:10 ` Linux 4.19-rc4 released, an apology, and a maintainership note Luke Kenneth Casson Leighton
2018-09-30 11:47 ` Luke Kenneth Casson Leighton
  -- strict thread matches above, loose matches on Subject: below --
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-16 19:22 Linus Torvalds
2018-09-17  0:18 ` Rene Herman
2018-09-17  0:23 ` Rene Herman
2018-09-17  6:57 ` opal hart
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

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=CAPweEDwKzoxoVFSNbSnsHtqNhxB+AbdjD9XMXW0MEwNPGdr3Xg@mail.gmail.com \
    --to=lkcl@lkcl.net \
    --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).