workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: gregkh@linuxfoundation.org, corbet@lwn.net,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.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>,
	Dave Airlie <airlied@gmail.com>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] Documentation/CoC: spell out enforcement for unacceptable behaviors
Date: Tue, 12 Nov 2024 10:45:22 -0700	[thread overview]
Message-ID: <d9bcf2df-8201-4eea-8e98-d305a4671736@linuxfoundation.org> (raw)
In-Reply-To: <ZzNppQIQm6O6lnfW@finisterre.sirena.org.uk>

On 11/12/24 07:43, Mark Brown wrote:
> On Mon, Nov 11, 2024 at 02:50:45PM -0700, Shuah Khan wrote:
>> On 11/11/24 13:07, Simona Vetter wrote:
> 
>>> Personal take, but I think a forced public apology as the primary or at
>>> least initial coc enforcement approach is one of the worst.
> 
> ...
> 
>> This document isn't intended to be a complete summary of all actions the
>> CoC takes in response to reports. There is a lot of back and forth with
>> the individuals to bring about change before the CoC asks for an apology.
> 
> I guess it would be good to explicitly call out (possibly in an
> incremental change on top of this one) that the specific enforcement
> steps here are examples, and are mainly for cases where a more
> mediation/education based approach fails or extreme cases where they're
> inappropriate?  Neither the existing document nor the current change
> make that explicit (at least to my reading), it's clear from for example
> the reports that are sent that the existing practice is to try to use
> those approaches first but I'm not sure that people would realise that
> from this document alone.

Thank you Mark. I will add more content to the document distilling the
discussion on this thread in the interest of transparency.

thanks,
-- Shuah

      reply	other threads:[~2024-11-12 17:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 16:18 Shuah Khan
2024-11-08 20:08 ` Randy Dunlap
2024-11-09  3:59 ` Theodore Ts'o
2024-11-11 20:07 ` Simona Vetter
2024-11-11 21:50   ` Shuah Khan
2024-11-11 22:35     ` Laurent Pinchart
2024-11-12  0:35       ` Shuah Khan
2024-11-12  5:18         ` Laurent Pinchart
2024-11-12 17:44           ` Shuah Khan
2024-11-12 17:49             ` Laurent Pinchart
2024-11-12 14:43     ` Mark Brown
2024-11-12 17:45       ` 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=d9bcf2df-8201-4eea-8e98-d305a4671736@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=airlied@gmail.com \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.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=torvalds@linux-foundation.org \
    --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