mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 2026 - September 2026
Date: Wed, 21 Oct 2026 14:22:14 -0600	[thread overview]
Message-ID: <d7086f73-9398-448a-834c-69e2ffca8563@kernel.org> (raw)

Linux Kernel Code of Conduct Committee: September 30th, 2026

In the period of April 1st, 2026 through September 30th, 2026, the Code
of Conduct Committee received the following reports:

Reports received: 3

Code of Conduct scope and enforcement related reports: 3

    -- Publicly coached and educated an individual who wasn't part of
       the kernel community about the CoC, advising them to follow
       the code of conduct when they interact with the community. The
       issue was resolved without considering other enforcement options.

    -- A public report to the CoC about technical discussion was resolved
       on the mailing list without any response or action by the CoC.

    -- A dispute about copying code had been resolved by the maintainer
       asking the developers to resolve the issue between them before their
       patches get reviewed and accepted.

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:[~2026-10-21 20:22 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=d7086f73-9398-448a-834c-69e2ffca8563@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®