linux-kernel - Code of Conduct Committee report for April 2024

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025043021-reprogram-gloss-acb5@gregkh>
Date: Wed, 30 Apr 2025 16:36:59 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc: "conduct@...nel.org" <conduct@...nel.org>,
	tech-board <tech-board@...ts.linux-foundation.org>
Subject: Code of Conduct Committee report for April 2024 - March 2025

Linux Kernel Code of Conduct Committee: March 31, 2025

Updates to the Code of Conduct documents:
 - The Code of Conduct documentation has been updated to clearly
   outline the enforcement when Unacceptable Behavior Code
   of Conduct Violations take place, and outline the Technical
   Advisory Board's role in approving remedial actions recommended
   by the Code of Conduct Committee.

Reference:
   https://docs.kernel.org/process/code-of-conduct-interpretation.html#code-of-conduct-interpretation

In the period of April 1, 2024 through March 31, 2025, the Code of
Conduct Committee received the following reports:

Reports received: 17

Development process related reports:
 - 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.

   These reports were about a developer demanding their patch to be
   accepted even after repeated attempts by maintainers advising the
   developers to understand the development process.

Code of Conduct scope and enforcement related reports:
 - Education and coaching on the role and scope of the Code of Conduct.

   Several reports from people outside the kernel community reporting
   past incidents before the Code of Conduct was adopted. Reports
   resolved clarifying the scope and validity of reports about past
   incidents before adopting the Code of Conduct.

Insensitive comments reports:
 - Education and coaching on the role and scope of the Code of Conduct.

   Reports about Office of Foreign Assets Control (OFAC) related actions
   and offhand comments in technical discussions that do not rise to the
   level of violations.

Unacceptable behavior or comments in email: 6
- 4 reports resolved instituting remedial measures on two individuals
  restricting their participation in development process.

  -- Rejecting pull requests from an individual for a full release cycle.
     Reference: 1

  -- Banning an individual for 3 months from Linux kernel mailing lists.
     Reference: 2

- References:
  -- 1. https://lore.kernel.org/all/6740fc3aabec0_5eb129497@dwillia2-xfh.jf.intel.com.notmuch/
  -- 2. https://lore.kernel.org/all/67cf7499597e9_1198729450@dwillia2-xfh.jf.intel.com.notmuch/

- Others
  - Resolved with the individuals making amends for their behaviors.

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@...nel.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

greg k-h
(On behalf of the Code of Conduct Committee)