Open Source Maintainership Isn't a Burnout Problem. It's a Contract Problem.

few months, a beloved open source project dies. The maintainer posts a goodbye note. Twitter mourns for 48 hours. Someone forks it. And then we do it again.

The narrative that follows is always the same: burnout. The maintainer was overwhelmed by issue volume, toxic users, feature demands, zero pay. We need to treat maintainers better.

All of that is true. None of it is the actual problem.

The actual problem is that open source has an implicit contract that nobody agreed to explicitly, and that contract is insane.

Here's what the contract says:

You write software. You put it on the internet for free. Anyone can use it. By putting it there, you implicitly agree to maintain it indefinitely, answer questions about it for free, fix bugs caused by other people's misuse of it, keep up with breaking changes in adjacent tooling, and do all of this on your own time at your own cost.

The user, meanwhile, has zero obligations. They can depend on your work in production systems worth hundreds of millions of dollars, file issues demanding features with zero payment or even acknowledgment, and abandon the project the moment a shinier alternative appears — leaving you to handle the resulting "why is this unmaintained?" reputation hit.

This isn't a burnout story. This is a contract you never signed being enforced against you by the weight of everyone else's assumptions.

I've maintained a few smaller projects. Nothing famous. The moment one of them got above ~800 GitHub stars, the tone of incoming issues changed completely. Feature requests started being filed as bugs. "This doesn't do X" — where X was something I'd never claimed it would do, documented as out of scope, and explicitly declined twice before. But the implicit contract says you owe them X, because you've demonstrated willingness to work on it.

The fix isn't "be nicer to maintainers." The fix is renegotiating the contract.

Some projects have started doing this explicitly: `MAINTAINERSHIP.md` files that say exactly what the maintainer commits to and doesn't. Business source licenses that require commercial users to pay after a threshold. README sections that say "issues will be triaged when I have time; PRs are welcome but may sit for months."

These feel rude to people who've been conditioned by the old implicit contract. They're not rude. They're honest.

The other half of the renegotiation has to happen on the user side. If your company depends on an open source package — really depends on it, meaning your service breaks if it goes unmaintained — you have a business risk that you've offloaded onto a stranger. That's not a relationship. That's exploitation with extra steps.

Funding maintainers through GitHub Sponsors, Patreon, Open Collective, or direct commercial agreements isn't charity. It's acknowledging that the value you're extracting from their labor is real and worth something.

The burnout conversation will keep happening every few months because burnout is the visible symptom. The invisible cause is a set of unspoken expectations that nobody questioned because the software was free.

Free software isn't free. You're just deciding who pays for it. Right now, the answer is: whoever cared enough to build it in the first place.