| User Profile | ||||
|---|---|---|---|---|
|
Description
The Community Development Leader is an individual who leads up the pool of community developers in the community development swim lane. This roll rotates every sprint/iteration between dedicated developers.
...
responsible for ensuring OpenMRS Community developers, from newcomers to experienced developers, are happy and successful and that they're able to effectively and meaningfully contribute to OpenMRS development.
Requirements
- Dedication to the OpenMRS mission, vision, and values
- Strong programming skills/experience relevant to OpenMRS programming
- Good communication skills and ability to interact effectively with people from diverse cultures
- Enough available, dedicated time to ensure that the community development swim lane is meeting expectations
Responsibilities
- Ensuring that community development swim lane is meeting its expectations
- Ensure all plans on ci.openmrs.org are green. If plans are failing, facilitate communicating the need to address them & finding someone to take responsibility to resolve them.
- 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 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
- Mailing the dev list once/week bragging fulfill responsibilities
Responsibilities
- Chief advocate for developer experience
- Developer Tools – the time it takes to get started
- Continuous Integration – the confidence a developer has that her changes won't break things
- Developer Documentation – access to a useful Developer Guide, API documentation, etc.
- Developer Community Tools – ease of finding and communicating effectively with other devlepers
- Cheerleading – how the developer & broader community knows about tickets closed, votes satisfied, and notable
...
- contributions
- Overseeing the application of OpenMRS Developer Stages
- Ensuring we always have an identified Release Manager for our Platform and Reference Application and that they are meeting community expectations
- Defining and ensuring goals are met for community development
- Response to pull requests
- Response to bugs
- Response to development-related Talk topics