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:   Sat, 6 Oct 2018 21:43:00 +0000
From:   <Tim.Bird@...y.com>
To:     <James.Bottomley@...senPartnership.com>,
        <ksummit-discuss@...ts.linuxfoundation.org>
CC:     <linux-kernel@...r.kernel.org>
Subject: RE: [Ksummit-discuss] [PATCH 2/2] code-of-conduct: Strip the
 enforcement paragraph pending community discussion

> -----Original Message-----
> From: James Bottomley
> 
> Significant concern has been expressed about the responsibilities outlined in
> 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, strip the
> enforcement clauses to give the community time to consider and debate
> how this
> should be handled.
> 
> Signed-off-by: James Bottomley
> <James.Bottomley@...senPartnership.com>
> ---
>  Documentation/process/code-of-conduct.rst | 15 ---------------
>  1 file changed, 15 deletions(-)
> 
> diff --git a/Documentation/process/code-of-conduct.rst
> b/Documentation/process/code-of-conduct.rst
> index aa40e34e7785..4dd90987305b 100644
> --- a/Documentation/process/code-of-conduct.rst
> +++ b/Documentation/process/code-of-conduct.rst
> @@ -59,21 +59,6 @@ address, posting via an official social media account, or
> acting as an appointed
>  representative at an online or offline event. Representation of a project may
> be
>  further defined and clarified by project maintainers.
> 
> -Enforcement
> -===========
> -
> -Instances of abusive, harassing, or otherwise unacceptable behavior may be
> -reported by contacting the Technical Advisory Board (TAB) at
> -<tab@...ts.linux-foundation.org>. All complaints will be reviewed and
> -investigated and will result in a response that is deemed necessary and
> -appropriate to the circumstances. The TAB is obligated to maintain
> -confidentiality with regard to the reporter of an incident.  Further details of
> -specific enforcement policies may be posted separately.

I think it's OK to leave the above section, as it doesn't speak to
enforcement, but rather is just a set of reporting instructions,
with an assurance of confidentiality.  This seems to me not to be
the objectionable part of this section.
(IOW, I would omit this removal from the patch).

If the next part is indeed removed, then maybe the section
needs to be renamed?
 -- Tim

> -
> -Maintainers who do not follow or enforce the Code of Conduct in good faith
> may
> -face temporary or permanent repercussions as determined by other
> members of the
> -project’s leadership.
> -
>  Attribution
>  ===========

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