From: Shuah Khan <skhan@linuxfoundation.org>
To: tech-board-discuss@lists.linuxfoundation.org
Cc: conduct@kernel.org
Subject: [Tech-board-discuss] Linux Kernel Code of Conduct Committee: March 31, 2023
Date: Fri, 7 Apr 2023 10:30:37 -0600 [thread overview]
Message-ID: <3ebcf8f1-b5aa-f46e-8db0-e9be3c46c264@linuxfoundation.org> (raw)
Dear TAB members,
Please review this 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
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>.
--------------------------------------------------------------------
thanks,
-- Shuah (On behalf of the Code of Conduct Committee)
next reply other threads:[~2023-04-07 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 16:30 Shuah Khan [this message]
2023-04-12 14:15 ` [Tech-board-discuss] Linux Kernel Code of Conduct Committee: March 31, 2023 Shuah Khan
2023-04-12 14:36 ` Jonathan Corbet
2023-04-12 14:54 ` Shuah Khan
2023-04-12 15:49 ` Steven Rostedt
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=3ebcf8f1-b5aa-f46e-8db0-e9be3c46c264@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).