Beginner Projects
A quick browse through the OpenMRS source code will tell you that its a big and scary place. Where's a good place to start? Reports in Trac can be deceptive, deceptively hard... or deceptively easy. So we've compiled a list of quick places to contribute. There's plenty to do, and we sure could use the help. Here are some fixes that are straightforward; they just need some time and attention
Contents |
Tickets Marked as Introductory Tickets
There are tickets on Trac (our Project site) that are marked as "intro tickets". These tickets are meant to describe projects that should be fairly quick and easy. Browse those and feel free to request ownership.
Tickets Marked as Trivial
There are tickets on Trac (our Project site) that are labeled as "trivial". These tickets are meant to describe projects that should be fairly quick and easy. Browse those and feel free to request ownership.
Source Code Commenting
Abstract: The source code is commented (only) occasionally. In some places, the javadoc comments are either incorrect or out of date. See ticket #143 for details. As you browse the code, it would be nice to have at least class level comments as well.
Module Version Tag
Mentor(s): Ben Wolfe and Burke Mamlin
Abstract: What changed from one version of a module to the next isn't really documented anywhere. It would be nice if the developer had a place to put a small list of what he/she changed since the last version. The best place for this is in the /metadata/config.xml file in a module. See ticket #338 for more details
Add Patient Data to Demo Data Set
Mentor(s): Ben Wolfe and Burke Mamlin
Abstract: Demo data is included in the liquibase-data.zip files found in metadata/model. The demo data is limited to just concepts and a few patients. The liquibase-demo-data.xml should be given 100 or so patients and a few data points for weight or height for each of them.
Removing Calls to Deprecated Methods
Mentor(s): Ben Wolfe and Burke Mamlin
Abstract: In version 1.3 we modified a lot of the API method signatures to make them more uniform. Inside most of the old methods is a straight forwarding of the parameters to the new method name. The API and the webapp still make calls to some those old deprecated methods. These calls to deprecated methods need to be changed to the new names. See ticket #1142
