/
2020 April, 29 Tech Committee Meeting notes

2020 April, 29 Tech Committee Meeting notes

Owned by Josh Zamor (Deactivated)
Last updated: May 27, 2020

Date

 

7am PST / 4pm CEST

https://us02web.zoom.us/j/83933898664

Attendees


Discussion items

TimeItemWhoNotes
5mAgenda and action item review


Check-in on PCMT integrationJosh Zamor (Deactivated)
  • Status:
    • Fetching products
    • map into openlmis
    • todo:
      • dispensable (needs to be in PCMT)
      • pack rounding threshold and round to zero (need to pull in)
    • Default values?
      • Not needed - we need to add dispensable  in PCMT
    • Products pulled down, added to queue, sent to OpenLMIS Reference Data
    • Supports update & create
    • Even with UUID in PCMT, we still need to fetch the Orderable from OpenLMIS, so that we have the response body with the programs / program orderable
    • Next:
      • there's a queue, so an admin could see the json responses from openlmis referencedata  -  i.e. did the create/update work
  • How will we surface future capabilities out of this proof of concept?  e.g. see thread in Product Forum
    • How will we prioritize them?
      • Might need a kick-off meeting to discuss the use-cases as defined from PoC → v1 of the integration.
    • Raise them on the forum, discuss solutions to the point that we're ready to put them into the backlog.
      • Leading to discussion "in person", if there isn't consesus

2020 Q2 - what would we like to achieve, how would we like to lead itJosh Zamor (Deactivated)
  • Proof of Concept PCMT integration
  • Performance testing
    • Problem: in releasing we do performance testing, we deploy the (old) malawi dataset to a server, as well as testing on a local instance.  Usually we take measurements from response endpoints (browser inspector), what we want to measure is the user experience:  click a button (action) to it being ready for the next action.  Much of this is dependent on the user's machine, 30-40% could be a variance based on differences in tester + machine, effecting the overall results.
    • Solution:  Had some ideas, tried some in 3.9 testing.
    • Would like to improve the approach in Q2.
    • Would also like to extend the testing to more areas:  Stock Management.
    • Would like to ensure it's not an overburden on the release process as we do the above
  • SIGLUS
    • This is ending in May
    • Would like an update in our next call - overview would be helpful for what's coming back to core.
      • Extend invite for communication lines
  • Offline capabilities in Stock Management
    • What would we like to use or change in the technical piece from Requisition
    • Epic is created but needs to be refined.

Sprint Showcases
  • Showcasing via Zoom is not very smooth
    • laptop resets
    • microphone issues
  • Move to hangouts?
    • number of people for free version?  Usually less than 10 so it should work.  10 people is the max for free version.
    • works for daily standups (however SD has paid version - up to 200 users)
    • SD could setup the showcase meetings
    • Recording not supported out of the box?  Google Meet?  Come on Google...
    • GSuite should be able to be setup to record.

AOB

Notes



Action Items

Related content

OpenLMIS: the global initiative for powerful LMIS software