Repository work flow structure
From OpenEMR Project Wiki
Revision as of 22:06, 11 November 2010 by Bradymiller (talk | contribs)
Overview
Our official repository is kept on sourceforge via git. We recently migrated from cvs to git, which is described HERE. Our sourceforge repository also has three official mirrors, which are described HERE. To avoid breaking the main sourceforge git repository, we are using the following work flow and development structure. The proper way for individual developers to set up their personal git repository is described HERE.
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).
- A standardized method to commit to the sourceforge repository has been documented HERE . Rather than pull in the entire remote branch of somebody else's code, recommend pulling in each commit via the 'cherry-pick' command.
- 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" (no questions asked and within 24 hours).
- 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 here). If this is done correctly, then it only takes an "Integrator" 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 here). If this is done correctly, then it only takes an "Integrator" several minutes to commit your code to the sourceforge repository if deemed acceptable.
Developers
(Requires a sourceforge account - only sourceforge account name and company associations are shown.) (Ideally, each developer should have their own sourceforge account.)
Integration Developers
- bradymiller
- stephen-smith
- sunsetsystems (Rod at Sunset Systems)
- tmccormi (Tony at Medical Information Integration)
Privileged Developers
- acmoore
- andres_paglayan
- cfapress
- drbowen (Sam at Medical Information Integration)
- larrylart
- markleeds
- mmfsystems (Vineet at MMF Systems)
- rachoac (Aron at Medical Information Integration)
- tekknogenius
- visolve-selvi (Selvi at Visolve)
- whimmel
- zhhealthcare (Paul, Jacob, Sam, and Eldho at Z&H Healthcare Solutions)
