Technical Advisory Board (TAB) public discussions
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "conduct@kernel.org" <conduct@kernel.org>,
	"tech-board-discuss@lists.linuxfoundation.org"
	<tech-board-discuss@lists.linuxfoundation.org>
Subject: Re: [Tech-board-discuss] Linux Kernel Code of Conduct Committee: September 30, 2023
Date: Mon, 16 Oct 2023 17:03:10 +0200	[thread overview]
Message-ID: <2023101626-equal-blazer-6b4b@gregkh> (raw)
In-Reply-To: <20231016103933.16f53df9@gandalf.local.home>

On Mon, Oct 16, 2023 at 10:39:33AM -0400, Steven Rostedt wrote:
> On Wed, 4 Oct 2023 10:54:16 -0600
> Shuah Khan <skhan@linuxfoundation.org> wrote:
> 
> > Dear TAB members,
> > 
> > Please review this Code of Conduct Report for April 1, 2023 through
> > September 30, 2023 and give us feedback.
> > 
> 
> Sorry for the late reply, just been way behind in work lately.
> 
> > 
> > --------------------------------------------------------------------
> > Linux Kernel Code of Conduct Committee: September 30, 2023
> > 
> > In the period of April 1, 2023 through September 30, 2023, the Code of
> > Conduct Committee received the following reports:
> > 
> > Unacceptable behavior or comments in email: 4
> > 
> > The result of the investigation:
> >   - Education and coaching clarifying the Code of Conduct conduct
> >     related to normal review and patch acceptance process: 3
> >   - Clarification on the Code of Conduct conduct related to
> >     maintainer rights and responsibility to reject code: 1
> > 
> > The reports were about the discussion during the patch review and
> > decisions made in rejecting code and these actions are not viewed
> > as violations of the Code of Conduct.
> > 
> > Please see the excerpt from the Responsibilities section in the
> > code-of-conduct-interpretation.rst document:
> > 
> > "setting expertise expectations, making decisions and rejecting unsuitable
> > contributions are not viewed as a violation of the Code of Conduct."
> 
> Sounds to me that people are trying to use the CoC as a way to get code
> accepted?

Yes, people are trying to use the CoC as a way to push back on patch
rejections, it's not anything new, unfortunately :(

> Well, there's only 4 reports in a month. I hope that's not too
> much of a hassle.

4 reports in 6 months, it's not much of a hassle so far.

thanks,

greg k-h

      reply	other threads:[~2023-10-16 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 16:54 [Tech-board-discuss] Linux Kernel Code of Conduct Committee: September 30, 2023 Shuah Khan
2023-10-09 14:34 ` Shuah Khan
2023-10-09 14:49 ` Theodore Ts'o
2023-10-16 14:39 ` Steven Rostedt
2023-10-16 15:03   ` Greg KH [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=2023101626-equal-blazer-6b4b@gregkh \
    --to=greg@kroah.com \
    --cc=conduct@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tech-board-discuss@lists.linuxfoundation.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