1. Design the Integration
2. Build a Rough Proof-of-Concept
Outcome: Show a rough proof-of-concept and take screenshots or video so we can share our progress. The code might not be committed back to our main open source project repos. The main result is that we will learn what is easy, what is hard, and inform our next steps for ultimately delivering a working integration.
3. Create a Joint Task List
10:00am Introductions
Review Goals
Gain understanding of how ODK2 works / high-level architecture diagram of ODK2*
Discuss micro-service integration (Docker, LDAP and OAuth2, etc)
Plan for Web APIs; identify the interface between the two systems
Achieve Goal #1-Design the Integration (see above)
~5:00pm End-of-Day Wrap-Up
*It’s more important that the OpenLMIS team learn about ODK2, and not as important that the ODK team learn how OpenLMIS works. From Waylon’s perspective, OpenLMIS is a generic consumer and they don’t need a big presentation about how OpenLMIS works.
See Notes/Outcomes
Link https://www.uberconference.com/villagereach-isg (or dial by phone at 401-283-5773, PIN 66343)
This document is public, and anyone can register for an account here to the OpenLMIS wiki by clicking Sign Up at the top right and then contacting Tenly Snow (Deactivated) or Mary Jo Kochendorfer (Deactivated) for full write access after you have signed up.