Date

26 Jun 2018

7am PST / 4pm CET

Meeting Link

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/737202874

Or iPhone one-tap :
US: +16699006833,,737202874# or +14086380968,,737202874#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 408 638 0968 or +1 646 876 9923
Meeting ID: 737 202 874
International numbers available: https://zoom.us/zoomconference?m=F0kj5u6u0wFxr7Xfz5NKZxl0xyLhuTPF

Attendees

Goals

See discussion items

Discussion items

Time	Item	Who	Notes
10m	Agenda and action item review
1-5min	APIs Tech Debt review	Łukasz Lewczyński (Deactivated)	Summarize future actions
3min	Mobile Strategy Discussion Review	Craig Appl (Unlicensed)
20min	Feature flags	Mateusz Kwiatkowski	show example how to use them on UI and backend ask about are there any potential improvements/changes
20min	Locale consistency	Chongsun Ahn (Unlicensed)	Summarize work that needs to be done

Notes

APIs tech debt review

update sent to mailing list on tickets that we want to create
feedback provided by Chongsun
list of tickets is pretty much on the mailing list - Łukasz Lewczyński (Deactivated)

Mobile Strategy Discussion Review

Reviewed multiple open source mobile tools over the last 2 months
Continue building Stock Mgmt within OpenSRP after review as lowest risk
Stock events are generated in the OpenSRP Android client, pushed to OpenSRP server and Nifi performs the integration with OpenLMIS. There is a one-to-one mapping of stock events between OpenSRP and OpenLMIS where all stock events generated in OpenSRP will go to OpenLMIS.
Mobile Stock Management Integration Design Spec
OpenSRP and OpenLMIS Integration Path Forward

Feature flags

went with the easiest approach
feature flags are configured via env variables
UI feature flag example implemented for batch approval screen (enabling/disabling availability of the batch approve)
Backend feature flag example implemented fix to filter search for for facilities by geo zone
The UI example is long-lived feature flag that should be documented; the backend one is short-lived feature flag that will be removed
potential problem - SQL migrations (they are not conditional at the moment); we agreed to leave it for now and just revert the migration file for release in case it's needed
Feature Flags Read the docs

Locale consistency

created epic and several tickets there to make locale consistent
the focus of the epic is on the consistency for the end-user
two main parts were we use/need locale and need to handle it: UI and Jasper reports
start with the tickets to add locale/currency/date format to the system settings and make sure services are using it
for future iterations: allow users to specify the timezone they want to display times in (the field already exists in User resource)

Action items

Łukasz Lewczyński (Deactivated) to create tickets after APIs tech debt review
Mateusz Kwiatkowski to create a ticket for documenting long-lived feature flags
Chongsun Ahn (Unlicensed) to follow up on the dev forum about one resource vs several resources for configuring locale/date format/number etc.
Chongsun Ahn (Unlicensed) to consult with Mary Jo on whether the epic should be considered tech debt

Browser not supported