Linus apparently will not pull any #Bcachefs changes into #Linux 6.13 due to "an open issue with the CoC (Code Of Conduct) board".
Kent shared that in a 36k long patreon post starting with "the future of bcachefs in the #kernel is uncertain, and lots of things aren't looking good.":
https://www.patreon.com/posts/116412665
Side note: this happened just hours after the rules for "Enforcement for Unacceptable Behavior Code of Conduct Violations" were merged to 6.13 :
https://git.kernel.org/torvalds/c/c818d5c64c9a8cc14853d716bf7ce6674a6126d0
2/ For completeness, as it's easy to miss in Kent's long post:
Kent refuses to send a public apology for a remark to a mm developer that lead to the escalation to the COC. Search for "you should probably send him an apology" in his Patreon post to find a good place to start.
Also note that Kent resurrected the #LKML thread with the remark yesterday; new messages start here: https://lore.kernel.org/all/vvulqfvftctokjzy3ookgmx2ja73uuekvby3xcc2quvptudw7e@7qj4gyaw2zfo/t/#u
3/ There is now a official msg from the #Linux Foundation Technical Advisory Board (TAB) to #Bcachefs developer Kent Overstreet based on a recommendation from the Code of Conduct Committee :
https://lore.kernel.org/all/6740fc3aabec0_5eb129497@dwillia2-xfh.jf.intel.com.notmuch/
'"[…] written abuse of another community member required action on your part to repair the damage to the individual and the community. You took insufficient action[…]
- Restrict participation in the kernel development process during the Linux 6.13 kernel […]"'
@kernellogger this drama is depressing... I don't know how you manage to follow these discussions, but thank you for doing that for the community here!
Depressing: definitely.
Following it: guess I got used to it, as it was my job for many years
Thx: yw!
@kernellogger nice to see the COC enforced. As a long time reader of LKML, the tone isnt the worst i have heard. The difference is, however, that the "pre COC heated discussions" were quick to tone down once someone pointed out that its starting to get personal/unproductive.
That does not seem to happen with Kent. And other devs who try to keep their discussions clean are starting to ignore him - which i can fully understand.
@kernellogger what the hell is it with people who insist on acting like this?
You have a sweet piece of tech, but you want to not treat other people appropriately to such a degree well no one will want to use that tech.
@rasmus91 I guess you have to ask a psychologist for a proper answer.
My view is simply: there are sadly a lot of people in this world that are not that kind to others as it IMHO would be appropriate, so up to some point they naturally will end up in various bubbles of life – including Linux kernel development.
@kernellogger @rasmus91 There are also a lot of walks of life where shitty behavior is overlooked and ignored, and nobody tells you to stop. Largely this has been the case for kernel development too. Maybe things will improve from here, but this wasn't really a great example of how to handle it.
@rasmus91 @kernellogger Look into the comments under this article:
https://www.phoronix.com/news/Linux-CoC-Bcachefs-6.13
Plenty of comments who think this behavior is just fine ...
@ascherbaum @kernellogger In particular I enjoy this sort of comment:
> This looks no more than what Linus has written for years
Yes, and it was decided that even Linus, or shall we say, even for ANYONE that sort of behaviour is unacceptable, and thus, Linus went on a sabbatical to do a course to change that behaviour. And if you occassionally read the lkml it sure seems like he did the work and reaped the benefits.
@rasmus91 @kernellogger Someone called this out, yes. And it is the right thing to do.
@kernellogger by “declining PRs” they mean “emails”‘right ? Anyway, tough sentence not being allowed to submit code in December