You fork a repo, spend twenty minutes hacking together a feature you need, hit ‘submit pull request,’ and close your laptop feeling like a hero. You just contributed to open source! You saved the internet! But the reality is, you just added a line item to a stranger’s sanity bill.
Open source isn’t free. It’s paid for with someone else’s sanity.
We are taught that open source is a beautiful, egalitarian utopia where the more open the gates are to contributions, the better the software becomes. That’s a lie. Wide-open gates are a fast track to maintainer burnout. The tension between openness (accepting all contributions) and quality (enforcing strict standards) is a constant, crushing pressure. If left unresolved, it either strangles the project in red tape or drowns it in endless churn.
Here is the twist nobody tells you: being a good open source maintainer has almost nothing to do with writing excellent code. It is about designing a social system that scales trust. You are no longer just an architect; you are a community steward. If you spend your days merging half-baked pull requests from people who didn’t read the docs, you aren’t leading a project—you’re running a digital orphanage.
Your code quality doesn’t matter if it pushes the maintainer to the point of exhaustion.
This is why the most important skill a maintainer can develop is ruthless boundary-setting. The most pro-social, ecosystem-saving thing a maintainer can do is refuse to be an on-call support bot. Close your GitHub issues without guilt. Lock your DMs. Reject the pull requests that don’t meet the standard. The community will complain, but the project will survive.
Every pull request you send without reading the contributing guide is a small tax on a maintainer’s sanity. Every time you complain on Reddit that ‘this library hasn’t been updated in two years,’ you are demanding that someone work for free, on demand, to serve you. If you depend on open source software—and you do—its sustainability hinges on maintainers who survive their own goodwill.
Refusing to be an on-call support bot is the most pro-social thing a maintainer can do for the ecosystem.
If you want to help, stop treating open source maintainers like public utilities. The survival of the open web depends on maintainers being selfish enough to protect their own boundaries. So the next time you want to submit a PR to a project you barely understand, ask yourself: am I actually solving a problem, or am I just creating a piece of work that someone else has to manage?
FAQ
Q: Shouldn't maintainers be willing to help people who want to contribute?
A: No. Their job is to keep the project alive, not to mentor strangers. If helping a contributor takes three hours that could have been spent fixing a critical bug, that 'help' is a net loss for the entire community.
Q: How do I contribute without being a burden?
A: Read the contribution guidelines, write tests, and make sure your code actually solves a documented issue. If you can't do those three things, don't submit a pull request.
Q: Are more contributors actually bad for open source?
A: Yes, up to a point. A flood of high-churn contributors creates bureaucratic friction faster than it improves the codebase. A fortress of three trusted committers is vastly superior to a swarm of a hundred random pull requests.