Morten Linderud didn’t write a dramatic resignation letter. He didn’t call out the ungrateful billions who use his work. He simply posted a quiet message to the Arch Linux mailing list: “I am resigning from the Arch Linux development team.”
And then he left.
No fireworks. No manifesto. Just the hollow sound of a door closing on the digital infrastructure millions of us depend on every single day.
You probably didn’t notice. Why would you? The tools he helped build—Arch Linux, the packages, the security patches—they still work. For now. But that’s exactly the problem. We treat open source maintainers like utility workers—invisible until the lights go out. And when a key maintainer walks away, we don’t panic. We don’t even ask who’s next.
Let’s stop pretending this is an isolated incident. Morten is not the first. He won’t be the last. The real story isn’t one person resigning—it’s that the entire open source model depends on a fragile coalition of volunteers who are quietly burning out, and nobody seems to care until a critical piece of the scaffolding collapses.
Think about it. Arch Linux is not some niche hobby project. It powers countless servers, embedded systems, and developer machines. It’s the foundation for distributions like Manjaro and SteamOS. Millions of people touch this code. And yet, the number of people who actually maintain it? A handful. A small, overworked, underappreciated handful.
That’s the open source lie we’ve all bought into: that goodwill is infinite, that passion pays the bills, that someone will always step up. But goodwill has a shelf life. Passion has a burnout rate. The real crisis isn’t that one maintainer resigned—it’s that the entire model assumes infinite goodwill from a finite, burning-out pool of people.
You’ve probably been on the receiving end of this. You’ve used a library that stopped being maintained. You’ve seen a critical bug sit unfixed for months because the sole maintainer had a kid, a job, a life. And you’ve thought, “Someone should do something.” But that someone is never you, right? Because you’re busy. Because you’re not paid to maintain that code. Because the system rewards new features, not maintenance.
That’s the free-rider problem in its purest form. We all consume the fruits of open source, but we treat contribution as optional charity. The result? A handful of martyrs keeping the lights on while the rest of us scroll past.
I’m not saying we should all quit our jobs and become maintainers. I’m saying we need to stop pretending this is sustainable. The moment a critical project loses its key maintainer—and there’s no succession plan, no funding, no recognition—the whole house of cards wobbles. Heartbleed was a warning. Log4j was a siren. This Arch Linux resignation is another tremor.
So what do we do? First, stop thanking maintainers and start paying them. Not with T-shirts. Not with “thoughts and prayers.” With money, time, and institutional support. If your company uses open source, you have a responsibility to contribute back—not just code, but the boring, unsexy work of maintenance, bug triage, and documentation.
Second, stop treating maintainers as interchangeable cogs. They are not. They are people with their own limits, their own priorities, their own right to walk away. Every time a maintainer resigns, it’s a signal that the system is broken. And we ignore those signals at our own risk.
Morten Linderud didn’t burn the bridge. He just walked away. But the bridge is still there, held together by a few more volunteers. The question is: How long before the next one leaves, and the bridge collapses?
We don’t have to wait for the lights to go out. We can fix this. But only if we stop believing the lie that open source runs on magic and goodwill. It runs on people. And people, like Morten, eventually walk away.
FAQ
Q: Isn't this just one person leaving? Happens all the time.
A: Yes, but the pattern is systemic. When a key maintainer of a critical project like Arch Linux leaves, the fragility of the entire volunteer model is exposed. One resignation is a canary, not an anomaly.
Q: What should I do if I rely on open source software?
A: Start by contributing—financially if possible, or with code, documentation, testing. Advocate for your employer to fund maintainers. Reduce your dependency on single-maintainer projects. And stop treating open source as free lunch.
Q: Isn't open source fine? It's been working for decades.
A: It worked when projects were smaller and the internet was less critical. Now the stakes are higher, the maintenance burden is larger, and the pool of volunteers hasn't grown proportionally. The model is showing cracks. Ignoring them is not a strategy.