On Fri, Jun 20, 2025 at 07:35:04PM -0400, Kent Overstreet wrote: > So it's hard to fathom what's going on here. I also need to add that this kind of drama, and these responses to pull requests - second guessing technical decisions, outright trash talk - have done an incredible amount of damage, and I think it's time to make you guys aware of that since it's directly relevant to the story of this pull request. I've put a lot of work into building a real community around bcachefs, because that's critical to making it the rock solid, dependable filesystem, for eeryone, that I intend it to be: building a community where people feel free to share observations, bug reports, and where people trust that those will be acted on responsibly. That all gets set back whenever drama like this happens. Last time, the casefolding bugfix pull request, ignited a whole vi. vs. emacs holy war. Every time this happens, the calm, thoughtful people pull back, and all I hear from are the angry, dramatic voices. More than that, I lost a hire because of Linus's constant, every-other-pull-request "I'm thinking about removing bcachefs from the kernel". It turns out, smart, thoughtful engineers with stable jobs become very hesitant about leaving those jobs when that happens, and that's all their co-workers are seeing. And the first thing that got cancelled/put aside because of that - work that was in progress, and hasn't been completed - was tooling for comprehensive programatic fault injection for on disk format errors. IOW - the tooling and test coverage that would have caught the subvolume deletion bug. That's a really painful loss right now. Even despite that, bcachefs development has been going incredibly smoothly, and it's shaping up fast. Like I mentioned before, 100+ TB filesystems are commonplace, users are commenting every release on how much smoother is getting. We are, I hope, only a year or less from being able to take the experimental label off, based on the decline in critical bug reports I'm seeing. The only area that gives me cause for concern - and it causes a _lot_ of concern - is upstream.
