January 15, 2019

Introductions and Call opening

• Notes from December Governance call

December Notes

Update on Sustainability Work and upcoming meeting

(5 min)

Resonance Team 

James Bernard

Rebecca Alban (Unlicensed) to start

Ideas from all

Community Goals for 2019

1) To provide a relevant and high-quality open-source logistics management information system to facilitate prioritized workflows and inventory management in LMIC. The software must be configurable, interoperable and easy to use so that technology vendors and resources in LMICs can deploy and support the system.

• We want to support more v3 implementations- in order to unlock and support the implementer community OpenLMIS needs to be: interoperable, configurable, easy to set up (e.g. Instant OpenHIE https://proposals.digitalsquare.io/71)
  • Increased focus on current implementations rather than getting new
• Deeper discussion about 'shadow' migration approach (gradual) versus the 'big bang' approach for upgrades (to be used in Tanzania)
• Create more linkages to other supply chain systems and software (e.g. Product Registry, Data Collection & Analysis platform, Decision Support Services)

By the end of this year we might have 3,4,5 different users of v3. These will have competing priorities.

Quality/performance is a hard metric; how do we measure it? So far test coverage, unit tests, number of bugs, have been our metrics for software quality. Feedback from implementer community is important- re: deployment, number of bugs, how quickly we get through them, etc.

2) To build or strengthen the implementer community and capacity of deploying OpenLMIS by strengthening community mechanisms for engagement, communication, and knowledge exchange.

• Increase community engagement, particularly at country-level. This includes current implementers, developers, partners.
• Empower Trusted Partners to promote OpenLMIS at global level (country visits, targeted demos, etc.)
• Create a shared understanding of how to talk about different OpenLMIS versions (ie: which donors/implementers are associated with each, attribute experience/learnings to each unique version, etc.)
• Continue to foster relationships with other Global goods and open source communities

Other thoughts re: goals for 2019

• Support/facilitate and respond to sustainability work by Resonance
• OTHER? 

Please reach out to Rebecca Alban (Unlicensed) with other thoughts or suggestions for what we should be focusing on in 2019

Mary Jo Kochendorfer (Deactivated)

Carl Leitner 

Post: https://forum.openlmis.org/t/a-time-for-transition/4910

Mary Jo is taking another role at DIAL and leaving her role as OpenLMIS Product Manager Brian Taliesin to proviide support to support this transition. Details are in Discourse forum post

Some details are still being resolved re: roles and responsibilities

Thank you Mary Jo!

Many people expressed their thanks. "Mary Jo has been the personification of OpenLMIS" for the last few years." We wish you the very best at DIAL!

Jan 29th in DC can also be used to talk about transition plans

OpenLMIS Representation in the Digital Health Atlas

(skipped)

https://digitalhealthatlas.org/en/-/   There is a map that stakeholders can scan to see what digital health technologies are being used in each country.

Linkages to the Global Good Guide Book (Carl Leitner to describe)

Consensus needed on who the contact/focal person for each implementation should be. 

How is it being used? Donors want to know a foot print of a solution (how scaled is it).  Additionally if anyone wants to learn more about the solution, they will want a contact which can provide that information.

Option 1) Each implementing organization is listed as the contact. If we have each implementing organization serve as the point person, we want a way to say they are all OpenLMIS.

Option 2) We list info@openlmis.org as the contact, so inquiries come to the Community Manager. If we have info@openlmis.org be the point for each implementation, we will need a way to keep it updated (right now we don’t know all the information about the scale of the solution in each country.

VOTE

Update on GAVI RFI

RFI Visit to Global Fund

DIAL and Software Freedom Conservancy

(skipped)

 1) the potential need to trademark the OpenLMIS Trusted Partner logo.   What types of services SFC can provide in this regard and how can DIAL can help facilitate?  

2)  pros and cons about moving the copyright from Village Reach to a third party such as SFC.

Conferences and Meetings

Conferences provide the community the opportunity for OpenLMIS members to speak or represent the OpenLMIS software and community in public forum.

Opportunities Roundtable

Definitions to use shared terminology:

• Implementation opportunity: an opportunity for an implementation or deployment of the OpenLMIS software.  Usually this is done at a national or sub-national level within a ministry of health. This can also include feature work which would be done within the implementation and contributed back to the global codebase.
• Community opportunity: a funding opportunity to support an organization or individual to work directly on the global codebase and/or administrate the community processes. This may include funding specific features on the community roadmap.

• This Trello table is being updated on an ongoing basis; to help the core team to track and manage implementation opportunities, but also provides a detailed snapshot of the scope and status of current implementation opportunities for stakeholders.
• Do we add things like this to the Trello table or develop a different way to track:
  • Machine Learning assets with Google
  • Data Collection and Analysis https://wiki.digitalsquare.io/index.php/Data_Collection_and_Analysis 

What is our strategy for interoperability?

list some interoperability use cases on a wiki page

strategy for fostering connections with other orgs: for example: TransIT

link to documentation in 3.5 about interoperability