Before GitHub
3 hours ago
- #Software Archival
- #GitHub
- #Open Source
- GitHub was not the author's first open-source platform; they previously used SourceForge, self-hosted Trac and Subversion, and Bitbucket before moving everything to GitHub.
- GitHub became central to the author's open-source identity, fostering community, professional relationships, and friendships through repositories and collaborations.
- The author is disappointed with GitHub's current decline, noting it was once key social infrastructure for open-source, not just a code host.
- GitHub enabled the micro-dependency phenomenon, making publishing and consuming code almost frictionless, which expanded open-source projects but introduced complexity.
- Pre-GitHub, open-source was smaller and more reputation-based, with dependencies involving more friction and vetting, often requiring vendoring for reliability.
- Despite distributed version control systems like Git and Mercurial reducing the need for a central host, GitHub became the centralized service for open-source hosting.
- GitHub’s benefits included easy project creation and discovery, contribution tools, archival of abandoned projects, and trust mechanisms, serving as a library for software.
- Concerns now include GitHub's instability, product churn, AI noise, unclear leadership, and a shift away from community focus, leading some notable projects to move elsewhere.
- Decentralizing to multiple forges or self-hosted solutions could increase autonomy but risks losing social context and archival benefits that GitHub provided.
- The author advocates for a public, well-funded archive for open-source software to preserve source code, releases, and project context independently of corporate interests.
- The future should balance learning from GitHub's era with pre-GitHub autonomy, ensuring easier project migration and preservation to avoid cultural crises.