Last week, the Technical Action Committee had a kickoff meeting. Most of the discussion focused on reviewing roles and responsibilities, discussing the differences between the Product Change Committee and the Technical Action Committee, and sharing initial ideas around what the TAC should focus on for the next couple of months.
Here are some of the points that came up during the meeting, some of which are similar to recent discussions that the PCC have had:
- Important to have countries and implementations represented on the PCC so that the product responds to on the ground needs
- Interested in having a roadmap that is grounded in what is feasible, what we know we can do now (i.e: in the next 3-6 months)
- TAC can help identify what modules are used in the ecosystem that can be leveraged by others
- TAC can determine the technical direction/approaches to invest in and what will help us get there (Microfrontends, being RESTful, moving away from server side, how OpenMRS can work at scale and how we get there, etc)
- TAC could come up with its own set of priorities for the next few months that can be shared with the PCC to inform a roadmap.
You can find the notes and a link to the recording here.
During last week’s PCC meeting, questions came up about Sync 2.0, FHIR, and OCL for OpenMRS: where do these currently stand? What is next? These seemed to the PCC like questions that fall under the TAC’s purview.
The TAC did not set a weekly time to meet and instead decided to circulate a Doodle poll to help arrive at a time. I encourage everyone who is interested in participating in these discussions to take a Doodle poll. Special note: the time options displayed on the Doodle poll should be: 4pm EAT | 1pm UTC | 9am EDT | 6am PDT or 5pm EAT | 1pm UTC | 10am EDT | 7am PDT.
With Daylight Savings Time starting again in a couple of weeks, I’ll set one time for the coming two weeks and we can confirm how to handle the DST change at the next meeting.