2025-01-15 Meeting notes

Date

Jan 15, 2025

Attendees

@Craig McNally
@Maccabee Levine
@Julian Ladisch
@Marc Johnson
@Ingolf Kuss
@Florian Gleixner
@Joshua Greben
@Jenn Colt
@Tod Olson

Discussion items

Time	Item	Who	Notes

Time	Item	Who	Notes
1 min	Scribe	All	@Tod Olson is next, followed by @Kevin Day 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	CC: @Maccabee Levine: No meeting PC: @Tod Olson: Main topic has been PC approval process. PC Subgroup on Evaluation Process presented a proposal, discussion followed. RMS Group: @Jakub Skoczen: New dates for Ramsons proposed, to be voted on; see chat log below. Need a couple weeks to assess how new Ramsons date will affect Sunflower. Security Team: @Craig McNally: Reminder to please review Deprecation Policy for FOLIO Modules outside of the official supported set with a Severe Security Vulnerability and provide feedback.xz Eureka Early Adopters: @Craig McNally Kickoff meeting 1/14 with Folio DevOps (Index Data), and Texas A&M Emphasis on collaboration, info sharing, etc. across the participants, Kitfox, EBSCO. Check-in with GBV earlier today. They've bumped into issues with hosting Keycloak, Kitfox is helping improve documentation. I've created a wiki page to collect information/findings/observations: Hosting / SysOps Findings
1 min	Upcoming Meetings	All	Jan 20, 2025 - Cancelled - MLK Day (US) Jan 22, 2025 - Regular TC Meeting – moved to Wed. this week due to US holiday on Mon. Jan 27, 2025 - Regular TC Meeting Jan 29, 2025 - Dedicated Discussion - TCR documentation changes Feb 3, 2025 - Regular TC Meeting ??? - Tri-council meeting - follow-up on Eureka Adoption?
5 min	TCR documentation change PRs		https://github.com/folio-org/tech-council/pulls Had planned to accept a number of simple changes in one Topic for a Wed meeting, slot for 29 Jan.
5-10 min	TCR Board Review	All	Deadline is technically Jan 24, but there may be some wiggle room given that Ramsons has slipped, and it's likely that Sunflower will as well. It isn't known yet by how much. Still aim for 24 Jan Not submitted yet, but someone from K-int reached out to PC and TC chairs about a new ILL module. We've informed him of the deadline, and pointed him to appropriate documentation. Folks involved in this module are new to K-int, will be learning process TCR Status/Updates: https://folio-org.atlassian.net/browse/TCR-46 mod-linked-data One bug issue - resolved & merged licensing is fine Accepted! https://folio-org.atlassian.net/browse/TCR-50 ui-linked-data Some questions about how to test a few outstanding items Nothing is looking controversial https://folio-org.atlassian.net/browse/TCR-51ui-ld-folio-wrapper Kevin not here today
5 min	Technical Council Sub-Groups Updates		Developer documentation subgroup needs new leader Question about how this intersects with the in-progress Eureka documentation ACTION: @Craig McNally: start conversation with Patty, @Jenn Colt, @Maccabee Levineon developer documentation
1 min	GitHub RFCs Wiki RFCs	All	...
1 min	Decision Log	All	No changes
5 min	Officially Supported Technologies (OST)	All	Check Recurring Calendar... @Craig McNally @Jenn Colt clean up OST and calendar We need to incorporate Go and then update the Calendar as well. Update the next instance in the calendar.
*	Voting Rules	All	See proposals: Voting Rule Comparisons Straw vote about whether we should require at least 6 yes votes to accept a proposal: 4 yes, 4 no. Today's notes: Review options around quorum and whether we use majority of members present or votes cast. Straw poll (non-binding): do we accept majority of cast (yes) or majority of TC members present (no): Yes: 3 No: 6 Absentions: 2
NA	Zoom Chat		`10:06:47 From Jenn Colt to Everyone:` `Dear RMS panel,` `Yesterday, we've met with short number of attendees.` `Please review meeting notes -` 2025-01-13 Release Management Stakeholder group `Proposal of wide message with new dates of Ramsons Release:` `Jan 13 - Jan 24 - Additional run of manual and automated regression testing` `Jan 24 - Ramsons bugfix deadline` `Jan 27 - Jan 31 - Final smoke testing week` `Feb 3 - Ramsons GA` `Please your likes if you support proposed dates and I will proceed with sharing of wide message` `Thank you in advance` `10:44:27 From Ingolf Kuss to Everyone:` `and that was understood to be the Default threshold.` `10:44:55 From Ingolf Kuss to Everyone:` `I mean, one can agree to lower or raise the threshold before each voting.` `10:54:19 From Jenn Colt to Everyone:` `And Tod so that’s three of us!` `10:57:47 From Maccabee Levine to Everyone:` `We are down to 3 minutes --- let's actually do this straw poll please?` `10:58:47 From Ingolf Kuss to Everyone:` `Yes, let's just have a straw poll. After this, someone might rewrite the proposal for the voting rules (in the spirit) of the straw poll.` `10:58:53 From Julian Ladisch to Everyone:` `Please do the straw poll. We don't need rules for a straw poll.` `10:59:01 From Ingolf Kuss to Everyone:` `Reacted to "Please do the straw ..." with 👍` `11:00:56 From Maccabee Levine to Everyone:` `Let's have a straw poll on whether we will get there some day :)` `11:01:15 From Craig McNally to Everyone:` `Reacted to "Let's have a straw p..." with 😂` `11:01:35 From Marc Johnson to Everyone:` `Reacted to "Let's have a straw p…" with 😀`

