> Once the BCacheFS maintainer behaves [...]
So, there are still behavioral issues here I take it? That is a bummer. This is not news to me, but I thought the situation has changed ever since.
So, there are still behavioral issues here I take it? That is a bummer. This is not news to me, but I thought the situation has changed ever since.
From the past discussion, it's mainly grave behavioral issues but they also end up being technical. Such as trying to push new untested features into RCs and breaking builds, and resorting to flame wars to push these problematic patches forward instead of actually working them out with maintainers.
But yeah, the final straw was a very abusive email sent to a maintainer in the mailing list.
Seriously, every time I read tales about all the horrific things I've done in the kernel community, the stories grow and get wilder and wilder.
Oh wait.
It's you.
So even if you were right all along, the outcome is that people are screwed because bcachefs is no longer maintained in the kernel.
Every day, I ask myself, do I want to be right, or do I want to be effective?
That's how you end up with decisionmaking that's nothing more than popularity contests and no one even bothering to do the analysis on which option is technically better.
That way leads the death of leadership.
If you want to accomplish something as challenging as a filesystem, you do it by consistently making the right call and sticking to it, over and over and over.
And if you keep doing that, eventually you end up with the most active filesystem community around, and the ability to flip even the kernel community the bird when their weaponized incompetence becomes too much :)