2018-04-17 Meeting notes

Owned by Josh Zamor
Last updated: May 21, 2018 by Sebastian Brudziński
3 min read

Date

7am PST / 4pm CET


Note we're using Zoom now:


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

TimeItemWhoNotes
10mAgenda and action item reviewJosh Zamor

Open Action item review from https://openlmis.atlassian.net/wiki/x/vAAND

Open action items from last time:

  • Chongsun Ahn (Unlicensed) to add docs on http caching / dtos
  • Paweł Albecki (Deactivated):  take the feedback from the DDD and package name improvements and show through a diagram and/or use of the example service what it'd look like given that feedback
  • To the group:   bring up what you'd like to see as part of the technical mobile strategy in the dev forum (Product Committee may look at some of this feedback)
  • Sebastian Brudziński:  Start a discussion on: 
    • Do we intend to move performance data into demo data - do we want to do that?  It's separate data sets, we think might like to combine for maintenance and consistency)
  • Chongsun Ahn (Unlicensed):  Grab one of the options on migration performance and start a dev forum post
  • Josh Zamor and Chongsun Ahn (Unlicensed):  write a ticket to investigate the CCE migration test issue
  • Josh Zamor to followup on the db migration test port - close up 8500 in ref distro before the release

Tech DebtJosh Zamor
  • Go over proposed process
  • Look at items in sprint
  • Schedule grooming call (or Slack?)

Update on the Architecture epicsJosh Zamor
  • Go over the Architecture component (it was Platform)
  • Purpose - to communicate architectural priorities so we all have a sense of where this is
  • Look at the top epics, talk through how we're going to start tackling them.
  • Do any of them get someone jazzed to help in filling out work tickets

Update on branch for releaseJakub Kondrat
10mApproach on retrieving data from SM for Stock Based requisitionsSebastian Brudziński
  • Follow up on 2018-04-12 Tags and Stock-Based Requisitions Epics Introduction Meeting in preparations for OLMIS-3850 - Getting issue details... STATUS
  • How should we get data for Stock Based requisitions?
    • Send all StockCardLineItems for the whole period for all products (potentially a lot of data) and then extract what's needed in requisition service and do calculations
      • Send Orderable
      • Send processing period
      • Send tag(s) - may not need this
      • Receive line items
    • New resource in StockMgmt (extended SrockCardsSummaries-like one) - all calculations in SM, only send aggregated numbers
      • Send Orderable
      • Send processing period
      • Send tag(s)
      • Send ?
      • Receive an aggregate number
(for next time)UI - Table approach after OLMIS-4541 - Getting issue details... STATUS Nikodem Graczewski (Unlicensed)
  • As discussed in Slack I left a spot for this Nikodem Graczewski (Unlicensed) if this meeting is the appropriate time.  Please update with details if it is, or let us know if we should move it back one.
(for next time)Cross-service migrationChongsun Ahn (Unlicensed)
  • Re-use run-sql
  • Bespoke
  • Template for cross-service migration / exemplar?

Notes


Jenkinsfile - branch for release

  • How do we automate the performance tests?
  • Translations
    • Transifex does have a branch specifier that tags the source with the branch name
      • so on rel-3.2.0 the source file becomes messages_en-rel-3.2.0 or something similar
      • translations on that source then occur
      • what does the workflow look like for the translator?
    • On the other hand, trunk based development may not really require this.  The messages in the release branch should be those in master.  What we wouldn't have is a view in TX that shows coverage of translation for a particular release, however we would have it up-to trunk, which should be a close proxy.
  • Should docker images tagged with build number be sent to DockerHub?
    • It would be good if we did if that meant we could parallelize stages:  e.g. as soon as an image is built, push it to docker hub so that another build server could start running contract tests.


Stock based requisitions

  • Comes down to the two questions outlined in agenda.
  • It appears that the two approaches are largely the same in terms of query parameters, only in what's passed back and where the responsibility lies.
  • We'll have a follow-on conversation before implementation to discuss details.


Action Items


OpenLMIS: the global initiative for powerful LMIS software