linux-kernel - Re: [Ksummit-discuss] [PATCH v2 2/3] code-of-conduct: Strip the enforcement paragraph pending community discussion

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] [day] [month] [year] [list]

Message-ID: <CAGXu5jKKK76KRpujbudHQWwtcRHSKEQwBeGMBJf=31WjdCJA4A@mail.gmail.com>
Date:   Mon, 15 Oct 2018 14:02:23 -0700
From:   Kees Cook <keescook@...omium.org>
To:     "Luck, Tony" <tony.luck@...el.com>
Cc:     James Bottomley <James.Bottomley@...senpartnership.com>,
        "ksummit-discuss@...ts.linuxfoundation.org" 
        <ksummit-discuss@...ts.linuxfoundation.org>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-discuss] [PATCH v2 2/3] code-of-conduct: Strip the
 enforcement paragraph pending community discussion

On Wed, Oct 10, 2018 at 2:04 PM, Luck, Tony <tony.luck@...el.com> wrote:
>> the enforcement clause of the new code of conduct.  Since there is concern
>> that this becomes binding on the release of the 4.19 kernel
>
> Is there some logic behind that concern? What's magic about the release
> of 4.19?

Greg KH said 4.19 was going to be the next LTS. But, regardless, if we
view bugs in the CoC as "just bugs", then can't we also include their
fixes in -stable? It'll land in 4.19.z just like anything else. I
don't think we need to rush anything into 4.19 -- as so many others
have said: it's in our best interest to take the time to get the CoC
right.

-Kees

-- 
Kees Cook
Pixel Security