Why Apache Foundation Hasn't Adopted Git Yet: A Comprehensive Analysis

In the rapidly evolving landscape of open-source software development, the Apache Software Foundation (ASF) plays a pivotal role. Despite numerous discussions and potential benefits, the ASF has yet to fully embrace Git as its primary version control system (VCS).

Background and Historical Context

The ASF has a number of projects, each with its own unique dynamics and contributions. Historically, the foundation has relied primarily on Subversion (SVN) for its VCS needs. This choice isn't without controversy as some members, including myself, advocate for a switch to Git. Git, known for its speed, efficiency, and extensive branching capabilities, offers significant advantages over SVN for modern software development practices.

Why the Transition to Git Hasn't Happened Yet

One of the primary reasons for the delay in transitioning to Git is the sheer size and complexity of the ASF infrastructure. Maintaining and managing over 90,000 projects with a team of only 3-5 part-time volunteers is a significant challenge. The infrastructure has been largely responsive to SVN needs for decades, a system inherited from the 1980s. Introducing a new VCS like Git would require considerable resources that the current setup might not be equipped to handle.

Current Status of Git Support

As of my last update, the ASF infrastructure team supports read-only mirrors of SVN repositories. A detailed plan for providing full read and write access to Git has been outlined since November 2010. This plan, being managed by volunteers, has progressed slowly but steadily. According to the latest indications, most projects are likely to have full Git access by the end of 2011. However, the current state of affairs is such that only read-only mirrors are available for many projects.

ASF Members and Git

ASF members, including myself, can request that their projects be mirrored to read-only Git repositories. For example, I am a committer on MRUnit, and I use git-svn to interact with the SVN repository. This hybrid approach leverages the strengths of both Git and SVN, providing a smooth transition while addressing the urgent need for Git support. Some projects have already adopted this approach, suggesting a growing trend towards Git use within the ASF.

Pragmatic Considerations

The decision not to support Git as a primary VCS is rooted in pragmatic considerations. The infrastructure team must balance the needs of the large number of projects with the practicalities of supporting a single VCS. Currently, the combination of SVN and Git through git-svn provides a reasonable method of integration, making it easier for projects to transition at their own pace.

Conclusion

While the shift to Git is on the horizon, the current infrastructure of the Apache Software Foundation presents significant challenges. The ongoing development and support for Git mirrors offer a pragmatic solution, allowing for a gradual transition. As the ASF continues to grow and improve its infrastructure, we can expect to see more projects adopting Git as their primary VCS.

If you have any questions or need further information, please feel free to comment or reach out to the infrastructure team directly.