惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

AI
AI
WordPress大学
WordPress大学
博客园 - 聂微东
Hugging Face - Blog
Hugging Face - Blog
小众软件
小众软件
V
V2EX
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Google DeepMind News
Google DeepMind News
V
Visual Studio Blog
The GitHub Blog
The GitHub Blog
IT之家
IT之家
D
Docker
M
MIT News - Artificial intelligence
D
DataBreaches.Net
博客园 - 三生石上(FineUI控件)
酷 壳 – CoolShell
酷 壳 – CoolShell
量子位
博客园_首页
Y
Y Combinator Blog
F
Full Disclosure
Microsoft Security Blog
Microsoft Security Blog
月光博客
月光博客
C
CXSECURITY Database RSS Feed - CXSecurity.com
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Spread Privacy
Spread Privacy
Know Your Adversary
Know Your Adversary
A
Arctic Wolf
Vercel News
Vercel News
T
Threat Research - Cisco Blogs
T
Threatpost
Apple Machine Learning Research
Apple Machine Learning Research
L
LINUX DO - 热门话题
T
The Exploit Database - CXSecurity.com
N
Netflix TechBlog - Medium
GbyAI
GbyAI
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
T
Tailwind CSS Blog
J
Java Code Geeks
爱范儿
爱范儿
Cisco Talos Blog
Cisco Talos Blog
博客园 - 叶小钗
Latest news
Latest news
C
Check Point Blog
阮一峰的网络日志
阮一峰的网络日志
博客园 - Franky
P
Privacy International News Feed
MyScale Blog
MyScale Blog
Project Zero
Project Zero
Simon Willison's Weblog
Simon Willison's Weblog

The Linux Kernel Archives

Active kernel releases The Linux Kernel Organization About Linux Kernel Contacts Frequently asked questions Linux.dev mailing list service Git mirror available in Beijing Get notifications for your patches List archives on lore.kernel.org Minor changes to kernel tarball releases Best way to do linux clones for your CI Nitrokey digital tokens for kernel developers Linux kernel releases PGP signatures RC tarballs and patches starting with 4.12-rc1 If you got "BAD Signature" this morning Fast new frontends with Packet Shutting down FTP services Gandi.net TLS certificates Cloning Linux from a bundle Introducing Fastly CDN Hurr, Durr Im'a Sheep FTP limited on mirrors.kernel.org Heartbleed statement Happy new year and good-bye bzip2 New frontend and googlesource.com Mirroring kernel.org repositories Fifty shades of Tux XZ by default and JSON /pub tree resync-ing Cleanroom styles Pelican Legal disclaimers and copyright
Code of Conduct
2020-01-02 · via The Linux Kernel Archives

The Linux kernel community operates a Code of Conduct based on the Contributor Covenant Code of Conduct with a Linux Kernel Contributor Covenant Code of Conduct Interpretation.

Committee Reports

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 any questions about these reports, please write to <conduct@kernel.org>.

March 2026

Archival copy: https://lore.kernel.org/lkml/f833fdfe-12f1-413f-966a-4c3ce9ad626e@kernel.org/T/#u

In the period of October 1, 2025 through March 31st, 2026, the Code of Conduct Committee received the following reports:

Reports received: 3

Code of Conduct scope and enforcement related reports: 3

  • 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 about insensitive comments made in a setting outside the scope and purview of the Code of Conduct.

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

September 2025

Archival copy: https://lore.kernel.org/all/dfa4d9f3-8b56-46fc-9d1b-68e07a3d6edc@kernel.org/

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

March 2025

Archival copy: https://lore.kernel.org/all/2025043021-reprogram-gloss-acb5@gregkh/

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

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

March 2024

Archival copy: https://lore.kernel.org/r/355aee5f-13ce-4e20-9ce8-e5bcddd14bc2@linuxfoundation.org

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

  • Unprofessional behavior or comments in email: 2