Topic Backlog
Decision Log Review	All	Review decisions that are in progress. Can any of them be accepted? rejected?
Translation Subgroup	All	Since we're having trouble finding volunteers for a subgroup, maybe we can make progress during a dedicated discussion session?
Communicating Breaking Changes	All	Currently there is a PoC, developed by @Maccabee Levine, of a utility to catalog Github PRs that have been labeled with the "breaking change" label. We would like to get developer feedback on the feasibility of this label being used more often, and the usefulness of this utility.
Officially Supported Technologies - Upkeep	All	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.
Dev Documentation Visibility	All	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.
API linting within our backend modules	All	https://folio-project.slack.com/archives/CAQ7L02PP/p1713343461518409 Hello team, I would like to discuss API linting within our backend modules. Some time ago, we transitioned our linting process from Jenkins to GitHub Actions as outlined in https://folio-org.atlassian.net/browse/FOLIO-3678. I am assuming that this move was done via some technical council decision. Please correct me if I'm wrong. In my observations, I've found two problems: Although I'm unsure about how to improve the existing linting implementations within Folio, I propose to consider an open-source solution that handles OpenAPI linting effectively and allows us to define custom rules. For your reference: https://stoplight.io/open-source/spectral A test of this solution can be found in this PR: https://github.com/folio-org/mod-search/pull/567. The same PR also provides an example of custom rule definition: https://github.com/folio-org/mod-search/pull/567/files#diff-d5da7cb43c444434994b76f3b04aa6e702c09e938de09dbc09d72569d611d9ab.Also, by employing 'Spectral', I discovered AsyncAPI (https://www.asyncapi.com/en), an API design tool similar to OpenAPI but for asynchronous interactions. I suggest that we consider using AsyncAPI in FOLIO to generate documentation for Kafka interactions.
PR Templates	All	https://folio-project.slack.com/archives/CAQ7L02PP/p1713445649504769 Hello team, Small request to consider. Regarding pr templates. What I suggest is that, pr template shouldn't be any instructions, because most developer who are creating pr have already understand the rules. If we put just two section into template, it will encourage developers to write more about their work and that lead to knowledge sharing among developers.
Proposed Mod Kafka	All	https://folio-project.slack.com/archives/CAQ7L02PP/p1714471592534689 Mike Taylor Proposal. If and only if a FOLIO instance is running Kafka, it should insert and enable a module called mod-kafka, which consists entirely of a module descriptor that says it provides the interface kafka. The purpose is so that other modules can use the standard <IfInterface> and similar tools to determine whether they should attempt Kafka operations. Rationale: the FOLIO ILS depends absolutely on Kafka, but other uses of the platform will not. One such example: a dev platform that includes only mod-users, used as a source of change events for Metadb.