It is not good when politics get in the way of good engineering.

Regardless of differing points of view on the situation, I think everyone can agree that bcachefs being actively updated on Linus tree is a good thing, right?

If you were able to work at your own pace, and someone else took the responsibility of pulling your changes at a pace that satisfies Linus, wouldn't that solve the problem of Linux having a good modern/CoW filesystem?

▲

motorest 4 days ago | parent | next [-]

> Regardless of differing points of view on the situation, I think everyone can agree that bcachefs being actively updated on Linus tree is a good thing, right?

I think bcachefs is not the problem. The problem seems to be the sole maintainer who is notoriously abusive and apparently unable to work with other kernel developers.

I'm sure if another maintainer came along, one that wasn't barred for being abusive towards other maintainers, there would be no problem getting the project back in.

▲

koverstreet 4 days ago | parent | prev [-]

At this time, I don't think so.

We were never able to get any sane and consistent policy on bugfixes, and I don't have high hopes that anyone else will have better luck. The XFS folks have had their own issues with interference, leading to burnout - they're on their third maintainer, and it's really not good for a project to be cycling through maintainers and burning people out, losing consistency of leadership and institutional knowledge.

And I'm still seeing Linus lashing out at people on practically a weekly basis. I could never ask anyone else to have to deal with that.

I think the kernel community has some things they need to figure out before bcachefs can go back in.

	▲	tarruda 3 days ago \| parent \| next [-]
		Keep in mind that bcachefs’s adoption and eventual mainstream acceptance are not contingent on Linus accepting your contributions or on you “removing the experimental label.” What matters is eliminating the barriers that prevent users from trying it, and that is far easier when bcachefs is an upstream filesystem—something that allows more distributions to offer it as an installer option. > And I'm still seeing Linus lashing out at people on practically a weekly basis. I could never ask anyone else to have to deal with that. This is a bit off‑topic, but I wouldn’t be so quick to judge how well Linus is doing his job; no one else in the world has his responsibilities. At this point, any new kernel contributor should be familiar with Linus and have come to accept, or at least tolerate, his ways. > I think the kernel community has some things they need to figure out before bcachefs can go back in. Fair enough. It may be better to let things cool off while giving bcachefs more time to reach a stable state before attempting to reintegrate it into Linux development. I hope you won’t give up, because Linux needs this. Since bcachefs is your project and you seem to enjoy working on it, it wouldn’t be a stretch to say that you need this too, right? Don’t let ego get in the way of achieving your goals.
	▲	thoroughburro 3 days ago \| parent \| prev \| next [-]
		This sort of misrepresentation of your public behavior will only trash your reputation further. I encourage anyone who reads this to actually look up the mailing list threads. It’s very illuminating.
	▲	motorest 3 days ago \| parent \| prev [-]
		> We were never able to get any sane and consistent policy on bugfixes, and I don't have high hopes that anyone else will have better luck. This reads an awful lot like blatant gaslighting. It's quite public that you were kicked out not only because of abusive behavior towards other kernel developers but also you kept ignoring any and all testing and QA guardrails, to the point you tried to push patched that failed to build. From the very public discussion, you should sit down any discussion on bugfixes and testing because, while you are voicing strong opinions on high quality bars, the evidence suggests you were following none.