linux-kernel - Re: [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]

Message-ID: <6b0d5ad6-c76b-8dbf-bd74-de352280e780@iki.fi>
Date:   Thu, 11 Oct 2018 09:39:45 +0300
From:   Tomi Valkeinen <tomi.valkeinen@....fi>
To:     James Bottomley <James.Bottomley@...senPartnership.com>,
        ksummit-discuss@...ts.linuxfoundation.org
Cc:     linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/3] code of conduct fixes

On 10/10/18 23:07, James Bottomley wrote:
> Resend to show accumulated tags and also to add a third patch listing
> the TAB as the reporting point as a few people seem to want.  If it
> gets the same level of support, I'll send it in with the other two.
> 
> ---
> 
> Previous cover letter:
> 
> 
> We've had several threads discussing potential changes to the code of
> conduct but Mauro is the only person to have proposed an actual patch. 
> In order to move the debate on, I'm presenting two patches, one to fix
> the email problem Mauro identified and the other to strip the
> enforcement section pending community discussion as Shuah suggested.
> 
> I'll take responsibility for collecting any tags people want to add
> (review/ack/sign off, etc) and sending the patch in as a signed pull
> request before 4.19 final if they get enough community support.
> 
> Note, I've sent both patches in as a series to facilitate review and
> discussion, but they are separable if one is looked on with less favour
> than the other.
> 
> It was also a bit unclear which list to send this to, but I finally
> settled on linux-kernel as the catch all and ksummit-discuss since
> that's where most of the current discussion is.  I can add other lists
> as people suggest them.
> 
> James
> 
> ---
> 
> James Bottomley (3):
>   code-of-conduct: Fix the ambiguity about collecting email addresses
>   code-of-conduct: Strip the enforcement paragraph pending community
>     discussion
>   code-of-conduct: Add back the TAB as the central reporting point
> 
>  Documentation/process/code-of-conduct.rst | 13 ++++---------
>  1 file changed, 4 insertions(+), 9 deletions(-)
> 

For the three patches (preferably with Alan's "except where required by
law"):

Acked-by: Tomi Valkeinen <tomi.valkeinen@....fi>

Although I think reverting 8a104f8b5867c682 is the best option.

 Tomi