Code Repositories
Anonymous Read-Only Access
Anyone can browse the source code online with a browser. For example, you can browser code at https://github.com/openmrs.
To check out a local copy of the code using git:
git clone https://github.com/openmrs/openmrs-core
See Using Git for more information.
Read/Write Git Access
To submit changes to a repository, we recommend following GitHub conventions of forking the repository and submitting a pull request.  Push access to a repository is managed by the owner of the repository. For repositories under individual user accounts within GitHub, you can request access rights from that user. For repositories within the OpenMRS organization on GitHub, developers who are /dev/3 or above already have push privileges but are expected only to push to repositories when appropriate per our GitHub Conventions.
Creating a new module or project
Developers are encouraged to publish their OpenMRS-related work with an OSI-approved license under their account on GitHub.  Community-developed modules and projects may request a project within the JIRA Issue Tracking System.
Using your personal repository on GitHub
- Create a new repo: https://github.com/new
- Name the project using our naming conventions for easier searching/finding of projects across GitHub repositories.
- Modules: "openmrs-module-yournewmoduleid"Â
- Contributions: "openmrs-contrib-uniquename"
- Start using it immediately!
Requesting to store it in the OpenMRS organization on GitHub:
When multiple developers across multiple organizations are sharing a repository, it may be easier to host it under the OpenMRS organization on GitHub. If a repository needs to move under the OpenMRS organization in GitHub, please post this request to the Repository Management category on OpenMRS Talk.
See GitHub Code of Conduct > Hosting a module under the OpenMRS organization.
See Also
- Some older projects (work prior to 2012) are still available in the OpenMRS Subversion repository, using Subversion (SVN).