Linux file system developer: we're severely under-resourced - eviltoast

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.

  • liori@lemm.eeOP
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    1 year ago

    Kernel is not a monolithic application, and you cannot develop it like one. There are tons of actors: independent developers, small support companies (like Collabora), corporations, all with different priorities. There is a large number of independent forks (e.g. for obscure devices), that will never be merged, but need to merge e.g. security patches from the mainline. A single project management tool won’t do, not your typical business grade tracking&reporting tool.

    CI is already there. Not a central one—again, distributed across different organizations. Different organizations have different needs for CI, e.g. supporting weird architectures that they need to develop against.

    There is a reason Torvalds created git—existing tools just wouldn’t work. There might be a place for a similar revolution regarding a bugtracker…