linux-kernel - Re: Code of Conduct: Let's revamp it.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <DnnwxXkM3V-CPhN11s-t3iwjDgZk30XHfaU7PmR7ZBCDsnmVDMtdIcKwVP7Zx420ZA1ai_RPw7Po-tw7ol2HkzfvXY_-6LA2L6QJ3hYIOyQ=@protonmail.com>
Date:   Fri, 21 Sep 2018 02:16:26 +0000
From:   unixing <unixing@...tonmail.com>
To:     Rik van Riel <riel@...riel.com>
Cc:     Edward Cree <ec429@...tab.net>, Olof Johansson <olof@...om.net>,
        Jonathan Corbet <corbet@....net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Code of Conduct: Let's revamp it.

On Friday, September 21, 2018 1:48 AM, Rik van Riel <riel@...riel.com> wrote:

> On Thu, 2018-09-20 at 03:14 +0100, Edward Cree wrote:
>
> > I think there are important differences between code to be run by
> > CPUs
> > and a Code to be run by humans. And when the author goes on a
> > victory
> > lap on Twitter and declares the Code to be "a political document",
> > is
> > it any surprise I'm worried?
>
> Speaking for myself, I expect there will be occasional
> impedance mismatches in communication between people
> from different cultures, and people with different
> neurotypes.
>
> That is not only expected, it is also perfectly fine.
>
> If people end up feeling like they are in conflict
> with each other, and they would like help resolving
> it, the first task of the TAB will be to mediate,
> and help people figure out how communication could
> be improved.
>
> The goal of the code of conduct is to make the community
> welcoming, and to help people with being a part of the
> Linux community.
>
> Mediation is not about telling people what to do,
> but about asking the people involved what they would
> like to see, and helping to breach the gap between
> their styles of communication.
>
> As an aside, the TAB has no power to remove anyone
> from the community. Patches are applied by maintainers,
> mailing lists are run by their administrators.
>
> The only things the TAB can do is mediate and advise.

That couldn't be more wrong. The existence of a TAB itself
is the problem. The community will be pushed to behave
according to what TAB expects to, otherwise the person will
be shamed and could even have their job jeopardized.
The world currently is walking towards a culture where everyone claimed to be oppressed becomes a mini dictator that can force,
shame, offend. I borrow the words of a wise man who's no longer
alive: “All of it began the first time some of you who know
bettet... let young people think that they had the right to
choose the laws they would obey as long as they were doing it in
the name of social protest.”
I'm using a phony e-mail because I don't feel "job-wise" safe to
criticize this culture, as the punishment is to lose job, end
career, end social life, etc.

I ask our fellows linuxers to not allow this culture to take over
our community. If the current code of conflict isn't working, let's
create a new one, politically NEUTRAL, and without any set of people
with power to dictate the behavior of thousands of engineers. Linux
is NOT a hostile place to work. According to this culture, I am a
minority, coming from third world country who found on Linux
community (since kernel 2.4) a very good source of knowledge and
freedom.

Kind regards,

Unixing