Maintainers Are the Missing Headline in the Open Source Funding Story
Archi4 min read
Contents
The Headline Nobody Writes#
When a foundation announces a new grant program or a company pledges support for open source, the story usually centers on money. What gets left out is the person who triages the issue queue on a Saturday. I spoke with a maintainer who has shepherded a widely used library for eight years. They asked that their project not be named, because the last time it appeared in a funding story, the issue tracker filled with requests they could not meet. The conversation has been edited for length and clarity.
The Funding Gap#
You have watched several funding cycles come and go. What do the announcements miss?
The announcements miss the maintenance work that does not map to a feature. A grant often funds a new module or a security audit. It rarely funds the person who reads 60 issues a week and closes 40 of them with a one-line explanation. That work is invisible in a press release, and it is the work that keeps the project alive.
Is the money reaching the wrong places?
Not wrong, exactly. It is reaching the places that are easy to describe. A company will sponsor a conference booth before it sponsors a maintainer's Tuesday afternoon. The Tuesday afternoon is where the actual risk sits. When a project fails, it usually fails because nobody was doing the boring part, not because the code was bad.
Who Answers the Issues#
What does a normal week look like for you?
About 15 hours on the library, on top of a full-time job. Roughly half of that is issue triage. A quarter is review. The rest is releases and the occasional patch. I have not written a new feature in 14 months. The last feature I shipped took three weekends, and two of those weekends were spent arguing about the API in a thread with 80 comments.
Do funders understand that split?
Most do not ask. They ask about roadmap and adoption. Adoption is a number they can put in a slide. Triage hours are not. I have started telling people that if you want to fund this project, fund the issue queue. That is the honest answer, and it makes some conversations awkward.
The Hidden Cost of Visibility#
What changed after your project was mentioned in a major funding story?
Inbound requests tripled for about six weeks. Most were polite. Some assumed the money had already arrived and that I was now a full-time employee of the project. I am not. The story did not say that, but the framing implied it. I spent those six weeks explaining the difference between a pledge and a bank transfer.
Did the funding materialize?
Part of it did, through a fiscal sponsor. The process took five months and required paperwork I had never done before. I am grateful for it. I also think the timeline is the part that never makes the article. People read that a project received support and assume the maintainer can stop worrying. The worrying just moved to a different spreadsheet.
What the Numbers Do Not Show#
If you could add one line to every open source funding story, what would it be?
Ask who is on call. Not who wrote the code, not who sits on the board. Who gets the alert at 2 a.m. when a dependency breaks a downstream build. That person is the project's actual risk profile. If the answer is one person, the funding has not solved the problem yet.
Is there a metric that captures this better than downloads?
Response time to security reports, and the number of people who can cut a release. Those two numbers tell you more than a download count ever will. A project with 10 million downloads and one person who can sign a release is fragile. A project with 50,000 downloads and four release managers is not. The headlines tend to reward the first number because it is easier to collect.
Advice for the Next Cycle#
What should companies and foundations do differently?
Fund roles, not events. Fund a triage rotation. Fund documentation for the parts of the codebase only one person understands. And when you publish a story about a project, call the maintainer before you publish, not after. A short conversation would have saved me six weeks of email.
What about maintainers reading this?
Write down what you actually do in a week. Not the roadmap, the hours. When someone offers support, hand them that list and ask which line they want to fund. Most will pick something specific. That is a better outcome than a vague pledge and a thank-you note. The unglamorous work is the work. Say so, even when the headline does not.
More articles