| | | |
|---|
1 min | Scribe | All | @Marc Johnson is next, followed by @Ingolf Kuss 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 | @Maccabee Levine @Tod Olson @Jakub Skoczen @Craig McNally @Jenn Colt | CC: @Maccabee Levine PC: @Tod Olson RMS Group: @Jakub Skoczen Security Team: @Craig McNally No updates, triaging issues. Tri-council Application Formalization: @Jenn Colt
|
10 min | TCR Board Review | All | |
1 min | Upcoming Meetings | All | Jan 31, 2024 - TCR Process Improvements Feb 5, 2024 - Regular TC meeting Feb 7, 2024 - Dedicated Topic Discussion - Topic TBD
|
5-10 min | Technical Council Sub Groups Updates | All | Quick updates only. If we can't find volunteers for groups, we'll need to add the topic to our backlog and address it during dedicated discussion sessions. Configuration group @Ingolf Kuss advised that @Olamide Kolawole submitted some comments and he and @Julian Ladisch met to discuss them @Marc Johnson raised that it seemed unusual for a contributor to be raising suggestions on the pull request (rather than making edits) and could consider guidance on this as a possible topic for the next process review
Translations TCR Process Improvements @Maccabee Levine advised that this would be discussed at Wednesday's meeting and feedback / attendance from the TC would be appreciated And that the group are also working with the PC chairs to improve the hand off process and to provide a communication plan for the changes
|
10 min | RFCs | All | Application Formalization RFC - DRAFT REFINEMENT PR: https://github.com/folio-org/rfcs/pull/22 Go Programming Language for Backend Development RFC - PRELIMINARY REVIEW PR: https://github.com/folio-org/rfcs/pull/25 @Marc Johnson asked if this was practically in draft refinement, given that it is receiving comments? @Craig McNally suggested there is some administration that needs to go along with that and refer folks to the documentation of the process in case comments were made prematurely
Distributed vs Centralized Configuration RFC - DRAFT REFINEMENT PR: https://github.com/folio-org/rfcs/pull/26 - @Olamide Kolawole will help the group
RFC Process Improvements: |
1-5 min | Postgres Messaging | All | The announcements were made before the holidays. No objections. Probably need to ask testing people explicitly. See: DR-000038 - PostgreSQL Upgrade to 16 Notes: |
1 min | Decision Log | All | Standing agenda item... is there anything in the decision log requiring attention? @Craig McNally Advised that we might have another source. @Marc Johnson advised that space was created by the Tech Leads, prior to decision records were introduced |
20-30 min | Officially Supported Technologies (OST) | All | Standing agenda item to review/discuss any requested or required changes to officially supported technology lists Check in on progress... does anything else require attention? Next Important Milestone: Review Ramsons (3rd party dependencies) and move from DRAFT → ACCEPTED by Feb 16, 2024 Notes from this meeting: @Maccabee Levine described updates to the process examples and walked through the example with @Craig McNally who raised minor amendments @Marc Johnson suggested that there will only be 2 releases in 2024. @Owen Stephens and @Craig McNally asked if anyone was aware of an official announcement on this @Craig McNally asked when there would be 4 active flower releases? @Marc Johnson advised that there will be 4 releases when the previous 2 are in support, the current one is being released (and has not become generally available) and the next release has started development (after the feature freeze for the current release) @Marc Johnson shared the draft inclusion of policy decisions and reasoning for each type of technology in the Ramsons OST page
|
1 min | Reminders | All | Quick reminders to TC members... Please review the PR for proposed changes to the TCR process: https://github.com/folio-org/tech-council/pull/55. This will be the topic of discussion on Jan 31, 2024
Please review @Marc Johnson 's changes to the Ramsons OST page (see above)
|
NA | Zoom Chat | | 11:04:33 From Jenn Colt to Everyone:
If you mean the slack thread that was just me asking tri council
11:05:09 From Jenn Colt to Everyone:
I thought of it in PC but didn’t want to drag into a rabbit hole
11:10:33 From Owen Stephens to Everyone:
@Marc Johnson can you say\
11:10:53 From Owen Stephens to Everyone:
Replying to "@Marc Johnson can yo..."
Sorry - can you say what the comments were about functionality that came up at PC?
11:12:05 From Marc Johnson to Everyone:
Replying to "@Marc Johnson can yo…"
It was mentioned that the TC had discussed the virtual item and patron lifecycles
Which confused me because I was completely unaware and it’s not part of our remit
11:12:25 From Marc Johnson to Everyone:
AFAIK there is also no way to find / list the transactions either
11:13:10 From Maccabee Levine to Everyone:
https://github.com/folio-org/tech-council/pull/55/files
11:13:45 From Owen Stephens to Everyone:
Replying to "@Marc Johnson can yo..."
Thanks
11:14:00 From Craig McNally to Everyone:
Reacted to "https://github.com/f..." with 👍
11:14:04 From Craig McNally to Everyone:
thank you @Maccabee Levine
11:17:54 From Marc Johnson to Everyone:
It’s worth noting that IIRC the product folks we did have in the last localisation / translation working group didn’t consider multi-lingual support in the same tenant to be a high priority which might explain why it hasn’t garnered a lot of attention
11:24:57 From Craig McNally to Everyone:
https://folio-org.atlassian.net/wiki/display/DD/Technical+Designs+and+Decisions
11:26:14 From Marc Johnson to Everyone:
That space also has team / module level decision documentation in it as well
11:29:24 From Marc Johnson to Everyone:
Many folks have found the 4 concurrent releases aspect of this to be challenging
11:29:42 From Jenn Colt to Everyone:
Reacted to "Many folks have foun..." with 🤯
11:31:32 From Owen Stephens to Everyone:
Q->R->S
11:33:49 From Jenn Colt to Everyone:
Do we know who would do it?
11:34:43 From Owen Stephens to Everyone:
If we were to do 3 releases this year (which is the cadence we aim for in theory) then Sunflower will be late 2024. However last year the Poppy release was pushed back a long way so we only got 2 releases
11:35:57 From Owen Stephens to Everyone:
Replying to "If we were to do 3 r..."
… in 2023
11:35:58 From Marc Johnson to Everyone:
Replying to "If we were to do 3 r…"
I thought 2024 was only getting 2 releases. Though I’m not sure where I got that understanding from
11:36:15 From Owen Stephens to Everyone:
Replying to "If we were to do 3 r..."
I’d not seen that anywhere but could have missed it
11:36:28 From Owen Stephens to Everyone:
Replying to "If we were to do 3 r..."
It seems more realistic tbh
11:38:36 From Huff, Jeremy T to Everyone:
Replying to "If we were to do 3 r..."
Wasn’t two releases what was decided on during the trip council meeting?
11:38:53 From Huff, Jeremy T to Everyone:
Replying to "If we were to do 3 r..."
Tri, not trip
11:39:30 From Jenn Colt to Everyone:
Replying to "If we were to do 3 r..."
Was that a decision or a discussion? I didn’t get the sense that was anything other than a recommendation?
11:39:53 From Huff, Jeremy T to Everyone:
Replying to "If we were to do 3 r..."
That’s true, I do not recall voting or anything like that.
11:40:09 From Tod Olson to Everyone:
Replying to "If we were to do 3 r..."
I had the same impression as Jenn.
11:40:13 From Huff, Jeremy T to Everyone:
Replying to "If we were to do 3 r..."
But it did seem to be an uncontested suggestion.
11:41:02 From Jenn Colt to Everyone:
It looks like RMS met this morning but I don’t see notes, just a recording
11:41:05 From Marc Johnson to Everyone:
Replying to "If we were to do 3 r…"
I didn’t get the sense that was an official decision, rather that the conversation reached a point where folks had mostly coalesced
11:48:01 From Tod Olson to Everyone:
I need to drop and get ready for the next thing, thanks everyone. |