From: Shuah Khan <skhan@linuxfoundation.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: gregkh@linuxfoundation.org, corbet@lwn.net,
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>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3] Documentation/CoC: spell out enforcement for unacceptable behaviors
Date: Thu, 14 Nov 2024 08:01:34 -0700 [thread overview]
Message-ID: <2dafc0bb-4dee-4c7e-91b0-01fa66a822aa@linuxfoundation.org> (raw)
In-Reply-To: <5rkn65qu2i3kz72hxbmcg25mrq5ehmb4y6xia2p3k4naiogi44@rcaoz3xnqlcf>
On 11/14/24 07:38, Konstantin Ryabitsev wrote:
> On Wed, Nov 13, 2024 at 04:25:57PM -0700, Shuah Khan wrote:
>> +The scope of the ban for a period of time could include:
>> +
>> + a. denying patch contributions and pull requests
>> + b. pausing collaboration with the violator by ignoring their
>> + contributions and/or blocking their email account(s)
>> + c. blocking their access to kernel.org accounts and mailing lists
>
> Can we change this to:
>
> c. restricting their ability to communicate via kernel.org platforms,
> such as mailing lists and social media sites
>
> It makes more sense to phrase it this way, because it's really the
> communication that is the focus of this policy, not general access like git,
> patchwork, etc.
>
Thank you Konstantin. Correct. The intent is to restrict communication.
The way you phrased it makes perfect sense. I will make the change.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-11-14 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 23:25 Shuah Khan
2024-11-14 14:38 ` Konstantin Ryabitsev
2024-11-14 15:01 ` Shuah Khan [this message]
2024-11-14 15:02 ` Konstantin Ryabitsev
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=2dafc0bb-4dee-4c7e-91b0-01fa66a822aa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox