February 9, 2021-agenda

Introductions and Call opening (5 min)

• Notes from Jan Governance call

January Notes

Welcome

Review agenda for this call

COVID 19 Edition Survey for Countries

(3 min)

We are depending on our network of partners to help circulate a short survey, across all the countries that we work in, to help us paint an accurate picture of their digital tool needs to support COVID vaccine distribution. This information will help us to adapt OpenLMIS accordingly to become a key tool in the COVID19 vaccination efforts.

The OpenLMIS for COVID- Country Survey is in google forms, here is the link: https://forms.gle/da9zafYpefu1rYMU7

So far, 12 responses mostly from CHAI countries. Only CHAI and VR have signed up for circulating this in their countries. We ask for all partners to do so via this sign up sheet:

https://docs.google.com/spreadsheets/d/1F5CPe7LjkSsSHlCZu_eTpd221D_gctP0TqEYJSMvdiY/edit#gid=0

UNDP LTA opportunity: update

(2 min)

Submitted! Thanks for all who are part of the consortium for their cooperation (VR, SolDevelo, JSI, BAO, CHAI, PATH). This is an important opportunity for the community, to be able to get UNDP funded country-specific contracts over the next 3-5 years. 

Next step is review from UNDP and hopefully the award of a LTA from UNDP to OpenLMIS (via VillageReach as contracting mechanism).

Update on Transition Activities, Next steps

(15-20 minutes)

Rebecca-

• Role of partners re: in country communications
• Request partner contact lists for in country stakeholder engagement (MoH, in country partners stakeholders to circulate memo to)
• Review of draft key messages (if time allows) 

Originally the Stewards team suggested a CAA mechanism (in the IP Summary we shared).

Since this was flagged at our last Working Group meeting, JSI and VillageReach have been meeting to discuss this. We have agreed in principle to a CLA mechanism--where JSI and VillageReach would each hold copyright, but would sign a CLA to formalize and document contributions to the open source project. 

Recommendation for the OpenLMIS Community is that we recommend contributors sign a CAA to give copyright of their contributions, but we would also provide an alternative CLA option.

The downside of CLA for the community, is that the more organizations who hold some of the copyright, the harder it is to get all those parties to agree to transfer it to a neutral third party fiscal sponsor, or to agree to change the license (if we ever wanted to), or to go to court if we ever needed to fight an infringement claim, for example. So CAA is still cleaner and better for the community as the preferred option.

Questions: 

• Are there any other Partners on this call who have a concern with the CAA recommended option? (Who would want the rights and obligations of a CLA instead?)
• Does anyone have concerns if we revise the IP Summary document to establish a preferred CAA as well as an alternative CLA option for the community contribution guidelines going forward? We would bring this policy written up to the Governance Committee next.

Identifying and establishing a neutral third party is something that will happen after the Handover Partnership begins, and it may take 1-2 years. In brief, no existing fiscal sponsor checks all the boxes of the criteria that make them ideal for OpenLMIS (or for other Global Goods in our space).

Questions: 

• How would the partners like to be involved in the selection and choice of a future fiscal sponsor/neutral third party?

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 documentation

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.

Community Opportunities:

• New Trello table! Similar to the above table, this tool is being used by the stewards to track our exploring of new product opportunities and partnerships

Study Tours:

• Study Tours wiki page tracks applications received, study tours completed, and other key milestones related to OpenLMIS Study Tours (this activity is no longer active due to COVID-19)