LKML Archive on
 help / Atom feed
From: Michael Woods <>
Subject: Re: Linux 4.19-rc4 released, an apology, and a maintainership note
Date: Mon, 17 Sep 2018 22:09:48 +0100
Message-ID: <> (raw)
In-Reply-To: <>

Hi Linus,

 > The one change that stands out and merits mention is the code of
 > conduct addition...

The Code of Conflict was perfectly fine. Whomever convinced you to add 
the Code of Conduct was convincing you to give control over to a social 
justice initiative that has no interest in the kernel's core function or 
reason for existence.

"Codes of conduct are tools used by the incompetent to wrest control 
away from the people who own the project, so they can feed on the corpse 
and wear the skin of the project as a fetish play"

Examples of these people trying to introduce codes of conduct, with 
commentary on the emotions and motivations driving CoC introduction:
- PHP:
- PHP 2:
- Ruby:
- Ruby 2:
- Node.js:
- Awesome-Django:
- Go:

Some alternative ideas should you wish to rethink the Code of Conduct:
- Code of Merit:
- No Code of Conduct:

 > This is my reality.  I am not an emotionally empathetic kind of person
 > and that probably doesn't come as a big surprise to anybody.  Least of
 > all me.  The fact that I then misread people and don't realize (for
 > years) how badly I've judged a situation and contributed to an
 > unprofessional environment is not good.

It has been good, this is easily proven by the quality and success of 
the Linux kernel. If you start being "nice" instead of forthright, every 
excuse in the mental health cookbook will be used to persuade you that 
emotions of the incompetent and their politics, are more important than 
improving the kernel.

 > This week people in our community confronted me about my lifetime of
 > not understanding emotions.  My flippant attacks in emails have been
 > both unprofessional and uncalled for.  Especially at times when I made
 > it personal.  In my quest for a better patch, this made sense to me.
 > I know now this was not OK and I am truly sorry.
 > The above is basically a long-winded way to get to the somewhat
 > painful personal admission that hey, I need to change some of my
 > behavior, and I want to apologize to the people that my personal
 > behavior hurt and possibly drove away from kernel development
 > entirely.

You are not that bad. The incompetent and mentally ill have convinced 
you to act against your best interests, and those of the Linux kernel.

 > I am going to take time off and get some assistance on how to
 > understand people’s emotions and respond appropriately.

Don't try to understand people's emotions, it has not been necessary and 
is not necessary. It is a trap, set to weaken your resolve and standards.

 > To tie this all back to the actual 4.19-rc4 release (no, really, this
 > _is_ related!) I actually think that 4.19 is looking fairly good,
 > things have gotten to the "calm" period of the release cycle, and I've
 > talked to Greg to ask him if he'd mind finishing up 4.19 for me, so
 > that I can take a break, and try to at least fix my own behavior.

 > I know when I really look “myself in the mirror” it will be clear it's
 > not the only change that has to happen, but hey...  You can send me
 > suggestions in email.

I wish you the very best, my hope is that you recuperate & take stock, 
realise how the snakes tricked you and come back with a vengeance.

Kindest Regards,

  parent reply index

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-16 19:22 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 ` Linux 4.19-rc4 released, " Rene Herman
2018-09-17  6:57 ` 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 [this message]
2018-09-18  1:30   ` Pavel Snajdr
2018-09-21 22:13     ` Michael Woods
2018-10-04 14:57     ` ebiederm
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 publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

LKML Archive on

Archives are clonable:
	git clone --mirror lkml/git/0.git
	git clone --mirror lkml/git/1.git
	git clone --mirror lkml/git/2.git
	git clone --mirror lkml/git/3.git
	git clone --mirror lkml/git/4.git
	git clone --mirror lkml/git/5.git
	git clone --mirror lkml/git/6.git
	git clone --mirror lkml/git/7.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ \
	public-inbox-index lkml

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox