[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <67ca110c9ce4b_1a7729493@dwillia2-xfh.jf.intel.com.notmuch>
Date: Thu, 6 Mar 2025 13:18:04 -0800
From: Dan Williams <dan.j.williams@...el.com>
To: Shuah Khan <shuah@...nel.org>, <gregkh@...uxfoundation.org>,
<corbet@....net>
CC: Shuah Khan <shuah@...nel.org>, <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 v2] Documentation/CoC: Spell out the TAB role in
enforcement decisions
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@...uxfoundation.org>
> Acked-by: Miguel Ojeda <ojeda@...nel.org>
> Acked-by: Steven Rostedt <rostedt@...dmis.org>
> Acked-by: Jonathan Corbet <corbet@....net>
Acked-by: Dan Williams <dan.j.williams@...el.com>
Powered by blists - more mailing lists