linux-kernel - Re: [Ksummit-discuss] [PATCH v2 0/3] code of conduct fixes

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:   Thu, 11 Oct 2018 00:41:05 +0100
From:   Al Viro <viro@...IV.linux.org.uk>
To:     "Eric W. Biederman" <ebiederm@...ssion.com>
Cc:     James Bottomley <James.Bottomley@...senPartnership.com>,
        ksummit-discuss@...ts.linuxfoundation.org,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-discuss] [PATCH v2 0/3] code of conduct fixes

On Wed, Oct 10, 2018 at 06:23:24PM -0500, Eric W. Biederman wrote:

> Which is very problematic.
> a) In append only logs like git we can not edit history.
>    Making it a mainters responsibility to edit the history, to do the
>    impossible is a problem.
> 
> b) There are no responsibilities of for people who are not Maintainers.
>    That is another problem.
> 
> c) The entire tone of the reponsibilities section is out of line with a
>    community where there are no enforcement powers only the power to
>    accept or not accept a patch.  Only the power to persuade not to
>    enforce.

  d) In effect, it either leaves the maillists exempt, or, if they are
     not as would seem to be the intent, dumps physically unsustainable
     load on somebody (davem, by default, for vger-based lists).
     And anyone who wants to claim that moderating l-k, l-scsi, fsdevel,
     etc., etc. is *not* physically unsustainable is welcome to try.
     Just make sure that your insurance covers the psychiatric care you
     are certain to need afterwards.

> Overall in the discussions I have heard people talking about persuading,
> educating, and not feeding trolls.   Nowhere have I heard people talking
> about policing the community which I understand that responsiblity
> section to be talking about.
> 
> Increasingly I am getting the feeling that this document does not the
> linux development community.

Quite.  Not the use of open maillists, not the amount of trees and the
depth of pull chains, not the size of community, not the cross-area work...

Frankly, it reminds me of "well, if everyone had only switched to one true
revision control system and used the one true integrated IDE with this nifty
set of plugins..." kind of proposals.  Good for you if it works for your
workflow, but forget about having everyone else switch to it.