7am PST / 4pm CET
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
Time | Item | Who | Notes |
---|---|---|---|
10m | Agenda and action item review | Josh Zamor | Action item review from https://openlmis.atlassian.net/wiki/x/vAAND Open action items from last time:
|
Dispensable - inner workings | Chongsun Ahn (Unlicensed) | ||
Java imports | Chongsun Ahn (Unlicensed) |
For code style guides, google simplified it - all static fist, non-static second, alphanumeric secondary sort. We adopted the style-guide way back, yet we seem to have removed the import order enforcement.
Next steps:
Discussed the migration of PoD rights in .
Open question on how to automate migration:
We chose #2 ,delete the old PoD Manage right as no production system is using the PoD feature. We'll add a note to the release notes for good practice, but otherwise the migration is a destructive action, that we predict will have no negative outcome.
We propose that option #3 might be useful - implementations migrating from an old version to the new would have anyone assigned the stock management right, automatically added to the PoD Manage right. New implementations wouldn't get this, but perhaps that's okay as in the future with ASN we'll have more PoD functionality migrated to the stock management service.
Next step: