[PATCH v2] Documentation/CoC: Spell out the TAB role in enforcement decisions

[PATCH v2] Documentation/CoC: Spell out the TAB role in enforcement decisions

[Shuah Khan]

Updates the document to clearly describe the scope and role the TAB plays
in making decisions on unresolved violations. If and when the CoC has to
make a call on instituting a ban, it doesn't act without the TAB's approval
and only when the TAB approves it with 2/3 vote in favor of the measure.

These changes ensure that the TAB role and its oversight on CoC measures
is consistently described throughout the document.

Fixes: c818d5c64c9a8cc1 ("Documentation/CoC: spell out enforcement for unacceptable behaviors")

Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Miguel Ojeda <ojeda@kernel.org>
Acked-by: Steven Rostedt <rostedt@goodmis.org>
Acked-by: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Shuah Khan <shuah@kernel.org>
---
v1 - v2:
- Reword change log to better describe the changes and updates.
- Add Fixes tag

 .../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
+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.
 
 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
-- 
2.45.2

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

[Dan Williams]

Shuah Khan wrote:
> Updates the document to clearly describe the scope and role the TAB plays
> in making decisions on unresolved violations. If and when the CoC has to
> make a call on instituting a ban, it doesn't act without the TAB's approval
> and only when the TAB approves it with 2/3 vote in favor of the measure.
> 
> These changes ensure that the TAB role and its oversight on CoC measures
> is consistently described throughout the document.
> 
> Fixes: c818d5c64c9a8cc1 ("Documentation/CoC: spell out enforcement for unacceptable behaviors")
> 
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Acked-by: Miguel Ojeda <ojeda@kernel.org>
> Acked-by: Steven Rostedt <rostedt@goodmis.org>
> Acked-by: Jonathan Corbet <corbet@lwn.net>

Acked-by: Dan Williams <dan.j.williams@intel.com>

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

[Jonathan Corbet]

Shuah Khan <shuah@kernel.org> writes:

> Updates the document to clearly describe the scope and role the TAB plays
> in making decisions on unresolved violations. If and when the CoC has to
> make a call on instituting a ban, it doesn't act without the TAB's approval
> and only when the TAB approves it with 2/3 vote in favor of the measure.
>
> These changes ensure that the TAB role and its oversight on CoC measures
> is consistently described throughout the document.
>
> Fixes: c818d5c64c9a8cc1 ("Documentation/CoC: spell out enforcement for unacceptable behaviors")
>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Acked-by: Miguel Ojeda <ojeda@kernel.org>
> Acked-by: Steven Rostedt <rostedt@goodmis.org>
> Acked-by: Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Shuah Khan <shuah@kernel.org>
> ---
> v1 - v2:
> - Reword change log to better describe the changes and updates.
> - Add Fixes tag
>
>  .../process/code-of-conduct-interpretation.rst  | 17 +++++++++++------
>  1 file changed, 11 insertions(+), 6 deletions(-)

I have applied this, thanks.

jon