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.
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
Thanks @dkayiwa. When we spoke last week, I think we decided Wednesday at 17:00 UTC may be too late in the day for many, so instead chose Mondays at 13:00 UTC (the hour before the TAC calls). I updated your post accordingly.
@dkayiwa, since you discovered the conflict with the PM call thisweek, I assume we are meeting today at the next hour (15:00 UTC)? I’ll share this assumption in #platform (on Slack) as well.
Thanks @grace. Please let us know if/when that changes.
My mother in law was discharged from hospital yesterday and i drove her back to the village for over 350km. By the time i got back home, it was too late!
Though commonly used in Fhir2 module , is it necessary to introduce Lombok in platform as a general standard for newer non-transient objects / object properties in components / modules were necessary .
I may have missed out on it ,but I have not come across it’s usage .
@dkayiwa, when you are back online, please confirm our kickoff meeting for Platform Team will be on Wednesday, 30 June, at 17:00 UTC. I’ve added this to om.rs/cal, but would be happy to change if needed.
Recently I tried out the docker project specifically for platform and I ran into this issue where I noticed @dkayiwa proposed filing a ticket (Not sure if this was done).
May be this is more of the task for the INFRA team so I am tagging @cintiadr@ibacher@raff@mksrom and @mozzy seeing you recently commited to the project