2024-01-29 Meeting notes

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.

Maccabee Levine Tod Olson  Jakub Skoczen  Craig McNally Jenn Colt 

• CC: Maccabee Levine
  • No CC meeting this week
• PC: Tod Olson 
  • Presentation on DCB, both DCB-related UI changes and discussion of DCB Integration. Acceptance vote now underway in Slack.
• RMS Group: Jakub Skoczen 
• Security Team: Craig McNally No updates, triaging issues.
  • No important updates - business as usual
• Tri-council Application Formalization: Jenn Colt 

All

• 31 Jan 2024 - TCR Process Improvements 
• 05 Feb 2024 - Regular TC meeting
• 07 Feb 2024 - Dedicated Topic Discussion - Topic TBD

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 - last meeting Olamide Kolawole will take a look at it and will provide comments.  Has that happened?
• Breaking changes - 
• Translations - Craig McNally bumped the topic in the folio chairs channel.  Stay tuned.

All

• Status/Updates:
  • 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
  • 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:

• We need another RFC to update the metadata retroactively to reflect the new or adjusted statuses. - Jenn Colt will do this, hasn't finished yet
  
  • nothing new today

The announcements were made before the holidays.  No objections. Probably need to ask testing people explicitly. 

See: DR-000038 - PostgreSQL Upgrade to 16

Notes:

Craig McNally - reached out to the test manager (Yogesh Kumar) today to check alignment on the plan for testing this.  Awaiting a response.  Stay tuned.

Standing agenda item... is there anything in the decision log requiring attention?

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 16 Feb 2024 
  • Maybe we should aim to start looking at this on 05 Feb 2024 so we have time for discussion/adjustments.
• Versions for the components:
  • Review/discuss Marc Johnson's draft changes to the Ramsons OST page.  See thread in #tc-internal for additional context/details.
• Timing of upkeep activities:
  • Review/discuss Maccabee Levine's adjustments to the OST page wrt timing of upkeep activities.
  • From Maccabee Levine in #tc-internal:

Please see the thread above about an error on the OST page for when to do one of the status transitions. I have added two new example tables to the OST page, in place of the examples that were listed previously:

• one which shows all the dates & triggering events that would affect the Quesnelia OST page
• and one that shows all the events during the Quesnelia release cycle that affect various OST pages (for Orchid, Quesnelia, Ramsons and Sunflower).

Wish I could do a PR on Confluence, but I just published the changes, here's the diff and we can always revert or adjust further.

Quick reminders to TC members...

1. Please review the PR for proposed changes to the TCR process:  https://github.com/folio-org/tech-council/pull/55. 
   1. This will be the topic of discussion on 31 Jan 2024 
2. Please review

Previous Notes:

• A workflow for these pages. When do they transition from one state to another. Do we even need statuses at all ?
• Stripes architecture group has some questions about the Poppy release.
• Zak: A handshake between developers, dev ops and the TC. Who makes that decision and how do we pass along that knowledge ? E.g. changes in Nodes and in the UI boxes. How to communicate this ? We have a large number of teams, all have to be aware of it.  TC should be alerted that changes are happening. We have a couple of dedicated channels for that. Most dev ops have subscribed to these channels. How can dev ops folk raise issues to the next level of community awareness ? There hasn't been a specific piece of TC to move that along.
• Craig: There is a fourth group, "Capacity Planning" or "Release Planning". Slack is the de facto communication channel.  There are no objections to using Slack. An example is the Java 17 RFC. 
• Craig: The TC gets it on the agenda and we will discuss it. The TC gets the final say.
• Marc Johnson: We shouldn’t use the DevOps Channel. The dev ops folks have made it clear that it should only be used for support requests made to them.
• Jakub: Our responsibility is to avoid piling up technical debt.
• Marc: Some set of people have to actually make the call. Who lowers the chequered flag ?
• Craig: It needs to ultimately come to the TC at least for awareness. There is a missing piece. Capacity Planning needs to provide input here. 
• Marc: Stakeholders / Capacity Planning could make that decision. Who makes the decision ? Is it the government or is it some parts of the body ?
• Marc: the developers community, the dev ops community and sys ops are involved. For example the Spring Framework discussion or the Java 17 discussion. But it was completely separate to the TC decision. It is a coordination and communication effort.
• Marc: Maybe the TC needs to let go that they are the decision makers so that they be a moderating group.
• Jakub: I agree with Marc. But we are not a system operating group. Dependency management should be in the responsibility of Release management. There are structures in the project for that.
• Jason Root: I agree with Jakub and with Marc also. Policies should drive operational/release/support aspects of Folio.
• Jason Root: If the idea of “support” is that frameworks are supported, then of course the project should meet that.
• Marc Johnson
  Some group needs to inform OleksAii when a relevant policy event occurs.
  These documents effectively ARE the manifestation of the policy.
• Craig: This is a topic for the next Monday session.

• Craig to see if Oleksii Petrenko could join us to discuss the process for updating the officially supported technologies lists.

Possible topic/activity for a Wednesday session:

• Discuss/brainstorm:
  • Ideas for the type of developer-facing documentation we think would be most helpful for new developers
  • How we might bring existing documentation up to date and ensure it's consistent 
  • etc.