Sure! First, A+ on making the Get Involved link on both prominent and welcoming. Having a great ‘how to help’ page doesn’t matter if no one can find it.

Here are some observations and suggestions:


The help page itself is well done. I like the fact that you don’t make people join a mailing list in order to talk to you – there’s a contact form where you make it easy to send in one’s thoughts. Hopefully that results in a prompt response and some personal attention to help the potential contributor find their way in.

I read the whole help page, and when I got to “Create a profile” at the bottom… I initially could not figure out how to do that. There was nothing that looked like a link to click. I checked the links in the footer. Still no luck. At some point I waved my mouse around and figured out that the orange headings are actually links, and clicking on “Get an OpenMRS ID” was what I needed to do.

Consider making the text “Create a profile” into a link, and also adding to the list of ‘Other OpenMRS sites’ in the footer.

The same issue exists for the text “let us know!” under the Suggest heading. Since it’s not immediately obvious that the orange headings are, in fact, links, I suggest making a bit of text under each of the headings clickable as well.


Moving on, the first sentence under Document is, “Do you have experience and skills with technical writing?” This makes it sound like you only want experienced technical writers as contributors, which I’m sure is not the case. Clicking through, the /help/document page is much more welcoming.

Consider something like, “OpenMRS needs assistance maintaining its documentation and resources. It is important to keep everything up to date and well-organized. We welcome anyone with an interest in writing and organizing information. Don’t worry if you’re not an experienced technical writer, there’s a place for everyone!”

Also on /help/document, it would be nice if “Let us know” linked to the Contact form with the ‘Getting Involved & Volunteering’ value pre-filled and the Documentation checkbox already checked. The fewer options the person has to think about and decide upon, the more likely they’ll finish it and submit the form.

Finally, I could not find any information on how to patch itself, or I would have. :)


While skimming the docs for new developers, I joined the #openmrs IRC channel on Freenode. As luck would have it, one of the Google Code-In participants, was having trouble building the project. Unable to resist, I went back to the docs to see if I could help.

I had no trouble finding and cloning the openmrs-core code, and after noting that there was a pom.xml, tried a naive ‘mvn install’ on it.

Sure enough, I had the same two test errors the student did. (He also had two test failures that I did not see.)

And another person reported the same thing last week on the OpenMRS Developers group.

With three of us experiencing it, there’s some kind of an issue here. A build that doesn’t work for a new user is a huge barrier to entry, because they may not know the tools well enough to get around it.

I replied to the thread on the OpenMRS Developers group so hopefully something can be done to improve things. Perhaps those problematic tests could be skipped by default, and the set up docs could be improved to explain what to do if the build fails.

All the text on the wiki and the channel /topic says the IRC channel is logged, but The logs after March 2014 are missing. If this is not something the community wants to work on, consider asking or another service to log the channel for you.


The getting started docs for OpenMRS are great. Except for the build failure, these are all minor suggested improvements. I don’t think I’ve seen another project that publishes a book on how to get started!