I’ve said this previously, and I’ll say it again: we’re severely under-resourced. Not just XFS, the whole fsdevel community. As a developer and later a maintainer, I’ve learnt the hard way that there is a very large amount of non-coding work is necessary to build a good filesystem. There’s enough not-really-coding work for several people. Instead, we lean hard on maintainers to do all that work. That might’ve worked acceptably for the first 20 years, but it doesn’t now.
[…]
Dave and I are both burned out. I’m not sure Dave ever got past the 2017 burnout that lead to his resignation. Remarkably, he’s still around. Is this (extended burnout) where I want to be in 2024? 2030? Hell no.
What kind of non-coding work do you need done?
Based on the post:
It doesn’t sound like they want non-technical contributions but they don’t need more patches necessarily. Just my interpretation, probably contact the mailinglist if filesystems truly interest someone.
Great summary!
I think the mailing lists need to come to Lemmy for discussion if they’re not getting the involvement they need.
As an older developer, when I want younger perspectives, I figure out where they spend their time, and go there.
the email lists:
I don’t think non-coding work means non-technical work - you’ll likely still need to dig deep into the technical details to actually be able to help
There is also a link to docs: add maintainer entry profile for XFS