Before GitHub (15 minute read)
GitHub transformed open source from a smaller world of self-hosted projects to frictionless micro-dependencies, but its current decline raises questions about what comes next and the need for independent archival infrastructure.
What: A reflection on how GitHub changed open source culture from the pre-2008 era of self-hosted infrastructure (Trac, SVN, personal servers) to today's centralized, low-friction ecosystem, and what might replace it as developers begin leaving the platform.
Why it matters: As GitHub shows signs of decline (instability, product churn, leadership issues), the open source community faces losing both a central hub and an accidental archive of software history, forcing developers to reconsider how to preserve the social context of projects (issues, discussions, releases) beyond just code.
Takeaway: Consider how your projects would survive if GitHub disappeared tomorrow—the distributed nature of Git protects code, but issues, pull requests, and project history may need separate archival strategies.
Deep dive
- Before GitHub, open source projects ran their own infrastructure (Trac, Subversion, tarballs) or used SourceForge, creating natural friction that limited dependencies and encouraged vendoring code directly into repositories
- The pre-GitHub world had fewer projects but more curation—dependencies came with history, reputation, and community trust built over years, not just package names
- Despite Git being philosophically distributed, GitHub became the centralized hub of open source, creating one of the great ironies of modern software development
- GitHub made open source dramatically more inclusive by reducing friction to near-zero for both publishing and consuming code, enabling the explosion of micro-dependencies seen in npm and similar ecosystems
- The platform accidentally became an archive and library for software history, keeping abandoned projects discoverable and preserving forks, issues, and discussions that would have disappeared on personal servers
- GitHub is now showing signs of decline: instability, product churn, Copilot AI integration complaints, and unclear leadership are driving notable projects away
- High-profile departures include Mitchell Hashimoto's Ghostty and other projects moving to Codeberg, signaling a potential shift that seemed unthinkable just years ago
- Returning to decentralized, self-hosted forges could restore autonomy but risks losing the archival function GitHub provided—issues, reviews, design discussions, and release notes are fragile and disappear when servers shut down
- The author calls for a well-funded, public archive for open source software independent of commercial platforms, focused on preserving source code, release artifacts, metadata, and project context
- The distributed nature of Git only protects the code itself; the social context that makes projects understandable and maintainable lives in centralized platforms and is more vulnerable than most developers realize
- Whatever comes next should make it easier to move projects and mirror their social context, harder for one company's decisions to become a cultural crisis for the entire ecosystem
Decoder
- Trac: Web-based project management and bug tracking system popular before GitHub, often paired with Subversion
- SourceForge: Early hosting platform for open source projects (founded 1999), once dominant but declined after GitHub's rise
- Subversion (SVN): Centralized version control system that required a single authoritative server, predecessor to Git
- Vendoring: Including third-party code directly in your own repository rather than depending on external package managers
- Pocoo: The author's open source collective for sharing server costs and infrastructure maintenance
- Codeberg: Non-profit, community-driven Git hosting platform based in Germany, emerging as GitHub alternative
- cgit: Lightweight web interface for Git repositories, used for self-hosted Git browsing
Original article
Open source was a much smaller world before GitHub, and projects had to run their own infrastructure.