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] [day] [month] [year] [list]

Message-ID: <20180929124628.GB23354@thyrsus.com>
Date:   Sat, 29 Sep 2018 08:46:28 -0400
From:   "Eric S. Raymond" <esr@...rsus.com>
To:     Alan Cox <gnomes@...rguk.ukuu.org.uk>
Cc:     Bernd Petrovitsch <bernd@...rovitsch.priv.at>,
        xDynamite <dreamingforward@...il.com>,
        "jonsmirl@...il.com" <jonsmirl@...il.com>,
        Theodore Tso <tytso@....edu>, fche@...hat.com,
        riel@...riel.com, ec429@...tab.net,
        Olof Johansson <olof@...om.net>,
        Jonathan Corbet <corbet@....net>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: Code of Conduct: Let's revamp it.

(I mistakenly sent this with 'r' previously. Please reply to this copy.)

Alan Cox <gnomes@...rguk.ukuu.org.uk>:
> The wording IMHO just needs tightening up - and that's a useful
> discussion that ought to he bad. I tihnk everyone understands the *inent*
> of such wording - don't go around doxing people, or posting their home
> address on facebook and calling for people to attend with pitchforks.

I'm going to, again, avoid normative statements and try to clarify what
the questions are here, speaking from my anthropologist/game-theorist head.

As a matter of process, there are two different sets of issues about changing
the CoC wording.  Referring to my previous post on ethos and telos:

       https://lkml.org/lkml/2018/9/23/212

1. The wording needs to be tweaked to make it clearer what things are against
the ethos. For example: we may want Code violations to include hateful speech
on the mailing list directed at other LKML members.  Does it follow that
we want the Code to proscribe "hate speech" directed against third parties,
or off-list "hateful" behavior? Perhaps we do, perhaps not; but either
way the boundaries need to be clearer.

2. The language needs to be examined with particular care to discover
where it implies a change to LKML's telos. I argue no position at this time
about whether LKML's telos *should* change, but I note that the rather heated
dissent the CoC has provoked comes from a widespread perception that it *is*, in
fact, a none-too-covert attempt to alter the telos.

I further note that this perception is supported by the CoC Author's
"Post-Meritocracy manifesto".

        https://postmeritocracy.org/

Kernel contributors, understandably, want a clear read on whether the
application of the CoC is to be guided by meritocratic or
"post-meritocratic" principles.  This is a telos issue, not just
an ethos issue, and much more fundamental.

I endorse a suggestion made elsewhere that a revised CoC would best be
developed by an RFC-like process. Because *that is how we do such things*;
that is *our* culture's mechanism for achieving and maintaining consensus
on difficult issues.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.