Developers

Where to Get Started

The OpenMRS Development website - (Trac) — tickets and bug reports
OpenMRS Project Ideas — a place to look, along with our active tickets and intro tickets, for where you can help.
Different Types of OpenMRS Developers
Getting Started as a Developer
You may find some helpful information in the EHSDI Training Course.

Documentation

Developer Conference Call

We have weekly developer conference calls to discuss technical issues around OpenMRS. You can learn more about our developer conference call on the Developers Conference Call page.

[edit]

Code of Conduct

The Code of Conduct covers your behavior as a member of the OpenMRS developer community, in any forum, mailing list, wiki, web site, IRC channel, install-fest, public meeting or private correspondence.

[edit]

Conventions

When developing for OpenMRS, whether in the core code or in modules, please familiarize yourself with the OpenMRS Conventions. In order to successfully collaborate, we must all try our best to abide with some common conventions. Failure to follow these conventions will inevitably cause more work for others, so your attention to them is much appreciated.

[edit]

Best Practices

In order to help developers discover and follow our conventions, we are evolving a list of OpenMRS Best Practices. Best practices includes things like Code Review Overview.

[edit]

Subversion Code Repository

Code can be browsed online through Trac.

Code can be downloaded from our Subversion repository with your subversion client using the url http://svn.openmrs.org/openmrs

Explanation of the Subversion Repository Layout and our Subversion Repository Code of Conduct

[edit]

Submitting Bugs

See our page about submitting bugs

[edit]

Submitting Patches

See the page about submitting patches to OpenMRS.

[edit]

Requesting Subversion Repository Access

We welcome any OpenMRS related code into the repository.

All committers will be expected to adhere to the Subversion Repository Code of Conduct and follow the outlined repository conventions.

Requesting a branch (only needed by partial committers, see Creating a Branch)

Only major features need be developed in branches (small bug fixes can be submitted via patches -- see #Submitting_Patches).

Branches are stored in /openmrs/branches

Send mail to code@openmrs.org. Include:

Your trac username
Description of the feature your branch will be creating/updating
A suggested branch name

Requesting a module

Modules are stored in /openmrs-modules

Send mail to code@openmrs.org. Include:

Your Trac username on http://dev.openmrs.org
Short description of what your module will be doing
What you think your module's id should be. (e.g: htmlformentry or serialization.xstream)

We invite any developers to keep their OpenMRS-related work in a module, contrib, or branch within the OpenMRS repository. For folks that are making regular contributions, see "how to become a partial committer."

[edit]