2018-09-19 TC Meeting notes

Date

19 Sep 2018

7am PST / 4pm CET

Meeting Link

http://uberconference.com/villagereach-isg

Attendees

Goals

Items from last call?
Orderable versioning
Build failures
Discouse

Discussion items

Time	Item	Who	Notes
5m	Agenda and action item review	Josh
	What can we do to limit the number of failures reported on #build?	Sebastian Brudziński	A single commit triggers various builds (build + ERD + contract tests + Sonar + deploy + ...) Devs usually don't check whether all the steps are passing (like contract tests or Sonar) - why? Probably too time consuming... Are we concerned with the amount of failures we are seeing at #build? Anything we can improve? Stop forwarding some failures to #build? Only notify Slack if build was not fixed after 12h? 24h? (LoE?)
	Discourse discussion	Wesley Brown
(next time)	Orderable versioning	Chongsun Ahn (Unlicensed)	Continue the show and tell on the how
(next time)	Feature flags	Josh Zamor and Sebastian Brudziński and Mateusz Kwiatkowski	Do we think this is mature yet? Can it be used to make quick, unplanned, releases of a service? Do we all understand it?
(next time)	Followup on audit log initializer		We completed OLMIS-3078 - Getting issue details... STATUS which will help production data sets, however for demo data we would still iterate over all the demo data records on the first start as they don't have snapshots yet. Is a slow startup still / more an issue? With the increased size of the demo data that we're adding, and thoughts to have millions of records, do we think we have an issue?
(next time)	DHIS2 followup on how		There are meeting notes from https://openlmis.atlassian.net/wiki/x/LYDSGQ Still items being figured out Plan is to start this after the mCSD / FHIR work

Notes

Build Channel Failures

Not in dev env: e.g. sonar coverage in IDE
A few ideas:
- Notify slack only after some time (end of day, 12h, 24h, etc...)
- Stop forwarding some notifications to #build - notify a single developer, create channels for each service?
- Can we shift left:
  - migration tests OLMIS-4343 - Getting issue details... STATUS
  - performance tests
- A Test that should almost never fail: ERD, contract test
- Team city
  - can send up local changes, bypassing vcs, to be built and tested

Discourse

Google groups posts: https://groups.google.com/forum/#!topic/openlmis-dev/1NbN5abTB_k
We'll be migrating users and historical posts into Discourse
- Company would be hosting it for us - no maintenance for us
We looked at talk.openmrs.org
We'd need to discuss categories and tags, and how we'd need to come up with a good set of categories ahead of time, e.g. https://talk.openmrs.org/categories

Action Items

Wesley Brown to look at team city
Wesley Brown post on the dev forum about our move to Discourse
Josh Zamor to schedule a call with Sebastian Brudziński and Mateusz Kwiatkowski on feature flags