From: Jonathan Corbet <corbet@lwn.net>
To: Shuah Khan <shuah@kernel.org>, gregkh@linuxfoundation.org
Cc: Shuah Khan <shuah@kernel.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, conduct@kernel.org,
tab@lists.linux.dev, Miguel Ojeda <ojeda@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v2] Documentation/CoC: Spell out the TAB role in enforcement decisions
Date: Wed, 12 Mar 2025 16:32:22 -0600 [thread overview]
Message-ID: <87senhlw21.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250306211231.13154-1-shuah@kernel.org>
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
prev parent reply other threads:[~2025-03-12 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 21:12 Shuah Khan
2025-03-06 21:18 ` Dan Williams
2025-03-12 22:32 ` Jonathan Corbet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87senhlw21.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=conduct@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tab@lists.linux.dev \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox