Page Comparison

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
  • No CC Meeting this week
• PC: Tod Olson
  • Kristin Martin rotating off as co-chair, need a new co-chair
  • Jeremy Huff will act as liaison from PC to TC (taking over from Owen Stevens)
  • Developer Advocate updates, largely reviewing developer documentation and working on developer mentorship program. Planning to interview Library of Australia to learn about their issues during onboarding
  • Acquisitions SIG is piloting a program for prioritizing issues, using JIRA voting (though concerned that "voting" may be interpreted as making development decisions as opposed to helping dev teams prioritize.
• RMS Group: Jakub Skoczen 
  • meetings canceled until 7/29
• Security Team: Craig McNally 
  • Jens Heinrich and Kevin Day  joined the attended a security team meeting to discuss potentially joining. 
• Tri-council Application Formalization: Jenn Colt  
  • No meeting last week

We had a productive retrospective last week, Several discussion topics were identified, which we need to allocate some time for...

Retro Board:

https://easyretro.io/publicboard/dY8fCRqguiSDP3wtvSLhNzlULdM2/1cf104bb-6aa4-4eb3-a878-0f9f1e235436

It's probably worth reviewing if you weren't present.

Continue RFC discussion again this Wednesday

Check in on action items:

• DONE - Taras Spashchenko to incorporate the notion of review windows into the RFC Process documentation
• DONE - Craig McNally to remove the Draft Refinement stage from the RFC Process documentation, make minor adjustments to language of RFC Prep and Public Review stages
• DONE - Craig McNally to remove Draft Review PR metadata field from the RFC template
  
  • See https://github.com/folio-org/rfcs/pull/36
• DONE - Craig McNally/ Jenn Colt to add the "adapt the RFC process to use the wiki" topic to an upcoming Wed. session
  • planned for 17 Jul 2024 along with a couple other RFC-related topics.
• DONE - Craig McNally to update the RFC Process documentation to highlight the importance of logging an official decision in the decision log upon the conclusion of the RFC. 

• 17 Jul 2024 - Dedication Discussion: RFC follow up continued
• 22 Jul 2024 - Regular TC Meeting
• 24 Jul 2024 - Dedicated Discussion: Topic TBD
• 29 Jul 2024 - Regular TC Meeting
• 31 Jul 2024 - Dedicated Discussion: Topic TBD

• Florian Gleixner - mod-reading-room: Meeting with development team. Got module and functionality presentation. Another meeting after evaluation is soon is planned.
• Jenn Colt - ui-reading-room  - Jenn started evaluation.
• TCR-43: mod-marc-migrations: Jeremy Huff will do the evaluation, Tod Olson and Jason Root will help.

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
• Go programming language
• Application formalization - Craig will update next week

Check Recurring Calendar

Orchid has not been moved from Active to Archived - Fixed
Jenn Colt will look at the table, it appears to be broken. No Q, or R Folio releases on the table. - Fixed

Ingolf Kuss

Jason Root

Craig McNally

Marc Johnson

Julian Ladisch

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

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.

00:18:03	Maccabee Levine:	Yup other folks were correct -- no requirement that the reviewer(s) include a TC member.  https://github.com/folio-org/tech-council/blob/master/NEW_MODULE_TECH_EVAL.MD#evaluation
00:22:35	Root, Jason M:	Reacted to "Yup other folks were..." with 👍
00:22:45	Patrick Pace:	Group Long-Term Strategy And Transition Plan Proposal - Developer Documentation Group - FOLIO Wiki (atlassian.net)
00:41:19	Maccabee Levine:	Apologies that I have to drop off at 11:50.  I support the proposal at offer here.  I share Marc's concern (and raised it at the subgroup), but I feel this organization gives us the best chance at trying to make it work.  And we are getting continuous indication that better documentation is needed.