linux-kernel - Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors

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: <c28df7c4-eb3f-3864-862c-edc330a8fce8@roeck-us.net>
Date:   Wed, 17 Oct 2018 06:45:22 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Josh Triplett <josh@...htriplett.org>,
        Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     James Bottomley <James.Bottomley@...senpartnership.com>,
        linux-kernel@...r.kernel.org,
        ksummit-discuss@...ts.linuxfoundation.org,
        Tomi Valkeinen <tomi.valkeinen@....fi>
Subject: Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list
 of discrimination factors

On 10/17/2018 02:13 AM, Josh Triplett wrote:
> On Wed, Oct 17, 2018 at 09:19:01AM +0200, Geert Uytterhoeven wrote:
>> Providing an explicit list of discrimination factors may give the false
>> impression that discrimination based on other unlisted factors would be
>> allowed.
> 
> This impression is, in fact, false, as has already been discussed
> elsewhere. I had hoped that discussion would suffice.
> 
> As mentioned there: The original commit explicitly said "Explicit
> guidelines have demonstrated success in other projects and other areas
> of the kernel."; this is precisely the kind of explicit guideline it
> refers to. Listing explicit cases to cover does not imply other cases
> are not covered; it does, however, ensure that the listed cases *are*,
> and helps people know that they're covered.
> 

That is really a matter of opinion. Mathematically speaking, your statement
is incorrect. One may wonder why the list is made explicit without hint
that it is an example. For example, political or social views are _not_
listed. Wasn't the same CoC used in other projects to at least try to
punish individuals with specific political and/or social opinions,
just for having those opinions and expressing them outside the scope of
the project ?

> This patch is not OK, and defeats one of the purposes of the original
> change.

The CoC, as it stands, singles out maintainers for enforcement action.
Based on your statement, is it correct to assume that this was on
purpose ? If not, what is the explicit list of purposes of the
original change ?

Guenter