Page Comparison

Jakub Skoczen is next, followed by Taras Spashchenko

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.

Maccabee Levine

Tod Olson

Jakub Skoczen

Craig McNally

Jenn Colt 

• CC: Maccabee Levine
  • Simeon and Chris are now co-chairs
  • Patrick gave dev advocate update. DA service desk form finally working. Intro'd to dev community. Did a developer environment tour with Kevin Day; 3 more set up but not yet scheduled. Working to get documentation processes established in case not renewed in October. Various proposals accepted by TC. Attending team leads meeting on Thursday to introduce, get thoughts. Also testing developer setup himself. Feedback on how to keep the manual going. Mike shared he has heard only positive things about Patrick's work.
  • Treasurer update. Carrying over 200k from FY24. FY25: AWS costs increasing, increase in test environments. Kat invited Peter and Yogesh to September 9th meeting to explain costs. Shawn Nicholson stepping into Tom's slot as third ACRG member. Kat has asked the group for a budget. Chris: important to see what part of the increase in costs is due to Eureka testing environments. Simeon: dev advocate continuing would be good, is tied to AWS discussion. should find a way to control AWS expense and to extend developer advocate role. Others agreed. Consensus that all are in support of continuing that role, pending financial analysis to determine how. CC added that projection to next year's budget. CC said they wanted to let Patrick know ASAP, just making numbers worked. Could approve it even with increased AWS costs, enough buffer for FY25 but not following year. Jenn volunteered to join ACRG if needed.

    Lref gdrive file
    url https://docs.google.com/spreadsheets/d/1pHhJ1rdX6E-G-xRuZMqePVPy0gUF755wWsuuvG5xiPY/edit?gid=28046518#gid=28046518

• PC: Tod Olson
  • Developer Advocate update, included this good observation:

    • Good citizen behavior requires a more cultural change for teams to keep general documentation up-to-date. Structural short-coming in the FOLIO community that this hasn’t been clearly delegated.

  • Ideas for tracking/maintaining/supporting roadmap
• RMS Group: Jakub Skoczen 
  • ...
• Security Team: Craig McNally 
• Tri-council Application Formalization: Jenn Colt  
  • Off this week. Last week picked  up work on spreadsheet, Kristin and Charlotte from PC have been working on it

• 14 Aug 2024 - Dedicated Discussion: Topic TBD
• 19 Aug 2024 - Regular TC Meeting
• 21 Aug 2024 - Dedicated Discussion: Architectural decision making
• 26 Aug 2024 - Regular TC Meeting

All

All

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, can be accepted. Florian says it's pretty settled
• Go programming language
• Application formalization

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 wants to go to JDK 21, LTS version, Marc concerned about the Operations work this will incur, Taras agrees this will take some heavy lifting

• 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) This is a regularly scheduled release, giving developers a head's up would be a good thing.
• Not clear on Sunflower version scope timeline and supported vert.x version
  
  Several more action items on Officially Supported Tech page. SysOps needs to be included in the informational process.

Ingolf Kuss

Jason Root

Craig McNally

Marc Johnson

Julian Ladisch

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:

• Original problem statement
• Input from SysOps SIG
• Proposals considered by Tech Council working group
• Recommendation from Tech Council working group

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: