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.
The team is organizing/prioritizing the bugs found out during the UAT that took place last week;
Ashraf and Shiyu: Wants to help out on the blog post/release notes of the release of OpenLMIS 3.0;
Mary Jo: To follow up with Tenly on the production/translation of the blog in Portuguese
Mary Jo: should we do a webcast/live demo with OpenLMIS 3.0? Later check - probably produce one in Portuguese;
Raised that the committee will need to figure out a way to voice/vote priorities for the 3.1 release. More to come on this and please weigh in on the listserv on your thoughts/ideas to do this effectively.
Changes in ver. 3
Orderable = Product (Ver 1 and 2)
Trade item = manufacturer or brand owner and are typically identified by that manufacturer or brand outside of OpenLMIS;
Commodity types = classifications of commodities, e.g., UNSPSC
Review the presentation in the agenda for details on the conversation.
Brian highlighted that each service will have a version number.
The presentation describes the version of the reference distribution (overall product). Each service will have a version number and can have its own minor releases. The key version for our partners to keep in mind is the one for the reference distribution.
There wasn't time for stock management so information and questions will be circulated to the group via the listserv.
OpenLMIS: the global initiative for powerful LMIS software