From: Shuah Khan <skhan@linuxfoundation.org>
To: Jonathan Corbet <corbet@lwn.net>, gregkh@linuxfoundation.org
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rdunlap@infradead.org,
daniel@ffwll.ch, laurent.pinchart@ideasonboard.com,
broonie@kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Miguel Ojeda <ojeda@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
Dan Williams <dan.j.williams@intel.com>,
Theodore Ts'o <tytso@mit.edu>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v4] Documentation/CoC: spell out enforcement for unacceptable behaviors
Date: Fri, 15 Nov 2024 14:41:48 -0700 [thread overview]
Message-ID: <0868e182-aa37-48c7-9dd0-ae4f6819c71a@linuxfoundation.org> (raw)
In-Reply-To: <87ttc8ji84.fsf@trenco.lwn.net>
On 11/15/24 14:32, Jonathan Corbet wrote:
> Shuah Khan <skhan@linuxfoundation.org> writes:
>
>> The Code of Conduct committee's goal first and foremost is to bring about
>> change to ensure our community continues to foster respectful discussions.
>>
>> In the interest of transparency, the CoC enforcement policy is formalized
>> for unacceptable behaviors.
>>
>> Update the Code of Conduct Interpretation document with the enforcement
>> information.
>>
>> Acked-by: Linus Torvalds <torvalds@linux-foundation.org>
>> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Acked-by: Miguel Ojeda <ojeda@kernel.org>
>> Acked-by: Dave Hansen <dave.hansen@linux.intel.com>
>> Acked-by: Jonathan Corbet <corbet@lwn.net>
>> Acked-by: Steven Rostedt <rostedt@goodmis.org>
>> Acked-by: Dan Williams <dan.j.williams@intel.com>
>> Acked-by: Theodore Ts'o <tytso@mit.edu>
>> Acked-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
>> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
>> ---
>>
>> Changes since v3:
>> - Modifies kernel.org actions as per Konstantin's comments
>> - Adds Konstantin's Ack
>>
>> Changes since v2:
>> - Adds details on the process leading up to the proposed
>> measures to seek public apology and bans for serious
>> unacceptable behaviors.
>>
>> - Hope this addresses your comments, Daniel Vetter,
>> Laurent Pinchart, and Mark Brown.
>>
>> - Would like to get this into 6.12 if at all possible.
>>
>> Changes since v1:
>> - Updates Acks with Ted's ack.
>> - Fixes subsection formatting as per Randy's suggestion.
>> - Fixes a spelling error.
>>
>> .../code-of-conduct-interpretation.rst | 87 +++++++++++++++++++
>> 1 file changed, 87 insertions(+)
>
> We seem to have reached a conclusion on this, so I have applied it.
>
> Thanks,
>
Thank you Jon.
-- Shuah
prev parent reply other threads:[~2024-11-15 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 20:56 [PATCH v4] Documentation/CoC: spell out enforcement for unacceptable behaviors Shuah Khan
2024-11-15 20:44 ` Kees Cook
2024-11-15 21:32 ` Jonathan Corbet
2024-11-15 21:41 ` Shuah Khan [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=0868e182-aa37-48c7-9dd0-ae4f6819c71a@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=daniel@ffwll.ch \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.