From: Shuah <shuah@kernel.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "conduct@kernel.org" <conduct@kernel.org>,
tech-board <tech-board@lists.linux-foundation.org>,
shuah <shuah@kernel.org>
Subject: Code of Conduct Committee report for April 2025 - September 2025
Date: Tue, 28 Oct 2025 13:36:33 -0600 [thread overview]
Message-ID: <dfa4d9f3-8b56-46fc-9d1b-68e07a3d6edc@kernel.org> (raw)
Linux Kernel Code of Conduct Committee: September 30, 2025
In the period of April 1, 2025 through September 30, 2025, the Code of
Conduct Committee received the following reports:
Reports received: 3
Code of Conduct scope and enforcement related reports: 2
- Education and coaching on the role and scope of the Code of Conduct.
-- Report about insensitive comments about projects and code that
don't fall under the scope of the Code of Conduct.
-- Report with questions about DCO which doesn't fall under the scope
of the Code of Conduct.
Actions:
- Ban on a developer was lifted after it expired.
Unacceptable behavior or comments in email: 1
- Resolved with the individual making amends for their behavior.
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
thanks,
-- Shuah
((On behalf of the Code of Conduct Committee)
reply other threads:[~2025-10-28 19:36 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=dfa4d9f3-8b56-46fc-9d1b-68e07a3d6edc@kernel.org \
--to=shuah@kernel.org \
--cc=conduct@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tech-board@lists.linux-foundation.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
all inboxes | Powered by JetHome®