linux-kernel - Re: [PATCH] Documentation/CoC: spell out enforcement for unacceptable behaviors

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: <2b1f6b86-0d56-445e-bed0-1e33b9882d48@infradead.org>
Date: Fri, 8 Nov 2024 12:08:17 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Shuah Khan <skhan@...uxfoundation.org>, gregkh@...uxfoundation.org,
 corbet@....net
Cc: workflows@...r.kernel.org, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org, Linus Torvalds
 <torvalds@...ux-foundation.org>, Miguel Ojeda <ojeda@...nel.org>,
 Dave Hansen <dave.hansen@...ux.intel.com>,
 Steven Rostedt <rostedt@...dmis.org>, Dan Williams <dan.j.williams@...el.com>
Subject: Re: [PATCH] Documentation/CoC: spell out enforcement for unacceptable
 behaviors

Hi--

On 11/8/24 8:18 AM, Shuah Khan wrote:
> The Code of Conduct committee's goal first and foremost is to bring about
> change to ensure our community continues to foster respectful discussions.
> 
> In the interest of transparency, the CoC enforcement policy is formalized
> for unacceptable behaviors.
> 
> Update the Code of Conduct Interpretation document with the enforcement
> information.
> 
> Acked-by: Linus Torvalds <torvalds@...ux-foundation.org>
> Acked-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Acked-by: Miguel Ojeda <ojeda@...nel.org>
> Acked-by: Dave Hansen <dave.hansen@...ux.intel.com>
> Acked-by: Jonathan Corbet <corbet@....net>
> Acked-by: Steven Rostedt <rostedt@...dmis.org>
> Acked-by: Dan Williams <dan.j.williams@...el.com>
> Signed-off-by: Shuah Khan <skhan@...uxfoundation.org>
> ---
>  .../code-of-conduct-interpretation.rst        | 52 +++++++++++++++++++
>  1 file changed, 52 insertions(+)
> 
> diff --git a/Documentation/process/code-of-conduct-interpretation.rst b/Documentation/process/code-of-conduct-interpretation.rst
> index 66b07f14714c..21dd1cd871d2 100644
> --- a/Documentation/process/code-of-conduct-interpretation.rst
> +++ b/Documentation/process/code-of-conduct-interpretation.rst
> @@ -156,3 +156,55 @@ overridden decisions including complete and identifiable voting details.
>  Because how we interpret and enforce the Code of Conduct will evolve over
>  time, this document will be updated when necessary to reflect any
>  changes.
> +
> +Enforcement for Unacceptable Behavior Code of Conduct Violations
> +----------------------------------------------------------------
> +
> +The Code of Conduct committee works to ensure that our community continues
> +to be inclusive and fosters diverse discussions and viewpoints, and works
> +to improve those characteristics over time. The Code of Conduct committee
> +takes measures to restore productive and respectful collaboration when an
> +unacceptable behavior has negatively impacted that relationship.
> +
> +Seek public apology for the violation
> +*************************************
> +

According to Documentation/doc-guide/sphinx.rst, kernel documentation tries to
use "~~~~~~~~~~~~~~~~~~~" for subsections (not "******************").

This is not enforced -- it's more of a guideline.

Thanks.

-- 
~Randy