Date
...
Time | Item | Who | Notes |
---|---|---|---|
1 min | Scribe | All | Jason Root is next, followed by Jakub Skoczen Reminder: Please copy/paste the Zoom chat into the notes. If you miss it, this is saved along with the meeting recording, but having it here has benefits. |
5-10 min | Liaison Updates |
| |
1 min | Upcoming Meetings | All |
|
5-15 min | TCR Board Review | All | |
5 min | Technical Council Sub-Groups Updates | All | |
1 min | RFCs | All | Reminder(s)
|
1 min | Decision Log | All | Need to log decisions for the following: (see above)
|
10-15 min | All | Check Recurring Calendar
| |
5-10 min | Developer Advocate Monthly Report | Patrick Pace (Unlicensed) | |
Time Permitting | Reference Data Upgrade | Hold until after Aug 2. In the Sys Ops SIG meeting the topic of Reference Data Upgrades came up. The SIG thinks that the solution of this problem for mod-inventory-storage is not enough, but that this problem needs to be solved in a general way, for all modules. There has been a long discussion 3-4 years ago about how FOLIO should handle reference data upon upgrades. See these links for background:
Previous Notes: Marc Johnson points out he remembers a difference set of formal processes for this from the previous subgroup Jason R. asks if the issue is that you cannot specify per-module what type of data to load, or that no matter what is specified the upgrade process overrides it Marc mentions that the proposal to correct this by Vince is a very involved and complex workflow. There has been no developer resources allocated to correct this issue and address the proposal No easy solution to this problem because the original default data is lost to time and change Will reach out to Julian Ladisch when he returns Notes: Ingolf Kuss is on vacation. Lets wait until Julian and Ingolf are both here. Today:
| |
NA | Zoom Chat |
...