As demands on the OpenMRS Platform grow, we need a more coordinated approach to handling Platform issues (prioritizing bug fixes, feature requests) and building a road map for the Platform. To this end, we are introducing the Platform Team with weekly meetings to focus on OpenMRS Platform needs. If you are willing to roll up your sleeves and help advance the OpenMRS Platform, please join us.
- Wiki page: om.rs/platform
- Notes page: om.rs/platformnotes
- JIRA board: om.rs/platformboard
- Slack channel: #openmrs/platform
- Zoom meeting: om.rs/zoomplatform
Vision:
- Robust & reliable APIs to support OpenMRS solutions, using an increasingly modular architecture that can scale as needed while preserving the benefits of administering a monolithic application.
Purpose:
- Review backlog and set priorities for Platform issues (bugs, new features, etc.)
- Bring major decisions to the Technical Action Committee to set the overall strategy and roadmap for the OpenMRS Platform
- Coordinate Platform-specific efforts across the community
Weekly Meeting Time
- Wednesdays at 17:00 UTC on Zoom (om.rs/zoomplatform)
Who can join?
- Anyone in the OpenMRS community interested in helping move us toward our vision.
Scope
- OpenMRS Core + Database
- APIs: RESTWS + FHIR
- Application administration
- Metadata & module management
- Backend Support for Frontend Framework
- Triaging/prioritizing Platform needs for the community
Out of Scope:
- Frontend applications
- Vertical- or Implementation-specific solutions
/cc @mseaton, @ibacher, @mksd, @jennifer, @grace @burke @mogoodrich @ssmusoke @fruether