Open source does not imply open community
This post provocatively argues that open source doesn't necessitate an open community, challenging the GitHub-era norm of constant engagement and maintainer burden. It strikes a nerve with many who feel the weight of unsolicited demands turning their passion into an unpaid second job. The discussion dissects the true meaning of "open source" and debates whether isolation or collaboration is the path forward for sustainable project health.
The Lowdown
The article, "Open Source Does Not Imply Open Community," passionately asserts that the modern, GitHub-dominated landscape has perverted the original spirit of open source, transforming it from a freedom-granting act into a source of burnout and unpaid labor for maintainers. It calls for a radical re-evaluation of how open source projects are managed.
- The Original Spirit: Historically, open source involved simple code distribution (tarballs, FTP) and minimal interaction, often just email or basic mailing lists. There was no inherent expectation of community, politics, Codes of Conduct, or extensive issue/pull request management.
- The GitHub Effect: The rise of GitHub, while centralizing development, is portrayed as having turned open source into an "unpaid job." Maintainers are now burdened with responsibilities mirroring corporate work: managing stakeholders, planning roadmaps, dealing with "office politics," and facing constant demands without compensation.
- Burnout and Invasion: This culture fosters burnout, as maintainers grapple with a deluge of issues, unsolicited feature requests, and complaints, feeling that their projects are being invaded and controlled by a demanding "community" they never consented to manage.
- Reclaiming Control: The author advocates for a return to isolated, focused development. This includes practical advice like disabling issue trackers and pull requests, using bare Git servers, and working only with small, trusted groups or completely alone.
- Redefining "Open": The core argument is that "open source" signifies code availability and licensing freedoms, not a mandate for open development processes, community engagement, or adherence to modern social policies. Maintainers should write code they love, use tools they prefer, and avoid becoming a "half tech incubator and half daycare."
The piece is a stark warning and a rallying cry for open source maintainers to reclaim their autonomy, emphasizing that true freedom in open source might lie in prioritizing personal well-being and project vision over the often-overwhelming and uncompensated demands of a perceived "community."
The Gossip
Lexicon & License: Deconstructing Open Source Definitions
Many commenters echoed the author's sentiment that "open source" fundamentally refers to the licensing and availability of code, not a mandated social contract or free support. They emphasize that licenses grant freedoms (like the four fundamental freedoms of FOSS) but don't imply zero cost, public distribution for all, or supply chain warranties. The distinction between this technical definition and often-misaligned social expectations is highlighted as a primary source of conflict and maintainer burnout, with some suggesting the need for a "SOCIAL.md" to clarify these boundaries.
Code & Conduct: Navigating Community Dynamics and CoCs
The discussion heavily weighed on the practicalities and politics of open source community management, particularly regarding Codes of Conduct (CoCs). Critics of CoCs decried them as tools for "grievance politics" or "woke/DEI/leftist entryists," arguing they instigate trouble rather than foster peace. Conversely, some commenters upheld the social aspect of open source, arguing that isolation is counterproductive, while others differentiated between "anti-social" and "anti-drama" approaches, preferring to interact only with trusted individuals rather than "internet randos."
Sustaining Software: The Bleak Economics of Free Labor
A pervasive concern among commenters was the dire economic sustainability of open-source maintenance. The prevailing expectation of "free support" and the unpaid labor for "the community" mean many maintainers receive inadequate or no compensation. While avenues like GitHub Sponsors exist, they're often a power-law system benefiting only a select few. The rise of AI agents was cited as a further threat, potentially replacing the need for human support and deepening the economic precarity for open-source developers, rendering the ecosystem "thankless and unsustainable."