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 for Android: free password hash cracker in your pocket

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

Message-ID: <1a51fc4c-882c-59ef-7497-262e595af10e@roeck-us.net>
Date:   Wed, 17 Oct 2018 06:32:36 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>,
        Josh Triplett <josh@...htriplett.org>
Cc:     James Bottomley <James.Bottomley@...senpartnership.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        ksummit-discuss@...ts.linuxfoundation.org, tomi.valkeinen@....fi
Subject: Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list
 of discrimination factors

On 10/17/2018 02:31 AM, Geert Uytterhoeven wrote:
> Hi Josh,
> 
> Thanks for your comments!
> 
> On Wed, Oct 17, 2018 at 11:13 AM Josh Triplett <josh@...htriplett.org> 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.
> 
> The CoC FAQ is not part of the CoC, and not part of the Linux kernel.
> If the CoC is imprecise, it should be fixed in the CoC, not in a separate
> document hosted elsewhere, as discussed elsewhere.
> 
> Comparison with the GPL and the GPL FAQ is not appropriate, as the GPL
> is still the precise legal document, while its FAQ is a clarification using
> laymen's terms.
> 
>> 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
> 
> Given the original commit was not submitted for and objected to public
> review, nobody had the chance to question these statements, and ask for
> pointers of proof, which would surely have happened.
> 
>> refers to. Listing explicit cases to cover does not imply other cases
>> are not covered;
> 
> It does, if not accompanied by "examples of...", like in the other sections.
> 
>> it does, however, ensure that the listed cases *are*,
>> and helps people know that they're covered.
> 
> So you agree people cannot know if the unlisted cases are covered or not?
> 
>> This patch is not OK, and defeats one of the purposes of the original
>> change.
> 
> So the purpose of the original change was to list a number of factors,
> without saying that it was just a list of examples?

One could consider adding something like "discrimination factors such as",
or maybe "or any other discrimination factors not listed here" to the
original text. Or a simple "regardless of, for example, ...".

Guenter