The Apache Software Foundation has completed migrating its Git service to GitHub, says its Git service was decommissioned after completing migration in February
Provides source code tooling services for 200M+ lines of code across 350+ Apache Projects — The Apache® Software Foundation …
Context & Ripple Effects
This closes a decade-long consolidation arc in open-source hosting. SourceForge, once the default home for project downloads, spent 2016–2018 trying to stay relevant through overhauls — terminating DevShare and rolling out a redesigned directory with a GitHub importer tool. Then came Microsoft's acquisition of GitHub, which ended GitHub's profitability struggle but raised the question of whether developers would scatter to GitLab or BitBucket.
The Apache Software Foundation's answer is the opposite of scattering: the steward of 350+ projects and 200M+ lines of code has moved everything onto GitHub and shut down its own Git service in February. That makes one of open-source's most important infrastructure bodies fully dependent on a single commercial platform — a dependency that later coverage of GitHub's reliability troubles puts in a new light.
First-order effects
- Apache's 350+ projects now run their source code workflow entirely on GitHub-hosted repositories, and the Foundation sheds the cost and maintenance burden of operating its own Git infrastructure.
- GitHub adds one of open-source's flagship portfolios to its platform, deepening the moat created by Microsoft's ownership.
Second-order effects
- Rivals GitLab and BitBucket lose the most credible template for foundation-scale migrations; competing for the next Apache-sized account becomes harder when the incumbent can point to this one.
- Concentration cuts both ways: when peak traffic overwhelmed GitHub's infrastructure and produced a nearly eight-hour outage across API, Actions, and Pull Requests, every migrated project inherited that single point of failure.
Third-order effects
- If more foundations follow Apache's lead, open-source version control effectively standardizes on one vendor's terms of service, pricing, and uptime — turning GitHub's reliability-first response to incidents into de facto public infrastructure policy.
- That dependency is exactly the opening for challengers: OpenAI's nascent GitHub alternative, reportedly prompted by engineer frustration with outages, targets the same concentration this migration exemplifies.
The trend: Open-source code hosting is consolidating onto a single commercial control plane, trading self-operated autonomy for ecosystem gravity while making the whole ecosystem hostage to one vendor's uptime.