From: Greg KH <greg@kroah.com>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: conduct@kernel.org, tech-board-discuss@lists.linuxfoundation.org
Subject: Re: [Tech-board-discuss] v2 Linux Kernel Code of Conduct Committee: March 31, 2023
Date: Thu, 13 Apr 2023 09:31:11 +0200 [thread overview]
Message-ID: <2023041336-crabgrass-jawed-9eb1@gregkh> (raw)
In-Reply-To: <e84802a0-8ce6-77d2-44e9-8959ca07b4e9@linuxfoundation.org>
On Wed, Apr 12, 2023 at 01:54:59PM -0600, Shuah Khan wrote:
> Dear TAB members,
>
> Please review the revised Code of Conduct Report for October 1, 2022
> through March 31, 2023 and give us feedback.
>
> --------------------------------------------------------------------
> Linux Kernel Code of Conduct Committee: March 31, 2023
>
> In the period of October 1, 2022 through March 31, 2023, the Code of
> Conduct Committee received the following reports:
>
> Unacceptable behavior or comments in email: 6
>
> The result of the investigation:
> - Education and coaching clarifying the Code of Conduct conduct
> related to normal review and patch acceptance process: 1
> - Clarification on the Code of Conduct conduct related to
> maintainer rights and responsibility to reject code: 5
>
> The reports were about the decisions made in rejecting code and these
> actions are not viewed as a violation 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>.
> --------------------------------------------------------------------
I've updated the public site with this new report:
https://kernel.org/code-of-conduct.html
and also added a link to our interpretation document there, as it wasn't
listed before.
thanks,
greg k-h
prev parent reply other threads:[~2023-04-13 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 19:54 [Tech-board-discuss] v2 Linux Kernel Code of Conduct Committee: March 31, 2023 Shuah Khan
2023-04-12 20:03 ` Jonathan Corbet
2023-04-12 20:43 ` Dan Williams
2023-04-13 2:29 ` Theodore Ts'o
2023-04-13 7:31 ` 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=2023041336-crabgrass-jawed-9eb1@gregkh \
--to=greg@kroah.com \
--cc=conduct@kernel.org \
--cc=skhan@linuxfoundation.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