I maintain something you depend on. I am done pretending that is sustainable.
fourteen years, two co-maintainers, zero budget, and an inbox that thinks it owns me
Contents
skerry is a small C library that parses JSON. it is maybe four thousand lines. it is also, as far as I can tell from the download numbers and the angry emails, inside a lot of things you use: routers, a payment terminal, at least two cars, and the backend of companies whose quarterly profit is larger than the GDP of the town I live in. I have maintained it for fourteen years. I have two co-maintainers who help when they can. our budget is zero.
I am writing this because last week I got an email from a company, a real one, a big one, demanding I fix a bug they considered critical "as a matter of urgency" and asking what my "SLA for security issues" is. they do not pay me. they have never paid me. they vendored my code into a product they sell for money and now they would like me to provide enterprise support, for free, on their timeline. I replied with one word. you can guess which.
what maintaining actually looks like
it is not the code. the code is the fun part and it is maybe 10% of the time. the rest is:
- issues that are not bugs in skerry, they are bugs in how someone used skerry, and I debug their code for free so they will go away.
- "is this still maintained?" opened on a library I committed to yesterday.
- a feature request that is really a demand, followed by "wow, hostile much" when I say no.
- security reports, which I take seriously and drop everything for, mixed in with the noise so I cannot ignore the inbox even when I want to.
- the slow realisation that a thing I made for joy is now load bearing for strangers who are angry at me.
the "just" people
every burnout post gets the same replies. "just add more maintainers." I have tried, onboarding a co-maintainer you can trust with a security sensitive C library is months of work and most people want commit access, not responsibility. "just charge for it." the license is open, the people using it chose it because it was free, the moment I charge they fork the last free version and I have the same work and a lawsuit. "just stop." then it bitrots, a CVE lands in your car, and you email me anyway.
here is a talk that says it better than I can, Kat Cosgrove on every open source maintainer being burned out, watch it before you open your next "is this maintained?" issue:
what I actually want
not pity. I like the work, the real work. I want three things. read CONTRIBUTING.md before you open an issue, it exists and it is short. if your company's product depends on my evenings, fund the evenings, even a little, even once. and when a maintainer says no, "no" is a complete answer, it is not the opening offer in a negotiation.
I am not quitting. I have a family and a day job and I will keep skerry alive because people's cars literally depend on it, which is exactly the problem. nej. I just needed to say it out loud, in public, with my name on it. now I am going to go offline for the weekend, because I have one, and skerry will be fine, because it has survived worse than me being tired.
Written by
Karl Lindqvist
Maintainer of skerry, the C JSON parser your company vendors and never thanks. 14 years, 2 co-maintainers, 0 budget. Gothenburg. Read CONTRIBUTING.md before you open an issue.
Get the best of #open_source_drama weekly
One email each Monday with the most useful posts. No spam; unsubscribe in one click.
Comments
Sign in to join the conversation.
Sign in to comment