Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
| Stage | Criteria | Expectations | Privileges | Example Role(s) |
|---|
/dev/null "Community" | - Be or desire to be a developer
| - Can communicate well and show respect for others
- Willing to be opened
| - Chat with devs on IRC
- Can become a /dev/1
- Claim an intro ticket (or a non-intro ticket with assistance from a /dev/2+)
| |
/dev/1 "Learning" | - OpenMRS ID
- Development Environment
- RTFM
- Introduced
- Claim ticket
- Pull Request Accepted
- Pass 5-10 question Introductory Quiz
| - Has tackled at least one intro ticket
- Can write a unit test
| - GSoC
- Post to dev list
- Propose topic(s) on Dev Forum(s)
| |
/dev/2 "Contributing" | - Helps others
- Participate in Dev Forum(s)
- Active ≥3 months
| - Can handle low complexity tickets
- Has tackled at least 10 tickets
- Can create a module
- Has pair programmed
| - Claim low-to-moderate complexity tickets
- Publish a module and resources to Maven repo
| |
/dev/3 "Cooperating" | - Curate ticket(s)
- Working with others
| - Can handle moderate complexity tickets
- Can function independently, yet looks for opportunities to pair program
| - Code review
- Configure CI
- Lead Sprint
- Push to module(s)
| |
/dev/4 "Collaborating" | - Spike
- Leading Dev Forum(s)
- Leading Sprints
- Endorsed by implementer(s)
| - Can handle complex tickets
- Has publicly thanked at least 10 other devs
- Finds effective ways for developers across organizations to work together
| | |
/dev/5 "Leading" | - Responsible for a component
- Mentor
- Engages with implementation(s)
| - Leading development
- Finds ways to make local implementation development benefit the community and community development benefit local implementations.
| - Can establish coding conventions
- Can deprecate services
| - Participant in code@openmrs.org
|