2020 May, 27 Tech Committee Meeting notes

Owned by Josh Zamor
Last updated: Jun 24, 2020
2 min read

Date

 

7am PST / 4pm CEST

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


Attendees


Discussion items

TimeItemWhoNotes
5mAgenda and action item review


Perfect ScrollbarKlaudia Pałkowska (Deactivated)
  • We had an issue with the npm project / github being removed, breaking the build
  • We're using a fork of an older version, we might be forking that again to make the style match
  • Is this the solution we want?  Will this break again?  What's the general strategy for npm project dependency removal (for the short term build break, for the long term maintenance)?
    • No perfect answer
      • One possible solution:  fork everything - this isn't reasonable
      • We're using a fork of Perfect Scrollbar that's now unmaintained - this was risky to start with!
        • One way to avoid the volatility is to use official packages
    • We're now using someone else's fork - still not the official package.
      • We're likely using this because it was the easiest way to make it work.
      • The new unofficial package will not be maintained, however he has promised that it won't go away.
    • How often do we think we've done this (i.e. using something that's unmaintained or unofficial)?
      • Maybe there was another package, name changed, links, etc
      • Is this related to some of the warnings we saw in GitHub? 
        • we think no, the warnings may be more security issues and upgrades available.
        • we have tickets/issues in the backlog that we need to get to

Stock Management Offline
  • Likely pushed back to Q3

or migrating to google hangout/meet/etc?
  • Worked OK
  • Lets try it in our June call?

SIGLUS OverviewChongsun Ahn (Unlicensed)
  • Updates on how the collaboration and how we've supported
  • Move back to June call
    • Note there is a demo of this in the PC right after this call.

Performance testing
  • Moving to June's call

Reporting stackOskar Hinc (Unlicensed)
  • Whole nother set of configuration (scripts, certs, docker files, credential files)
    • Suggestion: Create repo with all sample initial files in one place, with readme that says what env vars to setup.
    • deployment and credential repos are separate
    • Jenkins deployment puts it all together.

AOB

Notes



Action Items



OpenLMIS: the global initiative for powerful LMIS software