2018-05-15 Meeting notes

Date

15 May 2018

7am PST / 4pm CET

Meeting Link

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

Josh Zamor

Goals

See discussion items

Discussion items

Time	Item	Who	Notes
10m	Agenda and action item review		Open action items from last time: 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 https://openlmis.atlassian.net/wiki/spaces/OP/pages/214466562/DDD+and+package+name+improvements
	From Showcase on 09 May 2018 the following were brought up to discuss in TC or decide on the dev forum How to create tickets and address TechDebt identified by Craig Appl (Unlicensed) in Microservice API Analysis for Reporting Proposed Reporting Platform Repository Structure (this could be approved on the dev forum, but if not it should be officially approved by the TC meeting since it is blocking work) Reporting - Data ingestion and Analytic Data Schemas need to review together as a group and decide which API changes to make.	Craig Appl (Unlicensed) Clay Crosby (Unlicensed)
	Stock Reason tagging	Sebastian Brudziński, Chongsun Ahn (Unlicensed)	tags design concerns: OLMIS-4716 - Getting issue details... STATUS OLMIS-4717 - Getting issue details... STATUS which requisition template columns should expose tags? total received quantity total consumed quantity total losses/adjustments - do we need tags here or do we just take the sum of all other adjustments?
(for next time)	Reporting Repo Template	Craig Appl (Unlicensed)
(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 migration	Chongsun Ahn (Unlicensed)	Re-use run-sql Bespoke Template for cross-service migration / exemplar?
(for next time)	API Designs for Stock Based Requistions (or for review)	Sebastian Brudziński
(for next time)	Demo data - review new findings	Chongsun Ahn (Unlicensed)

Notes

API Reporting Review

Is it valuable to transition?
Who can
What skills are needed?
How to get the points in red out of wiki into work to be done?
- One is to big, how to right-size it
- Some might reflect that a more restful approach would be appropriate

Sebastian Brudziński Create a wiki page for the things in red and make a decision log - output will be recommended decision and priority to tech committee for final decision

Wiki page: APIs Tech Debt review
Ticket: OLMIS-4726 - Getting issue details... STATUS

Reporting Platform Repo Structure

Josh had lots of questions... Craig and Josh will meet: sidecar, structure of each image, is it generic, etc

Chongsun asked about generic-ness of Nifi repo. Could we have only one Nifi for multiple uses: reporting and demo data loading

Josh Zamor and Craig Appl (Unlicensed): Schedule this discussion. Add or have a second discussion w/ Chongsun Ahn (Unlicensed) if we think Nifi repo won't be generic enough for both Demo Data loading and Reporting.

Stock Reason Tagging

Does MJ have a concern about current tagging concept? Something in Logistimo about user and system tagging?

Josh Zamor and Mary Jo Kochendorfer (Deactivated) to schedule and meet

Technical concerns?

Sebastian Brudziński Josh Zamor Chongsun Ahn (Unlicensed) to schedule and meet