The Open Source Tragedy Nobody’s Talking About: Review Board Proves Good Code Doesn’t Sell Itself

You’ve probably used Review Board. You probably never thought about who maintains it. That’s the problem.

For 17 years, a small team—led by one developer, ChipX86—built and maintained the code review tool that companies like Google, Microsoft, and Facebook quietly depend on. They didn’t charge for it. They didn’t lock features behind a paywall. They believed in the open-source dream: build something great, and the community will support it.

They were wrong.

Open source doesn’t die because nobody wants it. It dies because nobody wants to pay for it.

Review Board is still alive. But it’s in a state of ‘maintenance mode’—a polite way of saying the project is slowly fossilizing. The core maintainer is burned out. The code is stable, but innovation has flatlined. And every developer who uses it assumes someone else is handling the upkeep.

This is the silent crisis of critical infrastructure. We scream when Cloudflare goes down. We panic when npm packages get hijacked. But we ignore the quiet decay of the tools we use every day—until they break.

Here’s the uncomfortable truth: the assumption that ‘good code sells itself’ is a myth. Open-source survival requires as much business acumen as technical excellence, or the project slowly fades into legacy maintenance.

Review Board didn’t fail. It succeeded the way open source usually succeeds—by being used, loved, and taken for granted. The team tried commercialization: they spun off a hosted version, offered enterprise support. But they lacked the aggressive, venture-backed push that turns a tool into a platform. No LinkedIn posts about ‘disrupting code review.’ No acquisition rumors. Just a steady stream of bug fixes and feature requests from people who never once asked, ‘How can we help you keep this alive?’

We—the developer community—have created a system where the maintainer’s reward is more work. And then we wonder why burnout is an epidemic.

I spent years relying on Review Board without ever thinking about its sustainability. Until I read ChipX86’s blog post—raw, reflective, and painfully honest. He doesn’t blame anyone. But he does describe the paradox: the more successful your open-source project becomes, the more it demands from you, and the less you can afford to give.

If you use a free tool, you are not a customer. You are a liability to the maintainer.

That’s the twist. We’ve been sold a story that open source is a community garden where everyone tends the flowers. In reality, it’s more like a farm where one exhausted farmer grows food for a thousand hungry strangers who never bring seeds.

So what do we do? First, stop pretending ‘free’ means ‘no cost.’ The real cost is invisible: maintainer mental health, feature stagnation, and the slow death of trust. Second, if you depend on an open-source tool, ask yourself: have you ever contributed code? Donated money? Sent a thank-you note that wasn’t a bug report? If the answer is no, you’re part of the problem.

Review Board isn’t dead. But it’s a warning. Every popular open-source project that hasn’t figured out a sustainable model is on the same trajectory. The difference is that ChipX86 had the courage to write about it. Most maintainers just quietly close their laptops one day and never come back.

This isn’t a call to panic. It’s a call to pay attention. Because the tools you love will not save themselves. And good code, it turns out, does not sell itself.