Skip to content
Tech News
← Back to articles

Open source does not imply open community

read original get Open Source Community Guide → more articles
Why This Matters

This article highlights how the open source movement has evolved from simple, community-driven projects to complex, corporate-managed ecosystems, particularly with the rise of platforms like GitHub. It underscores the challenges faced by maintainers who now juggle community expectations, corporate interests, and personal passions, raising questions about the true openness of modern open source. Understanding this shift is crucial for both developers and consumers to navigate the current landscape and foster healthier open source communities.

Key Takeaways

Open source software has existed long before the invention of the (D)VCS. The author likely hosted a barebones HTML webpage or a txt file describing the project. There definitely was an FTP server somewhere with tarballs. The author may have been reachable by email.

If you were really lucky, there was a mailing list you could sign up for to receive announcements and maybe discuss the software with other interested parties. There might have been an unofficial IRC channel someone created under the name of the software so people could discuss it.

This was and still is open source.

No "community". No politics. No Code of Conduct. No pull requests or issues. No wiki. No core team.

Later, we had sites like Sourceforge. You got your CVS/SVN and mailing lists operated for essentially "free", and it was easier to build in the open.

Then came the DVCS wars which git decidedly won, and the world eventually converged on Github.

"In the late 00's, Github was created. This has made a lot of people very angry and been widely regarded as a bad move." - Douglas Adams if he were alive today.

Github turned all of open source into an unpaid job for maintainers. You go to work and find newly assigned tickets; have meetings with stakeholders; plan a roadmap; deal with office politics and distractions; hit your deadlines, metrics, and KPIs; come into work one day and learn the requirements have changed again and now you have to start over. Standups. One-on-ones. Agile. Waterfall. But you're getting a paycheck and health insurance, so you just deal with the nonsense.

Then you come home from work and it's time to unwind on something you enjoy. Ding, you've got notifications. Issues are piling up. Pull requests are being flung in your direction completely rearchitecting the software to do things that were never really within scope. Complaints. Demands. There's now a chat group. People with no patience are angry and now you have to babysit them, have your own one-on-ones. There's a "community" now that you're responsible for. You never signed up for this, but this baggage is just the way it is, right? Suddenly open source is a second job. You're burned out. You don't even have control or direction over your own project anymore without your name being dragged through the mud.