LKML Archive on
 help / Atom feed
From: Michael Woods <>
To: Pavel Snajdr <>
Subject: Re: Linux 4.19-rc4 released, an apology, and a maintainership note
Date: Fri, 21 Sep 2018 23:13:08 +0100
Message-ID: <> (raw)
In-Reply-To: <>

Hi Pavel,

> and how about if we viewed the new Code of Conduct as about the same 
> thing as BitKeeper was for the development process?
You should view the Code of Conduct for what it is, as I referenced 
previously with real world examples, the evidence shows that it is just 
a ploy to take control away from the competent and give it to the 

An example of the hypocrisy Linus is in for:
a) From Coraline Ada Ehmke's Code of Conduct:
> Our Standards
> Examples of behavior that contributes to creating a positive environment
> include:
> * Using welcoming and inclusive language
> Examples of unacceptable behavior by participants include:
> * Trolling, insulting/derogatory comments, and personal or political 
> attacks
> * Public or private harassment
> * Other conduct which could reasonably be considered inappropriate in a
> professional setting
> Coraline Ada Ehmke, @CoralineAda
> 40,000 open source projects, including Linux, Rails, Golang, and 
> everything OSS produced by Google, Microsoft, and Apple have adopted 
> my code of conduct.
> You can make me have a bad day, but it doesn’t change the fact that we 
> have won and you have lost.
In software projects, there will be no "calling out" of bad behaviour 
for the self identifed victims this was written for, whom are invariably 
the least useful contributors and most capable of inventing victim 
narratives. The CoC will be used by the mentally ill and incapable to 
create accusations for attacking competent individuals.

> It was not perfect, but wass *something* for a start.
A Code of Conduct is not required, to the contrary, all successful 
software projects, if they wish to remain so, should never adopt one. I 
previously referenced preferable alternatives.

> I've been always looking up to the guys leading major community 
> projects and how they go about things - and I think, that most of the 
> bad fall-out in them is caused by insanely high expectations - firstly 
> from the leader themselves, and secondly from others as well.
Linus has excelled up to this point, the Code of Conduct will stifle his 
ability to maintain the kernel.

> The new Code of Conduct is a guarantee for us, that we won't be 
> laughed out of the room  and that our members won't be demotivated to 
> contribute upstream - if we can all agree to be nice on each other; 
> yet we still need you guys to tell us, when we're trying stupid things 
> or going about things the wrong way, in some way that we will notice & 
> can learn from.
The one thing you do not understand, which is key to understanding why 
complex projects are successful, most people are not intelligent enough 
to contribute. Their contributions if accepted, would create chaos, and 
if not simply rejected, would create long backlogs due to the amount of 
effort required to explain why their code is not of the standard required.

> If I understand the context correctly, the previous "regime" could be 
> the culprit, at least to some extent, why still don't have the VM 
> look&feel-having containers with vanilla. So I'm just really trying to 
> say, that I'm really excited about the signal this change has sent.
This is not a believable position, that you were waiting for a Code of 
Conduct before contributing successfully to the Linux Kernel.


  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
2018-09-18  1:30   ` Pavel Snajdr
2018-09-21 22:13     ` Michael Woods [this message]
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