/
2019-02-05 TC Meeting notes

2019-02-05 TC Meeting notes

Mar 05, 2019

    Date

    Feb 5, 2019

    7am PST / 4pm CET

    Meeting Link

    https://zoom.us/j/211353423

    Attendees

    • Sebastian Brudziński

    • Elias Muluneh

    • Nikodem Graczewski (Unlicensed)

    • Łukasz Lewczyński (Deactivated)

    • Mateusz Kwiatkowski

    • Paulina Buzderewicz

    • Craig Appl (Unlicensed)

    • Wesley Brown (Unlicensed)

    • Chongsun Ahn (Unlicensed)

     

    Discussion items

    Time

    Item

    Who

    Notes

    Time

    Item

    Who

    Notes

    5m

    Agenda and action item review

    Josh

     

    15m

    Feature Flags

    Josh Zamor (Deactivated)

    • 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 (Unlicensed)

     

    5m

    DHIS2 Update

    Craig Appl (Unlicensed) / Josh Zamor (Deactivated)

    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

    Notes

     

    Feature Flags

    • 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.

     

    Build Failures

     

    • 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?

     

    DHIS2

    • above in notes

     

    Rapid Pro PoC Update

     

    • 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

    Multiple checklists plugin in Jira

     

    • SolDevelo has developed an add-in to Jira, checklists inside tickets

    • Has been added to our OpenLMIS Jira

    • Just go try it in Jira

     

    Action Items

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

      OpenLMIS: the global initiative for powerful LMIS software