linux-kernel - Re: [PATCH] Documentation/CoC: Spell out the TAB role in enforcement decisions

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: <20250304200947.GF30583@pendragon.ideasonboard.com>
Date: Tue, 4 Mar 2025 22:09:47 +0200
From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
To: Shuah Khan <shuah@...nel.org>
Cc: gregkh@...uxfoundation.org, corbet@....net, workflows@...r.kernel.org,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	conduct@...nel.org, tab@...ts.linux.dev,
	Miguel Ojeda <ojeda@...nel.org>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH] Documentation/CoC: Spell out the TAB role in enforcement
 decisions

Hi Shuah,

Thank you for the patch.

On Tue, Mar 04, 2025 at 12:48:12PM -0700, Shuah Khan wrote:
> Updates to clarify and spell out the TAB role in approving and overturning
> enforcement measures for Code of Conduct violations.

As with any technical change, I think it would help reviewers if the
commit message could explain *why* this change is appropriate at this
time. For instance, it would be good to know if this is meant to ensure
the document clearly describes the existing practices without a change
of rules, or if there's another reason.

Without an explanation of the intent, the CoC and TAB would appear more
opaque, especially given the tags present on v1 that shows the patch has
been discussed behind closed doors.

> Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Acked-by: Miguel Ojeda <ojeda@...nel.org>
> Acked-by: Steven Rostedt <rostedt@...dmis.org>
> Acked-by: Jonathan Corbet <corbet@....net>
> Signed-off-by: Shuah Khan <shuah@...nel.org>
> ---
>  .../process/code-of-conduct-interpretation.rst  | 17 +++++++++++------
>  1 file changed, 11 insertions(+), 6 deletions(-)
> 
> diff --git a/Documentation/process/code-of-conduct-interpretation.rst b/Documentation/process/code-of-conduct-interpretation.rst
> index 1d1150954be3..4cdef8360698 100644
> --- a/Documentation/process/code-of-conduct-interpretation.rst
> +++ b/Documentation/process/code-of-conduct-interpretation.rst
> @@ -145,13 +145,16 @@ kernel community.
>  
>  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.
> +if needed.  Once the TAB approves one or more of the measures outlined
> +in the scope of the ban by two-thirds of the members voting for the

There was no mention of "ban" in this section, is the addition of that
word on purpose ?

> +measures, the Code of Conduct Committee will enforce the TAB approved
> +measures.  Any Code of Conduct Committee members serving on the TAB will
> +not vote on the measures.

We're switching from a 2/3 majority to *not* implement a recommendation
to a 2/3 majority to implement it. Without judging the merit of this (at
first sight I feel positive about the change), I think it's worth
explaining why.

>  
>  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.
> +TAB approved 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
> @@ -227,9 +230,11 @@ The scope of the ban for a period of time could include:
>         such as mailing lists and social media sites
>  
>  Once the TAB approves one or more of the measures outlined in the scope of
> -the ban by a two-thirds vote, the Code of Conduct Committee will enforce
> -the TAB approved measure(s) in collaboration with the community, maintainers,
> -sub-maintainers, and kernel.org administrators.
> +the ban by two-thirds of the members voting for the measures, the Code of
> +Conduct Committee will enforce the TAB approved measure(s) in collaboration
> +with the community, maintainers, sub-maintainers, and kernel.org
> +administrators.  Any Code of Conduct Committee members serving on the TAB
> +will not vote on the measures.
>  
>  The Code of Conduct Committee is mindful of the negative impact of seeking
>  public apology and instituting ban could have on individuals. It is also

-- 
Regards,

Laurent Pinchart