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]

Date:   Sun, 07 Oct 2018 20:18:26 +0300
From:   Laurent Pinchart <laurent.pinchart@...asonboard.com>
To:     ksummit-discuss@...ts.linuxfoundation.org
Cc:     Josh Triplett <josh@...htriplett.org>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        James Bottomley <James.Bottomley@...senpartnership.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors

Hi Josh,

On Sunday, 7 October 2018 14:35:14 EEST Josh Triplett wrote:
> On Sun, Oct 07, 2018 at 10:51:02AM +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.
> > 
> > Avoid any ambiguity by removing the list, to ensure "a harassment-free
> > experience for everyone", period.
> 
> I would suggest reading the commit message that added this in the first
> place. "Explicit guidelines have demonstrated success in other projects
> and other areas of the kernel." See also various comparisons of codes of
> conduct, which make the same point. The point of this list is precisely
> to serve as one such explicit guideline; removing it would rather defeat
> the purpose.
> 
> In any case, this is not the appropriate place for such patches, any
> more than it's the place for patches to the GPL.

So what's an appropriate place to discuss the changes that we would like, 
*together*, to make to the current document and propose upstream ? As stated 
in another e-mail in a similar thread, I believe we need to come together and 
decide on what we want to do. We still have no official forum to do so, and 
repeatedly telling people that ksummit-discuss and LKML are not the right 
place won't make the concerns go away. Only by discussing problems will we 
come to solutions.

-- 
Regards,

Laurent Pinchart