[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5rkn65qu2i3kz72hxbmcg25mrq5ehmb4y6xia2p3k4naiogi44@rcaoz3xnqlcf>
Date: Thu, 14 Nov 2024 09:38:00 -0500
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Shuah Khan <skhan@...uxfoundation.org>
Cc: gregkh@...uxfoundation.org, corbet@....net, workflows@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, rdunlap@...radead.org,
daniel@...ll.ch, laurent.pinchart@...asonboard.com, broonie@...nel.org,
Linus Torvalds <torvalds@...ux-foundation.org>, Miguel Ojeda <ojeda@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>, Steven Rostedt <rostedt@...dmis.org>,
Dan Williams <dan.j.williams@...el.com>, Theodore Ts'o <tytso@....edu>
Subject: Re: [PATCH v3] Documentation/CoC: spell out enforcement for
unacceptable behaviors
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.
-K
Powered by blists - more mailing lists