Developer Checklist
The OpenMRS community actively encourages members to grow as contributors by taking up more advanced roles within the community. Many of our dedicated volunteers began by working on introductory tickets, and went on to become senior contributors within the community, working on a wide range of tasks from core OpenMRS development to working on individual implementations.
The following checklist signifies potential milestones which a developer may follow. Note that these are very generic guidelines, with no strict timelines or strict order of precedence. Rather, they serve as inspiration for potential options available to all community members.
OpenMRS Developer Checklist
| □ | Join the OpenMRS community. Get an OpenMRS ID. Introduce yourself to others. Begin contributing to introductory tickets. |
| □ | Gain more knowledge of the OpenMRS, and begin to participate in mailing list discussions. |
| □ | Begin to suggest potential improvements to the existing code base. |
| □ | Identify a module or field you're motivated to work on, and begin to familiarize yourself in this field by building relationships with other interested people. |
| □ | Becomes a sprint leader or project owner. |
| □ | Volunteer to mentor others. You may mentor students who participate in various internship programs, or other developers working on implementation specific features. |
| □ | Work directly with associated implementations in need of your expertise. |
| □ | Become a full-time community volunteer who is supported by an affiliated institution or an implementation. |
| □ | Link your interest in OpenMRS with other related medical applications, systems, tools, API's, or frameworks; and become a champion for collaboration and mutual support. |