2020-08-06: Technical Action Committee (TAC)

Our next TAC meeting is this Friday. Agenda and notes here.

What we cover: These meetings are a good place to join if you’re interested in having a finger-on-the-pulse of some of the high-level technical work going on week-to-week! :slight_smile: Our goal is not to dive into each topic in detail, but to make sure the overall direction and any needed endorsements are clear. Open to anyone in the community who is interested in and has an opinion about the technical direction of OpenMRS.

When: Friday at 7:30pm IST | 5pm Nairobi | 4pm Cape Town | 2pm UTC | 10am EST | 7am PST.

Where: https://iu.zoom.us/j/93941698390

Brief Updates

  • Re-framing the TAC time & proposal to reduce to q 2 weeks

  • Squad Showcase plan

  • Upcoming releases

  • Jira updates - please help us by reviewing tickets you’ve created, or tickets assigned to you in RA or TRUNK. (Search query that works for anyone here!)

Main Topics

  • DHIS2 integration: direction we’re heading
  • (15 mins) Module Maintenance Plan (@bistenes): Team-based approach proposal
  • (20 mins) Module Release Standards (@ibacher)
    • range of new technologies that are getting close® to releases, e.g., the FHIR module, the MF, the OCL squad. What does it mean that a module is released (especially if we intend it to be used)? What practices / model should we have in place to ensure that it works?

@burke @mksd @ibacher @dkayiwa @wanyee @janflowers @ssmusoke @jdick @aojwang @morrisng @mogoodrich @ggomez @bashir @ball @ccwhite23 @akanter @akimaina @herbert24 @bistenes @tendomart @gcliff @mozzy @sharif @gcliff @christine @k.joseph