2018-12-11 TC Meeting notes

Date

11 Dec 2018

7am PST / 4pm CET

Time	Item	Who	Notes
5m	Agenda and action item review	Josh
	Discourse checkup	Wesley Brown	Checkin on if there's questions on use? Quick demo
?	Follow up on developer experience	Josh Zamor	https://forum.openlmis.org/t/improving-the-developer-experience/850 What's next?
Did this, any questions?	DHIS2 followup on how (keeping this on the agenda to discuss the plan prior to implementation, however implementation isn't pressing on this just yet)	Josh Zamor	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
(next time)	Database timestamp migration / testing	Sebastian Brudziński	We'll go over problem statement and some solutions as well (we ran into this before so we'll summarize those notes) Timestamp in Requisition service on database migration Was discovered on perftest Migration testing If migration is added with timestamp < other existing migration, than migration added will be ignored.
(next time)	Profiling		Focus on backend Bring up frontend if possible

On forum.openlmis.org
Transitioned away from Google Groups, if you post there, it won't be followed.
If you're not getting emails:
- Check your Profile (Click on Your image / avatar on forum.openlmis.org, and then the small gear icon)
  - It defaults to not sending you an email if you have it open in the background. Change this at Emails → "Send me emails even when I'm active on the site".
  - Get emails for everything by activating Mailing List Mode. Emails → Enable Mailing List Mode
- Follow categories (e.g. Technical Committee), by going to the home screen, then the category, clicking on the "circle" icon in the upper right and selecting a different mode. Default is Normal which only notifies you if you're mentioned.

Everyone should take last 20+ minutes from ending call early to reply to this thread:
- https://forum.openlmis.org/t/improving-the-developer-experience/850
The UI workflow is different than the backend
- That friction requires going to READMEs (may be out of date), and learning how the other side works.