LKML Archive on
 help / Atom feed
From: opal hart <>
Subject: Re: Linux 4.19-rc4 released, an apology, and a maintainership note
Date: Mon, 17 Sep 2018 06:57:12 +0000
Message-ID: <20180917065712.45d321f9@clamav.local> (raw)
In-Reply-To: <>

The new kernel rc release is good news as always. The rest of this? not
so much.

"I can’t wait for the mass exodus from Linux now that it’s been
infiltrated by SJWs. Hahahah" -- @CoralineAda on Twitter [1][2]

You really want people like this attempting to sabotage FOSS projects?
I for one am not discontinuing usage of Linux over any political BS,
and I believe it is foolish for anyone to leave any software project
over politics, but that does not mean I welcome political agendas in
software development.

Your old Code of Conflict was perfect and succinct. If someone cannot
use their head to figure out what is right or wrong to say in a mailing
list or a commit message, that person is unfit for contributing to
software in general. This doesn't need to be spelled out for anyone. We
didn't need to explicitly bar discriminatory speech from software
discussion, because software discussion was never the place to have
discrimination against people -- it only allows for discrimination
against shitty code. You, Linus, have never attacked anyone from what I
have seen; you have only attacked poorly-decided actions, which is
perfectly justified. People who really want to contribute to Linux dust
their shoulders off, take your criticism, and figure out how to
re-approach you depending on what they did that was not to your taste.
Anyone who shies away from criticism is IMO unfit to contribute in the
first place. I mean, yes, there are ways to get your criticisms across
in a more "constructive" tone, but this does not call for any code of
conduct. Maybe you do need to take time to figure out how you want to
approach the community, but don't take it that you *have* to do
anything. You don't have to do a thing. People will still use Linux
regardless. People who care about Linux will continue to contribute to
it, because they do not take your words personally (nor should they).

This Code of Conduct trend is nothing but a concern-trolling campaign
that people carry out in order to gain control over projects,
organisations, and communities. Everyone is best off if we do not give
these people the control they desire. Take their demands with a grain
of salt: they suggest a boilerplate Code of Conduct, you decide which
parts from which Linux can benefit, if any.


This is just another two cents from a fellow faceless transgender woman
on the Internet, yours truly,
wowaname <>
Please use detailed subject lines and reply below quoted text
whenever possible.

  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 [this message]
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     ` 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 \
    --in-reply-to=20180917065712.45d321f9@clamav.local \ \ \ \

* 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