2024-11-25 Meeting notes

Date

Nov 25, 2024

Attendees

@Craig McNally
@Jenn Colt
@Charlotte Whitt
@Ghassen Tajini
@Maccabee Levine
@Taras Spashchenko
@VBar
@Marc Johnson
@Florian Gleixner

Discussion items

Time	Item	Who	Notes

Time	Item	Who	Notes
1 min	Scribe	All	@Marc Johnson is next followed by @Jakub Skoczen 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 In person CC meeting planning. LOC (Caitlin) offered to host. Attendence suggestion of CC + other chairs + officers. Also the vendors? Talk about governance models? ACRG update from Shawn. Teams doing a good job keeping under $30k cap/m with manual shutdown processes. Starting in March with Eureka as targeted platform, some environments will be reduced. Can keep to the cap even if Okapi infra is continued past March, but easier if not. Subgroup discussing both short-term and long-term with EBSCO -- what should be considered central infrastructure. EBSCO sent a response today, agrees with principle that development outside of community work should be funded by those doing it. Discussing what community infrastructure looks like as we aim for sustainability. Will ask Kat to re-present the budget with $30k/m AWS cost for remainder of year. CC writing a proposal to get the two devs for better sample data tool. PC: Discussion about reading room functionality RMS Group: @Jakub Skoczen: Security Team: @Craig McNally: No updates Tri-council Application Formalization/Eureka: @Jenn Colt Good productive discussion last Wednesday, will have a part 2
1 min	Upcoming Meetings	All	Nov 25, 2024 - Regular TC meeting Nov 27, 2024 - Dedicated discussion: Cancelled for American Thanksgiving Dec 2, 2024 - Regular TC Meeting Dec 4, 2024 - Dedicated discussion: Eureka timeline continued Dec 9, 2024 - Regular TC Meeting Dec 11, 2024 - Dedicated discussion: New language adoption policy Dec 16, 2024 - Regular TC Meeting Dec 18, 2024 - Developer advocate retro Dec 23, 2024 - Regular TC meeting vs Cancel? Dec 25, 2024 - Cancel Dec 30, 2024 - Regular TC meeting vs Cancel? Jan 1, 2025 - Cancel
5-10 min	TCR Board Review	All	Review of https://folio-org.atlassian.net/browse/TCR-44 @Marc Johnson raised a concern about marking the Sonar criteria as non-applicable, given the efforts to review the criteria in a sub-group @Mike Taylor stated that the module was run through Sonar and so the criteria passes, even though different means are now used Accepted by lazy consensus @Maccabee Levine raised awareness of this question @Jenn Colt and @Craig McNally advised that they hadn't made much progress on their evaluations
5 min	Technical Council Sub-Groups Updates
1 min	GitHub RFCs Wiki RFCs	All	Go still needs work
1 min	Decision Log	All	Go still needs work
5 min	Officially Supported Technologies (OST)	All	Check Recurring Calendar... @Craig McNally @Jenn Colt clean up OST and calendar @Marc Johnson Asked which release Go would be included for Sunflower (by exempting ourselves from the process, and expect system administrators to accommodate it in shorter notice). @Craig McNally advised that we have to accept Go for Sunflower, given the acceptance of `mod-reporting` for Sunflower
1 min	TC member changes	All	@Craig McNally has been updating Election Runner with nominations; will send out to TC members the morning of the 25th.
*	Voting Rules	All	See proposals: Voting Rule Comparisons The TC discussed the proposals @Maccabee Levine suggested we take a goal oriented approach, and the primary trade off is between making decisions with few people vs. not being able to make a decision @Florian Gleixner raised a concern about the lack of distinction between `fail` and `no decision` for option 3 and how that could lead to repeated votes. @Marc Johnson suggested that repeated votes are always an option at present and if `fail` means that no future notes can happen on this topic, that raises the concern about when to revisit decisions
NA	Zoom Chat

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.