linux-kernel - Re: [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses

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:   Mon, 8 Oct 2018 09:37:59 +1000
From:   Dave Airlie <airlied@...il.com>
To:     Al Viro <viro@...iv.linux.org.uk>
Cc:     James Bottomley <James.Bottomley@...senpartnership.com>,
        LKML <linux-kernel@...r.kernel.org>,
        ksummit <ksummit-discuss@...ts.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity
 about collecting email addresses

On Mon, 8 Oct 2018 at 08:56, Al Viro <viro@...iv.linux.org.uk> wrote:
>
> On Mon, Oct 08, 2018 at 08:25:35AM +1000, Dave Airlie wrote:
>
> > This isn't a legally binding license or anything, but departing from
> > the upstream wording makes it tricker to merge new upstream versions
> > if they are considered appropriate.
>
> Nicely done, that - gotta love the passive voice use.  Considered appropriate
> *by* *whom*?

Good question, do we have a CoC maintainer? Is Linus it, Greg, TAB?

Maybe step one is to find the person who can make changes to the
kernel CoC (has anyone checked if Linus or Greg will merge this).

>
> Anyway, upstream clearly is a poor fit for Linus kernel community structure
> - the use of open lists, amount of subprojects, the length of transmission
> chains into the mainline, total amount of contributors, amount of people
> elsewhere in the project with occasional forays into any given area, etc.
> And IIRC the CoC upstream's opinion was that it wouldn't fit.

I think we can try, fixing upstream is a worthy goal for other
projects in the same position, rather than everyone diverging.
>
> We can surround it with "explanations" until we get something that more or
> less fits, but then we'd need to reanalyse them every time an upstream
> change gets merged.  And the lack of textual conflicts is not a good thing
> in such situations, obviously.

We do this already for the GPL (hence the GPLv2 only, and syscall exceptions).

Dave.