2017-11-28 Meeting notes
Date
Nov 28, 2017
7am PST / 4pm CET
Meeting Link
Toll: +1-415-655-0001
Number: 199 948 686
Attendees
@Mateusz Kwiatkowski
@Ben Leibert
@Elias Muluneh
@Nick Reid (Deactivated)
@Nikodem Graczewski (Unlicensed)
@Klaudia Pałkowska (Deactivated)
@Paweł Albecki (Deactivated)
@Sebastian Brudziński
@Josh Zamor (Deactivated)
@Paweł Gesek
@Brandon Bowersox-Johnson
Miss anyone?
Goals
Feedback on Demo-data loading approaches
Review error message handling from dev forum
Discussion items
Time | Item | Who | Notes |
|---|---|---|---|
5m | Action Item review from last time | @Josh Zamor (Deactivated) |
|
20m | REST issues | @Mateusz Kwiatkowski |
|
10m | UI v7 Architecture Q&A | @Nick Reid (Deactivated) |
|
| If time: expanded REST pattern | @Sebastian Brudziński |
|
Notes
REST Issues
See dev forum post: https://groups.google.com/forum/#!topic/openlmis-dev/p5YqKKcor7I
Great discussion on the article about REST and getting away from CRUD.
Next steps:
@Mateusz Kwiatkowski has created action page: https://openlmis.atlassian.net/wiki/x/AYCLC
create Jira tickets for bullet points #1-5 and #7 (6 total)
UI v7 Architecture
See link: https://openlmis.atlassian.net/wiki/x/aIBQBw
Questions:
When?
Piecemeal
likely see it in newer local fill features
How does this fit in with Angular terms / architecture
Would be useful to have a graphic
Would be helpful to start sections of with more of a why
Are we creating custom framework / reinventing the wheel?
Not so much, we're moving toward more structured code
How much do we save going this route rather than a re-write?
Moving to business logic in pure javascript
Aiming for longevity
Doesn't prevent someone from doing what they want
Next steps:
Move discussion to dev forum, will re-visit in next tech committee
Action Items