From: Shuah Khan <skhan@linuxfoundation.org>
To: tech-board-discuss@lists.linuxfoundation.org
Cc: "conduct@kernel.org" <conduct@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: v2 Linux Kernel Code of Conduct Committee: September 30, 2024
Date: Mon, 14 Oct 2024 17:21:42 -0600 [thread overview]
Message-ID: <0e7716d1-8e85-4416-8cc4-c91f7c4e0def@linuxfoundation.org> (raw)
Dear TAB members,
Please review this Code of Conduct Report for April 1, 2024 through
September 30, 2024 and give us feedback.
v2 reflects the current status of "report 2".
thanks,
-- Shuah (On behalf of the Code of Conduct Committee)
--------------------------------------------------------------------
Linux Kernel Code of Conduct Committee: September 30, 2024
In the period of April 1, 2024 through September 30, 2024, the Code of
Conduct Committee received the following reports:
Unacceptable behavior or comments in email: 2
The result of the investigation of report 1:
- Education and coaching on maintainers' right to accept or reject
patches. Clarifying the expectations that developers can't demand
their patches to be reviewed and/or accepted by the community.
The report was about a developer demanding their patch to be accepted
even after repeated attempts by maintainers advising the developer
to understand the development process.
The result of the investigation report 2:
- Resolved with a public response to the violator on the behavior and
following up with conversation.
Education and coaching in email and conversation about how the behavior
and language used won't promote respectful and productive discussions
and that it is detrimental to the health of the community.
- We are continuing to monitor the situation.
Unacceptable behavior or comments on a private invitee only chat
channel: 2
- Education and coaching clarifying the role of Code of Conduct
conduct on conversations that occur on a private chat channel.
- Following up with conversation with the violator to correct the
behavior.
- We are continuing to monitor the situation.
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>.
Please visit the following Code of Conduct link below for information
about the Code of Conduct Committee and previous reports:
- https://www.kernel.org/code-of-conduct.html
--------------------------------------------------------------------
reply other threads:[~2024-10-14 23:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0e7716d1-8e85-4416-8cc4-c91f7c4e0def@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).