...
- Ensuring that community development swim lane is meeting its expectations
- At least 60% of community development effort is on tickets
- Considering bugs across OpenMRS core and all OpenMRS-supported modules
- Prioritizing quick wins, and low-hanging fruit, e.g. recently-reported bugs, highly-voted small new features, and avoiding intro tickets except for assigning them to n00bs or unless they are the only reasonable option for pair ** programming with a n00b
- ~30% of community development effort is spent assessing curating tickets, answers.openmrs.org, answering dev list questions, addressing n00b code reviews very quickly & looking for stale code reviews
- Ensure n00bs are happy & productive
- Find an opportunity to pair program at least once/week
- TODO: find metric that this is happening
- Hang in IRC
- At least 60% of community development effort is on tickets
- Mailing the dev list once/week bragging about tickets closed, votes satisfied, and notable n00b contributions
...