Voting members reviewed 4 proposals most ranked Resonance as their first choice, Lenati was second:
Re: Resonance: what is their experience working with Open Source material? and do they understand the relevant business models? Timeframe was a concern-could some of the things be accelerated? They have a lot of private sector supply chain engagement, could incorporate new business models
Re: Lenati: Seem to have a bias toward commercialization–what would this do to our services for MoHs? Do they understand the context in which we are working re: donor environment? Their framework is good and the stepwise process they use
Next steps: We will reach out to both vendors with the above questions and ask them to respond by COB Monday. Rebecca Alban to schedule 30 minute meeting next Thursday for committee to vote. BBMGF contract with vendor to be finalized by late September, with the goal to begin work in early October
Next Step- Rebecca Alban to set up a meeting next week to allow folks to discuss priorities and vote; If anyone cannot attend this meeting and would like to vote, please indicate this to Rebecca so that we ensure all voices are heard
Conferences and Meetings
Conferences provide the community the opportunity for OpenLMIS members to speak or represent the OpenLMIS software and community in public forum.
Michael has accepted an invitation to share from his experience about how to cultivate open source communities. This came out of the suggestion to move from Google Groups to Discourse but does not need to be limited to that topic. If you have questions about how we can continue to grow a health open source community, Michael is a great person to ask.
Regarding Discourse: Are we in agreement to look at options for a shift to Discourse?
Highlight the current gaps:
Does not fill the gap between real time communication (Slack) and email.
Ends up being another funnel into our inboxes
Lacks advanced forum features like categories, user/community management, user individualization/progression, etc
Proposal for Discourse (based on feedback from Craig):
Discourse would be the main entry point into the OpenLMIS community for new members
The system should require an account but one that can be freely made by the user. User categorization can be used to denote users with more experience within the community (seeOpenMRS Developer Stages)
I think that Discourse would incorporate:
Google Groups discussions
Public project-related email
Some of what currently goes into Slack
Some the discussions currently occurring within the wiki
If yes, Highlight Options for implementations and LOE/cost implications
Next Steps; members review the notes and be prepared to make a decision about Discourse at next governance meeting. Wes to prepare information related to LOE and cost implications
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.
Community funding opportunities:
Country Implementation Opportunities Updates:
CHAI Cameroon proposal: working with Village Reach and will move forward with a proposal next month.
Benin- have requested a demo environment so that they can showcase features to stakeholders. If an implementation opportunity arises, we will notify trusted partners. Scope and funding availability is still unclear
Cote d' Ivoire- Community is making a presentation/demo to the MoH TWG tomorrow. JSI, Softworks and VR have expressed varying levels of interest and have requested an RFP from the MoH to clarify the scope