...
Potentially add information on how to watch/track issues. Make a diagram showing how a bug is first called 'roadmap' and is triaged within the sprint schedule (could be up to two weeks). Specifically state that implementers should view triage to make sure it is core bug. Do we need guidelines our gates for 'hot fix'? Add more on how to use labels (potential)
Potential text:
- All bugs must be submitted to the OpenLMIS Jira project.
- "Follow or watch the OLMIS ticket for updates on its status. Instructions on tracking issues: HERE."
- Additional information: Implementer is responsible for informing implementation stakeholders team about the status of the bug.
Proposing or Implementing New Features in OpenLMIS
Update Coordinating with the Global Community to reference the new section on Proposing a new feature:
- Potentially add information on how to submit a 'new feature' ticket in JIRA. Be explicit about how to interact with Product Committee.
- Potentially add more detail about the feature and technical proposal piece. Do we need to be explicit in how long it will take the community to respond or what the average length of time is?
Update the Coordinating with the Global Community Section with information on contributing features. https://github.com/OpenLMIS/openlmis-ref-distro/blob/master/docs/source/contribute/contributionGuide.md
Update Feature Roadmap, add the following text for SUGGESTING FEATURES:
Please follow these instruction if you want to suggest a new feature or if you'd like to develop a feature and contribute it back to OpenLMIS. The OpenLMIS Product community will review, provide feedback, and prioritize. If the work isn't funded, the Product Committee will attempt to identify resources to implement and bring to the attention of the Governance Committee. If this work is funded and done by external resources, the work can move forward with those resources.
...