Open MPI Git repositories
As of September 2014, Github does not support fine-grained directory-based ACLs inside Git repositories.
NOTE: AS OF SEPTEMBER 2016, THIS PAGE IS A BIT STALE; WE NO LONGER HAVE AN
ompi-release REPO. THIS PAGE NEEDS TO BE UPDATED.
As such, to continue Open MPI's long tradition of only allowing Release Managers and Gatekeepers to write to release branches, Open MPI has two Git repositories:
https://github.com/open-mpi/ompi This is the main repository for active development. Active Open MPI developers have push access to this repository. There is only one branch in this repository:
- Do NOT push additional branches into this repository.
- If you want to share a branch with someone, push it somewhere else (e.g., your own personal Github fork of the main
- Let me be totally clear: do not push non-
masterbranches into the community
ompirepo! That's what your personal fork repos are for.
- All wiki pages for the Open MPI code base are on this project.
- All bugs/enhancements are filed as Github issues on this project.
- https://github.com/open-mpi/ompi-release This repository contains all the branches for all of Open MPI's official release series (as of this writing: v0.9, v1.0, ..., v1.8).
- There is intentionally no
masterbranch in this repo.
- This repo only contains release branches.
- Only the Open MPI Release Managers and Gatekeepers have write access to this repo.
- The only way to get code into this repo is to submit a Github pull request.
Open MPI's first source code commit was on November 22, 2003. The project initially used CVS as its version control system. When Subversion finally hit v1.0, the project moved its code to a Subversion repository. The Subversion repository, a wiki and issue system (Trac) were all hosted at Indiana University.
Over time, developers started using Mercurial and Git for side development and forks. The project started supporting official Mercurial and Git mirrors of the SVN repository (on Bitbucket and Github, respectively).
Eventually, the Open MPI developers decided to wholly move to Git, and Github was selected as the hosting platform. In September, 2014, much of the Subversion and Trac (wiki and tickets) content were migrated to Github. Specifically:
- The Subversion trunk was moved to the
ompiGithub repo (https://github.com/open-mpi/ompi)
- The Subversion release branches were moved to the
ompi-releaseGithub repo (https://github.com/open-mpi/ompi-release)
- All other Subversion branches (e.g., the private /tmp branches and the /vendor branches) were left in Subversion. Subversion was left in a read-only status.
- The Trac wiki pages were converted to Github Markdown and moved to the
- All open, non-Changeset-Move-Request Trac tickets were converted to be Github issues on the