2019-02-05 TC Meeting notes

Date

05 Feb 2019

7am PST / 4pm CET

Time	Item	Who	Notes
5m	Agenda and action item review	Josh
15m	Feature Flags	Josh Zamor	Team MtG, what critical challenges have we encountered with Feature Flags? Are feature flags ready to be used with Team Parrot? (does team parrot have significant work planned that'd fit their use?)
10m	Build failures	All, Wesley Brown
5m	DHIS2 Update	Craig Appl (Unlicensed) / Josh Zamor	Update on DHIS2 scope decision: https://openlmis.atlassian.net/wiki/x/zIDfHQ Progress: Scope #1, compute the indicators and make them available, is in progress. Scope #2, transport the indicators to DHIS2, is scheduled for 3.6 but reduced in priority to give more space for reporting stack robustness (product ready). Design is proceeding: https://openlmis.atlassian.net/wiki/x/NIEyGw Question: which DHIS2 version(s) should we support? (TZ is currently on 2.30, latest is 2.32). 2.29 supposed to stop breaking API...
10m	RapidPro PoC	Nikodem Graczewski (Unlicensed)
15m	Review Multiple Checklists for Jira (low priority)	Sebastian Brudziński	Multiple Checklists for Jira were added to OpenLMIS instance https://marketplace.atlassian.com/apps/1220026/multiple-checklists-for-jira Demo and talk how we can leverage them to improve our workflows

No critical challenges
Other teams could pick this up.
We don't use them in the UI yet, so not ready there.
Team Parrot is working on functional testing, doesn't apply, however for performance improvements this might be an area they'd apply.

A lot of failures in build channel in slack
What can we do to eliminate these failures
There are multiple days, full of failures, with no comments - do we have thoughts?
- Still have a lot of builds / tests that take a lot of time to run - test internal to service passes, contract and inter-service tests might fail
- If a test fails, should it keep re-notifying if subsequent runs also fail?

Choose RapidPro to give a layer of abstraction on top of Kannel, Twilio, Nexmo, etc
PoC page using TextIt (hosted RapidPro) and Twilio: https://openlmis.atlassian.net/wiki/x/c4D3HQ
Some notable restrictions on sending in batches, configuration using different endpoints, performance notes, etc
Recommendation is to use the broadcasts endpoint for 3.6 requirements, however for future requirements we might want to switch to flow_starts, however it should be noted that there'd configuration needed.
- At the least would be knowing the flow id.
- Could also include passing through a map of values to fill in a message template in the flow

Josh Zamor followup with Team Parrot on feature flags in performance improvements
Josh Zamor schedule a call on level setting on build failures (put out open invite), bring up notifications