2017-06-13 Meeting notes
Date
Jun 13, 2017
7am PDT
Meeting Link
https://www.uberconference.com/villagereach-isg
Optional dial in:
Dial in: 401-283-5773
PIN: 66343
Attendees
@Josh Zamor (Deactivated)
@Ben Leibert
@Brandon Bowersox-Johnson
@Paweł Gesek
@Sebastian Brudziński
@Nikodem Graczewski (Unlicensed)
@Nick Reid (Deactivated)
@Paweł Albecki (Deactivated)
@Mateusz Kwiatkowski
@Mary Jo Kochendorfer (Deactivated)
@Tenly Snow (Deactivated)
Bonface Ochieng
Goals
Review our adoption ofTransifex with an eye on our recommendation on usage in implementations:
gate keeper?
cost?
community participation?
limits (user accounts, projects, strings)
Adopt a Code of Conduct
Discuss current UI extensibility maintainability / goals?
Setup a in-depth conversation on performance with regards to large reference data lists: i.e. Orderables
Review Action items out of May 30 2017 meeting
Discussion items
Time | Item | Who | Notes |
|---|---|---|---|
5m | Agenda review | TBD |
|
15m | Code of Conduct | @Brandon Bowersox-Johnson |
|
20m | UI extension maintainability | cancelled for this call, will revisit | |
10m | Performance - large reference data lists | @Josh Zamor (Deactivated) | Setup a call for tackling our Reference Data Performance question(s):
Could we schedule this as early as Wednesday? |
10m | Action item review |
|
|
@Josh Zamor — I'd like to add an agenda item to either this meeting or the next (this one looks kinda full)
Topic: Maintaining UI modifications
The issue here is that every time an implementer overrides an OpenLMIS-UI file, there is almost an unknown amount of tech debt the implementer is taking on — as there is not a clear way to tell if a new version of the underlying modules have made changes to these files.
The original goal of this architecture was to allow easy ways for an implementer to completely remove and change the behavior of OpenLMIS-UI components and or pages. The original unit tests for a component are unable to overridden in the same manner, which maintains the component's contract with other pieces of OpenLMIS.
As the MW implementation has progressed, there have been issues updating code — and making sure behavior has not been irreversibly changed.
There will probably be more to discuss based on the dev list email...