The result of the investigation:

  • Education and coaching clarifying the role of Code of Conduct conduct on conversations that don't go against the CoC.
  • Education and coaching the individuals on the impact of making unprofessional comments which could be misunderstood leading to negative impressions about the community.

The reports were about the offhand comments made while rejecting the code which are not violations of the Code of Conduct

Unacceptable behavior or comments on a private invitee only chat channel: 1

  • Education and coaching clarifying the role of Code of Conduct conduct on conversations that occur on a private chat channel.

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

September 2023

Archival copy: https://lore.kernel.org/r/3351be6b-854e-479d-832c-83cb8829c010@linuxfoundation.org

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

  • Unacceptable behavior or comments in email: 4

The result of the investigation:

  • Education and coaching clarifying the Code of Conduct conduct related to normal review and patch acceptance process: 3
  • Clarification on the Code of Conduct conduct related to maintainer rights and responsibility to reject code: 1

The reports were about the discussion during the patch review and decisions made in rejecting code and these actions are not viewed as violations of the Code of Conduct.

Please see the excerpt from the Responsibilities section in the Linux Kernel Contributor Covenant Code of Conduct Interpretation document:

setting expertise expectations, making decisions and rejecting unsuitable
contributions are not viewed as a violation of the Code of Conduct.

March 2023

Archival copy: https://lore.kernel.org/r/557ef895-ad2d-eff9-7cb8-70dbcf41adea@linuxfoundation.org

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

The reports were about the decisions made in rejecting code and these actions are not viewed as violations of the Code of Conduct.

Please see the excerpt from the Responsibilities section in the Linux Kernel Contributor Covenant Code of Conduct Interpretation document:

setting expertise expectations, making decisions and rejecting unsuitable
contributions are not viewed as a violation of the Code of Conduct.

September 2022

Archival copy: https://lore.kernel.org/r/57a492fb-928b-9e0a-5f0e-dc95ef599309@linuxfoundation.org

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

  • Unacceptable behavior or comments in email: 1

The result of the investigation:

  • Resolved with a public apology from the violator with a commitment from them to abide by the Code of Conduct in the future.

March 2022

Archival copy: https://lore.kernel.org/r/4401af50-083d-0239-6b7f-3454c8d69fec@linuxfoundation.org

In the period of October 1, 2021 through March 31, 2022, the Code of Conduct Committee received the following reports:

  • Unacceptable behavior or comments in email: 2

The result of the investigation:

  • Education and coaching clarifying the Code of Conduct conduct related to normal review process: 2

April 2021

Archival copy: https://lore.kernel.org/r/448b06e4-41fc-26df-a862-c3ba2f70b6b3@linuxfoundation.org

In the period of November 1, 2020 through April 30, 2021 the Code of Conduct Committee received the following reports:

  • Unacceptable behavior or comments in email (3rd party): 4

The result of the investigation:

  • Education and coaching: 1
  • Public response to call attention to the behavior and request correction with consequence of ban if behavior persists: 1
  • Public response to attention to the behavior and request correction: 1
  • Clarification on the Code of Conduct conduct related to maintainer rights and responsibility to reject code: 1

October 2020

Archival copy: https://lore.kernel.org/lkml/20201105083002.GA3429143@kroah.com/

In the period of January 1, 2020 through October 31, 2020 the Committee received the following reports:

  • Unacceptable behavior or comments in email: 1
  • Unacceptable comments in github repo by non-community members: 1
  • Unacceptable comments toward a company: 1

The result of the investigation:

  • Education and coaching: 1
  • Locking of github repo for any comments: 1
  • Clarification that the Code of Conduct covers conduct related to individual developers only: 1

September 2018 to July 2019

Archival copy: https://lore.kernel.org/lkml/20190810120700.GA7360@kroah.com/

In the period of September 15, 2018 through July 31, 2019, the Committee received the following reports:

  • Inappropriate language in the kernel source: 1
  • Insulting behavior in email: 3

The result of the investigations:

  • Education and coaching: 4