The future of Bcachefs faces uncertainty due to a conflict with the Linux kernel community's Code of Conduct Committee (CoC). The problem arose because Linus Torvalds rejected the inclusion of new fixes for Bcachefs in the upcoming kernel version 6.13 in response to complaints filed by the CoC.
Recently , the CoC rules were updated to allow for stricter disciplinary measures . These include the possibility of blocking a developer who fails to resolve conflicts according to the committee's guidelines or who refuses to issue a public apology for inappropriate behavior.
Sanctions may include temporary suspension of patch and pull request acceptance, as well as exclusion from mailing lists and services related to kernel.org. The maximum duration of this ban is two months, coinciding with the development cycle of a new kernel branch, and its lifting may be conditional upon a public apology.
The new rules were applied to Overstreet after an incident in which he directed an offensive remark ("Get your head checked. And get the hell out of here with this shit") at Michal Hocko , a memory management system developer. Although Overstreet maintains that the conflict with Hocko was resolved privately, the CoC demanded a public apology, which he refused, deeming it inappropriate to address personal matters in this manner. Furthermore, Overstreet criticized the negotiations, which he felt focused more on protecting the project's corporate image than on resolving the conflict fairly.
The decision to block Overstreet was supported by prominent members of the kernel community, including Linus Torvalds, Greg Kroah-Hartman, and other key developers such as Miguel Ojeda and Theodore Tso.
The situation jeopardizes the progress of Bcachefs, which had gained attention as a promising file system solution, and raises questions about how to balance the governance of community projects with freedom of expression and the management of internal conflicts.
Kent Overstreet shared his thoughts on the conflict with the CoC and its implications for the Linux kernel community. According to Overstreet, intense disputes are inherent to the nature of engineering work, where passionate developers often have differing viewpoints. While these discussions can become heated, he maintains that they are an essential part of the creative and collaborative process that drives technical advancement. In his opinion, the CoC's efforts to impose a refined tone of communication violate the established engineering culture, which values ​​openness and a focus on problem-solving over social formalities.
Overstreet warns that suppressing heated debates could lead to a culture of indifference and exclusivity, where only a small elite group feels comfortable participating. This, he argues, could transform kernel development into a less inclusive environment, moving away from the collaborative dynamic that characterizes the community. He believes engineers must confront complex problems directly, even if it means engaging in tense discussions. According to Kent, these disputes, however intense, can lead to effective solutions when a neutral third party evaluates the arguments and makes an informed decision.
It's worth noting that the conflict between Overstreet and Michal Hocko wasn't recent, originating a year ago in a technical disagreement. Overstreet proposed a lightweight mechanism for profiling memory allocation operations, which required adding macros to the allocation functions. However, Hocko rejected the proposal due to concerns about the potential performance impact. According to Overstreet, he attempted to argue technically in favor of his solution, but perceived that he received only formal responses and a lack of willingness to delve deeper into the issue.
Therefore, in response to the most recent conflict, the CoC announced a temporary suspension of Overstreet's participation. During the release cycle for version 6.13, his pull requests will not be accepted. Despite this measure, Overstreet published a letter he sent to Hocko in September, just two days after the offensive message. In it, he offered a personal apology and explained the reasons behind his behavior, seeking a private resolution.
Finally, if you are interested in learning more, you can find the details at the following link.