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]

Message-ID: <3908561D78D1C84285E8C5FCA982C28F7D409730@ORSMSX107.amr.corp.intel.com>
Date:   Mon, 8 Oct 2018 17:05:58 +0000
From:   "Luck, Tony" <tony.luck@...el.com>
To:     Al Viro <viro@...IV.linux.org.uk>, Dave Airlie <airlied@...il.com>
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, 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.

The whole document is under 500 words, if we can manage merges of tens
of thousands of lines of code, this should be pretty easy by comparison.

Making it difficult to merge new upstream versions could also be considered
a positive thing.  Given the outcry about this version appearing with no
community discussion, I think folks will also be unhappy about finding some
future merge that just says "Update CoC to upstream 1.5".

-Tony