Call Information

Webex Link: https://meetings.webex.com/collabs/#/meetings/detail?uuid=M299H1X42RL8F1ABXL3LOKN9TN-3O29&rnd=371900.06805

Meeting Number: 192 173 465

Host Key: 352864

Audio Connection:  +1-415-655-0001 

AGENDA:

ItemTimeLead

Software Development Update

20 min

Mary Jo Kochendorfer (Deactivated)

GS1 Support and Product Model

Introduction to Medical Commodities: OpenLMIS Model for GS1. The model has been updated for OpenLMIS 3 based on the conversations between Josh, Mike and others (USAID BI&A, Intellicog and GS1 consultants).

  • Data Model

  • Malaria Example

  • Review other key sections

  • Q & A


20 min

Brandon Bowersox-Johnson

Versioning Discussion

OpenLMIS 3 is adopting a periodic release schedule. After the 3.0 release, the community can expect:

  • Patch releases with bug fixes will come out on an as-needed schedule (3.0.1, 3.0.2, etc);
  • Minor releases with new functionality will come out quarterly and will be backwards-compatible (3.1, 3.2, 3.3, etc);
  • Major releases would be for non-backwards-compatible API changes. None is planned at this time (4.0 and above).

These release numbers use a standard called Semantic Versioning.

The goal of the 3.0 re-architecture is to enable multiple country implementations to share a common code base and derive "shared value". For example, Country A's implementation might fix a bug or add a new report, they would contribute that code to the open source project, and Country B could use it; and Country B could contribute something that Country A could use. For this to succeed, a few things must happen:

  • Two or more countries adopt the 3.0 series. (In Progress first in Malawi; second country TBD)
  • Each country be ready to share any bug fixes or improvements with the open source community.
    • Core team be available to review pull requests.
  • Each country ask the core team if they need extension points to customize OpenLMIS for country-specific needs.
    • Core team be ready to quickly add those extension points.
  • Each county implementation upgrade to latest versions (3.0.1, 3.0.2, 3.1, 3.2, etc) as they become available.

The first bullet point is already underway. The remaining bullet points need to be established with each country implementation. Each of these pieces is critical to establish a strong global community of shared benefit for all participants.

We want to make sure everyone in the OpenLMIS community understands this and has the information they need to advocate for this.

Slides: https://docs.google.com/presentation/d/1k4oecJ2vgsxXvv5czJAIaHiNjad8aa3M8JzxtaZBpKg/edit?usp=sharing


20 minBrandon Bowersox-Johnson

Stock Management

  • #25.3
  • #29
Not enough time, Will follow up on the listserv

Shiyu Jin (Deactivated)

3.1 Scope and Priorities

  • Need to begin reviewing and prioritizing. Governance Committee will want to review and sign off.
  • Discuss an approach to voting and giving community members a way to note down preferences.
Not enough time, Will follow up on the listservMary Jo Kochendorfer (Deactivated)

Update on requests from the Governance Committee

  • Functional spec toolkit is up on Confluence - Functional Specification Template (Vaccine work is exploring more enhanced features within Confluence, more to come soon)
  • Publish current implementation's roadmaps publicly
    • Update from Ashraf (Cote d'Ivoire, Zambia, Tanzania)
    • Update from Mary Jo (Benin and Mozambique)
  • Merging roadmaps to see across all implementations and 3.x
    • Blocked by first step
Not enough time, Will follow up on the listserv

Mary Jo Kochendorfer (Deactivated) and Ashraf Islam (Unlicensed)

3.0 Website Refresh

  • Content review needs to be completed by Feb 17th
Reminder


ACTION ITEMS:

ATTENDANCE:

NOTES: 

Mary Jo

Brandon


Versioning

There wasn't time for stock management so information and questions will be circulated to the group via the listserv.


RECORDING


ADDITIONAL READING: