Linux Code of Conduct Board and CoC Supremacy Over Code/Function
-
It's FOSS ☛ A Problem in the Linux Kernel Yet Again: This Time, It's Bcachefs! [Ed: The Linux Foundation's Linux Kernel Code of Conduct (CoC) Committee is Now Officially Corporate]
Some issues with the developer of bcachefs in the Linux Kernel community. Maybe, it's just being overblown? What do you think?
-
Bryan Lunduke ☛ Linux Code of Conduct Board Blocks File System Changes
A code change for new bcachefs features is being blocked not for technical reasons... but a CoC dispute. Seriously.
Update
An overview:
-
Flamewar Leads to Declining of Bcachefs Pull Requests During Linux 6.13 Kernel Development Cycle
"Get your head examined. And get the fuck out of here with this shit." That's how Bcachefs developer Kent Overstreet ended a post on the Linux kernel mailing list.
This was followed by "insufficient action to restore the community's faith in having otherwise productive technical discussions without the fear of personal attacks," according to an official ruling by committee enforcing the kernel community's code of conduct. After formalizing an updated enforcement process for unacceptable behaviors, it then recommended that during the Linux 6.13 kernel development cycle, Overstreet's participation should be restricted (with his pull requests declined). Phoronix covered their ruling, and ItsFOSS and The Register offer some of the backstory.
Overstreet had already acknowledged that "Things really went off the rails (and I lost my cool, and earned the ire of the CoC committee)" in a 6,200-word blog post on his Patreon page. But he also emphasized that "I'm going to keep writing code no matter what. Things may turn into more of a hassle to actually get the code, but people who want to keep running bcachefs will always be able to (that's the beauty of open source, we can always fork), and I will keep supporting my users..."