All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: "tech-board-discuss@lists.linuxfoundation.org"
	<tech-board-discuss@lists.linuxfoundation.org>
Cc: "conduct@kernel.org" <conduct@kernel.org>
Subject: Re: [Tech-board-discuss] Linux Kernel Code of Conduct Committee: September 30, 2023
Date: Mon, 9 Oct 2023 08:34:49 -0600	[thread overview]
Message-ID: <c3e612f7-ca7e-467b-9758-48c22aa92892@linuxfoundation.org> (raw)
In-Reply-To: <42c40a4b-78d5-4878-9eff-31bcfc221d35@linuxfoundation.org>

Dear TAB members,

On 10/4/23 10:54, Shuah Khan wrote:
> Dear TAB members,
> 
> Please review this Code of Conduct Report for April 1, 2023 through
> September 30, 2023 and give us feedback.
> 
> 

Please give us feedback on this report before the end of this week.

thanks,
-- Shuah (On behalf of the Code of Conduct Committee)

> --------------------------------------------------------------------
> 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."
> 
> We would like to thank the Linux kernel community members who have
> supported the adoption of the Code of Conduct and who continue to
> uphold the professional standards of our community. If you have
> questions about this report, please write to <conduct@kernel.org>.
> 


  reply	other threads:[~2023-10-09 14:34 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 [this message]
2023-10-09 14:49 ` Theodore Ts'o
2023-10-16 14:39 ` Steven Rostedt
2023-10-16 15:03   ` Greg KH

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=c3e612f7-ca7e-467b-9758-48c22aa92892@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=conduct@kernel.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 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.