Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Date

...

TimeItemWhoNotes
1 minScribeAll

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 minLiaison Updates
1 minUpcoming MeetingsAll
  •  - Dedicated Discussion:  Architectural decision review processes
    • Which process used to propose and review architectural things depends on the size/scope...
  •  - Regular TC Meeting
  •  - Dedicated Discussion: Topic TBD
  •  - Regular TC Meeting
5-15 minTCR Board ReviewAll
5 min

Technical Council Sub-Groups Updates

All


1 minRFCs

All

Reminder(s)

  • Go RFC still open - admin action required, only a PoC - nothing formal required other than closing the pull request.
  • Still Need Decision Log record for application formalization, Go, configuration RFCs
1 minDecision LogAll

Need to log decisions for the following:  (see above)

  • Decentralized configuration - Florian is working on this, will come back around next week. Write-up in draft
  • Go programming language
  • Application formalization - Craig will update next week


10-15 min

Officially Supported Technologies (OST)

All

Check Recurring Calendar

  • Message to channels about RFCs.  Due end of next week.  Craig McNally and Jenn Colt will confer about posting to the listed channels.  Maybe find automation.
  • Need to Review comments on Sunflower page and move to accepted if no further changes are required.
  • Julian Ladisch: "See https://folio-project.slack.com/archives/C01HUKJCMC7/p1722859432396769 why I suggest to consider bumping the Officially Supported Technology version for Spring Boot (and Spring Framework) for Ramsons." (Spring Boot 3.3 to 3.4)
5-10 minDeveloper Advocate Monthly ReportPatrick Pace
Time PermittingReference 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:

  • Maccabee Levine Is this the same as the PC subgroup working to improve sample data?
    • Marc Johnson Not sure.
    • Tod Olson Thought we were taking about the same thing as the group a lot of people were on for a while.
    • Craig McNally Reference data working group a couple years ago is what sysops is taking about.  Not sure if it's the same as the sample data group.
    • Tod Olson Was much more involved the last time.
    • Maccabee Levine Just make sure the two groups are aware of each other.
  • When Ingolf Kuss returns, can get more info.
  • Tod Olson This new PC group is about sample data.  Years ago data was contributed.  Now new functionality, there are no sample data test cases.
  • Maccabee Levine Example, in snapshot there are no orders connected to any invoices.
  • Tod Olson Reference data can be customized (i.e. material types) or added to, but often is not.  Some stable conventions are needed for the reference environments.  It's a fuzzy boundary.
NAZoom Chat



...