Repository work flow structure

Overview

Our main official repository is kept on sourceforge via git. We migrated from cvs to git on 10/30/2010, which is described on the git migration wiki page. Our sourceforge repository also has six official mirrors, which are described below. The proper way for individual developers to set up their personal git repository is described on the git for OpenEMR tutorial wiki page. To avoid breaking the main sourceforge git repository, we are using the following git repository structure, work flow and development structure:

Official git Main Repository

Sourceforge

repository link: git://openemr.git.sourceforge.net/gitroot/openemr/openemr
web page link: http://sourceforge.net/projects/openemr/develop

Official git Repository Mirrors

github

repository link: git://github.com/openemr/openemr.git
web page link: http://github.com/openemr/openemr
mirrors from Sourceforge repository every 30 minutes via an external script

gitorious

repository link: git://gitorious.org/openemr/openemr.git
web page link: http://gitorious.org/openemr/openemr
mirrors from Sourceforge repository every 30 minutes via an external script

google code

repository link: https://code.google.com/p/openemr
web page link: http://code.google.com/p/openemr
mirrors from Sourceforge repository every 30 minutes via an external script

bitbucket

repository link: https://bitbucket.org/openemr/openemr.git
web page link: http://bitbucket.org/openemr/openemr/
mirrors from Sourceforge repository every 30 minutes via an external script

repo.or.cz

repository link: git://repo.or.cz/openemr.git
web page link: http://repo.or.cz/w/openemr.git
Supposed to mirror from the Sourceforge repository every 60 minutes automatically by the repo.or.cz site.

assembla

repository link: git://git.assembla.com/openemr.git
web page link: http://www.assembla.com/spaces/openemr/
mirrors from Sourceforge repository every 30 minutes via an external script

Experimental Repository Mirrors

launchpad

This is actually a Bazaar repository, which the Launchpad site automatically converts from git. Due to technical limitations (they plan to fix this), it is only able to mirror the master branch.

repository link: http://code.launchpad.net/openemr
web page link: http://code.launchpad.net/openemr
Supposed to mirror from the Sourceforge repository every 4-6 hours automatically by the launchpad.net site.

Developer roles and work flow

Integration Developers

These are the only developers with commit access to the sourceforge repository.
They have demonstrated common sense and proficiency in git and OpenEMR development.
They are responsible for committing their own code.
They are willing to commit the code of the "Privileged Developers" (when requested).
Standardized methods to commit to the sourceforge repository have been documented in the 'Advanced Usage' section of the git for OpenEMR tutorial wiki page . Rather than pull in the entire remote branch of somebody else's code, recommend pulling in each commit via the 'cherry-pick' command (this is specifically documented on the git for OpenEMR tutorial wiki page).

Privileged Developers

These are developers that have demonstrated common sense and proficiency in OpenEMR development.
They do not have commit access to the sourceforge repository.
Their code will be directly committed to the sourceforge repository upon request to an "Integration Developer" in the Developer forum. (will be committed within 24 hours). To clarify, this is for code that is ready to be committed; ie. do not request commits of code that might need further review.

To take advantage of this "fast-track" commit, you need to submit code via a public git branch. (instructions on how to do this can be found on this wiki page). If this is done correctly, then it only takes an "Integration Developer" several minutes to commit your code to the sourceforge repository.

Standard Developers

Standard developers whom have or are in process of submitting code.
They do not have commit access to the sourceforge repository.
Their code needs to be reviewed before committing to the sourceforge repository.

Best way to do this is to submit code via a public git branch. (instructions on how to do this can be found on this wiki page). If this is done correctly, then it only takes an "Integration Developers" several minutes to commit your code to the sourceforge repository if deemed acceptable by the community review.