linux-kernel - Re: [PATCH] Documentation/CoC: Reflect current CoC interpretation and practices

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: <87h70tpw6d.fsf@meer.lwn.net>
Date:   Mon, 26 Sep 2022 17:12:26 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Kristen Carlson Accardi <kristen@...ux.intel.com>,
        linux-doc@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Kristen Carlson Accardi <kristen@...ux.intel.com>,
        Shuah Khan <skhan@...uxfoundation.org>,
        linux-kernel@...r.kernel.org,
        LF TAB <tech-board@...ts.linux-foundation.org>
Subject: Re: [PATCH] Documentation/CoC: Reflect current CoC interpretation
 and practices

Kristen Carlson Accardi <kristen@...ux.intel.com> writes:

> The Code of Conduct interpretation does not reflect the current
> practices of the CoC committee or the TAB. Update the documentation
> to remove references to initial committees and boot strap periods
> since it is past that time, and note that the this document
> does serve as the documentation for the CoC committee processes.

Since this takes the TAB's name in vain, they should probably be CC'd on
it; I've added that now.

Thanks,

jon

> Signed-off-by: Kristen Carlson Accardi <kristen@...ux.intel.com>
> Reviewed-by: Shuah Khan <skhan@...uxfoundation.org>
> Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> ---
>  .../code-of-conduct-interpretation.rst        | 24 ++++++++++---------
>  1 file changed, 13 insertions(+), 11 deletions(-)
>
> diff --git a/Documentation/process/code-of-conduct-interpretation.rst b/Documentation/process/code-of-conduct-interpretation.rst
> index 4f8a06b00f60..922e0b547bc3 100644
> --- a/Documentation/process/code-of-conduct-interpretation.rst
> +++ b/Documentation/process/code-of-conduct-interpretation.rst
> @@ -127,10 +127,12 @@ are listed at https://kernel.org/code-of-conduct.html.  Members can not
>  access reports made before they joined or after they have left the
>  committee.
>  
> -The initial Code of Conduct Committee consists of volunteer members of
> -the TAB, as well as a professional mediator acting as a neutral third
> -party.  The first task of the committee is to establish documented
> -processes, which will be made public.
> +The Code of Conduct Committee consists of volunteer community members
> +appointed by the TAB, as well as a professional mediator acting as a
> +neutral third party.  The processes the Code of Conduct committee will
> +use to address reports is varied and will depend on the individual
> +circumstance, however, this file serves as documentation for the
> +general process used.
>  
>  Any member of the committee, including the mediator, can be contacted
>  directly if a reporter does not wish to include the full committee in a
> @@ -141,16 +143,16 @@ processes (see above) and consults with the TAB as needed and
>  appropriate, for instance to request and receive information about the
>  kernel community.
>  
> -Any decisions by the committee will be brought to the TAB, for
> -implementation of enforcement with the relevant maintainers if needed.
> -A decision by the Code of Conduct Committee can be overturned by the TAB
> -by a two-thirds vote.
> +Any decisions regarding enforcement recommendations will be brought to
> +the TAB for implementation of enforcement with the relevant maintainers
> +if needed.  A decision by the Code of Conduct Committee can be overturned
> +by the TAB by a two-thirds vote.
>  
>  At quarterly intervals, the Code of Conduct Committee and TAB will
>  provide a report summarizing the anonymised reports that the Code of
>  Conduct committee has received and their status, as well details of any
>  overridden decisions including complete and identifiable voting details.
>  
> -We expect to establish a different process for Code of Conduct Committee
> -staffing beyond the bootstrap period.  This document will be updated
> -with that information when this occurs.
> +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.
> -- 
> 2.37.3