2025-06-02 Meeting notes

Date

Jun 2, 2025

Attendees

@Jenn Colt
@Craig McNally
@Florian Gleixner
@Tod Olson
@Kevin Day
@Ingolf Kuss
@Julian Ladisch
@VBar
@Owen Stephens

Time	Item	Who	Notes

Time	Item	Who	Notes
1 min	Scribe	@Florian Gleixner	@Jakub Skoczen is next, followed by @Jenn Colt 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-15 min	Liaison Updates	@Maccabee Levine @Tod Olson @Jakub Skoczen @Craig McNally	CC: @Maccabee Levine: PC: @Tod Olson / @Marc Johnson Data Import WG (originally under Metadata Management SIG) has become the Data Import Special Interest Group. Data Import concerns are more broad than bibliographic metadata, will allow separate prioritization and more opportunities to work with other SIGs. The already have a history of running labs for actively testing and troubleshooting workflows and issues. The SIG would like to invite more people to become active members, and plans to post summaries of meetings on their Slack channel. Community Priorities Dashboard Development: Goal is to provide priority guidance when development time is available and POs are looking for relative priorities. Process solicits priority items from SIGS and PC to give relative rankings based on Impact, Competitiveness (in marketplace), Usability, and Vision alignment. RMS Group: Nothing new Security Team: @Craig McNally: Nothing new. semgrep is in evaluation, @Craig McNally will report to the TC. Eureka Early Adopters: @Craig McNally: Latest status updates can be found here , spreadsheet there is up-to-date Community Driven Development: Decided on goals for group, defining what CCD means. Reviewed docs that have been put out. Meeting every week in June Wed at 10am EST. Community Driven Development Working Group
5-10 min	Upcoming Meetings	All	Jun 2, 2025 - Regular TC meeting Jun 4, 2025 - Dedicated Discussion - Kong/Keycloak and flower releases Jun 9, 2025 - Regular TC meeting Jun 11, 2025 - Dedicated Discussion - Environmental variables and Folio multitenant upgrade problem Dedicated Discussion Topics: Kong/Keycloak and flower releases - treat them like infrastructure or like modules? Okapi support proposal Support Ramsons with Okapi until 2026-03-31: – FOLIO Security Group's decision regarding extention of Ramsons support period: "Secuity group suggests to not extend the support period because Spring based modules are out of support, unless all Spring base modules get updated to a supported Spring version." The dev teams have released the 6 Okapi-specific modules for Sunflower: Okapi multi-flower-release 6.2.x, mod-authtoken 2.17.x, mod-login-saml 2.10.x, mod-consortia 1.3.x, mod-login 7.13.x, mod-permissions 6.7.x The snapshot reference environments and the Karate tests have successfully been running Sunflower with Okapi. Institutions that want to run Sunflower with Okapi may need to set up a Sunflower Okapi Bugfest environment. FOLIO contribution network proposal: @Craig McNally Is this in discussion or for approval? @Jenn Colt Still in discussion Environmental variables - Kevin/Sysops problem statement Folio multitenant upgrade problem could be discussed during dedicated discussion about environment variables. inconsistencies among variable naming across modules Ingolf will address this in Sys Ops SIG 2025-05-07 Sys Ops & Management SIG Agenda and Meeting Notes some problems with increased memory (from Q → R) and JAVA_OPTIONS parameters. Many modules have to be adapted for more memory. Many out-of-memory events and heap-space events. problems with the ENV variable. Kafka topics use that and also the Elasticsearch index. Maybe the ENV variable should be named better. Maybe it should be only for Kafka. It is not good to use the ENV variable for two purposes. Upgrades get broken if you don't change the value of ENV between releases on a muti-tenant system. env variables with dots: e.g. okapi.url , tenant.url, kong.url , am.url . This is inconsistent and can cause errors. For mod-fqm-manager, there are lowercase variables with dots. See: Open Group Base Specifications Issue 6, IEEE Std 1003.1, 2004 Edition, Environment Variables Spring Boot doc: Externalized Configuration Binding From Environment Variables where are the pain points ? What problems have system admins encountered ? variables with different names in different modules, but which express the same quantity inconsistent naming (KC_, KEYCLOAK_, ...) 2025-05-12 Sysops did have this discussion, @Ingolf Kuss will share the notes in Slack. Developer Advocate Evaluating existing modules Communication plan to promote updates to OST pages Need to update OST pages with communication plan changes Need a retro on changes to OST(?) TC Roles and Responsibilities Has this been influenced by CC adopting a vision statement that the community should direct FOLIO development? FQM RFC WOLFcon Planning OST discussion around the Grails 7 and Java 17 issues; get to talk to the stakeholders there might be a securiry issue to it OST Trillium: Spring Boot 4.0: As the next minor version after 3.5 is 4.0 we should replace or Spring Boot 3.6 decision with Spring Boot 4.0: https://spring.io/projects/spring-boot#support Issue about the Eureka release schedule - do we want to come back to it ? Continued third-party support during release periods Prompted by Kong/Keycloak and Spring Boot, plus extra-long Trillium cycle Should probably talk about this more generally, beyond these specific examples
0 min	TCR Board Review	All	Nothing on the board
0 min	Technical Council Sub-Groups Updates	All	Nothing to discuss today
5 min	GitHub RFCs Wiki RFCs	All	6-2: Previous: Check in on documentation updates - @Joshua Greben @Joshua Greben went through all the pages, removed GitHub references and changed to refer to wiki. Should be done. TC members should review. Circle back next Monday. @Joshua Greben will reach out to the authors of the RFCs in GitHub to retroactively add (stub records) on the wiki, linking out the RFC. Example in RFC log entry for application formalization. You need some metadata (which is already on the template) for it to show up in the list. Today: Remaining work: fix the page properties metadata so the RFCs appear in the log
5-10 min	Decision Log	All
10 min	Officially Supported Technologies (OST)	All	Jenn posted updates, let her know if more info was needed.
5 min	Vagrant box support (related to Equinix)	Craig	6-2: Jenn posted to CC, will post to the other channels too. @Craig McNally Conversation about alternatives will start when needed. ___ The proposal from DevOps is to support vagrant boxes for Q and R, and then stop doing it going forward. Wayne thinks this is about 1 weeks worth of focused effort on the DevOps side and he will let us know when they might be able to schedule this work. Equinix is provider supplying the environment in which we build Vagrant boxes Some people still using Vagrant boxes, but not most SysOps/DevOps suggest supporting through Q & R, then let it drop; extending further requires a lot of extra tooling; goal is formal approval from PC Mainly useful for Okapi environment, not for Eureka About one week of work for Q & R; much more for Eureka Note this is still an officially supported path for a development environment, especially for UI dev; Suggestion that we need a replacement before announcing sunset of Vagrant boxes Vagrant has been practically superseded by Rancher environments for some years now, though challenges with who pays for these environments Observation: tend to be obstacles (bureaucratic and financial) for developers at universites to spin up a Rancher environment, may not have the needed local resources; obstacle for community development CC might be good venue for this question of how to provide development environments, and TC is the right body to bring the question In this case TC is mainly communication, we are not in position to make alternative recommendations, not in our remit Decision TC approves by lazy consensus Next steps Multiple communications: communication in development channel and folio-stripes-architecture, folio-stripes-updates Update documentation (who?) Jason to communicate to DevOps Communicate to CC that one alternative to Rancher environments for devs is going away, @Jenn Colt will inform CC See Vagrant as the key dependency here: https://github.com/folio-org/stripes/blob/master/doc/quick-start.md And here: https://github.com/folio-org/stripes/blob/master/doc/new-development-setup.md Also Eureka Developer Guide \| Getting Started Today: Check-in... did the things above happen? The upcoming flower release “Xique xique” will be Witten Xiquexique to accommodate scripting around it. @Craig McNally will make chairs group aware of the problem and asks if a formal approval has to be done. Deprecation of mod-configuration DR-000039 - Distributed vs. centralized configuration @Craig McNally some teams still use it. Developers are aware of the deprecation. Do we need to follow the timing plan with a readonly transition step or or can we just remove mod-configuration in Trillium or Umbrellaleaf? Probably developers need some time? @Jenn Colt Is managing this via RFC unusual? @Craig McNally We did it for some other things too: Postgres / Eureka… @Craig McNally will talk to developers, if they can make the transition, then stick to the plan, dropping the readonly phase, when not needed. If developers need more time, extend the plan to Umbrellaleaf. @Florian Gleixner if the plan can not be fulfilled, a formal decision to extend the plan should be made.
as NA	Zoom Chat		17:21:00 From Day, Kevin To Everyone: https://github.com/folio-org/mod-configuration?tab=readme-ov-file#deprecation 17:25:04 From Owen Stephens To Everyone: Speaking as a member of a team affected by this, I was definitely aware of the deprecation. I think the deprecation was pushed back from Sunflower to Trillium to give extra time to move? 17:25:34 From Owen Stephens To Everyone: But we’ve just completed work to migration away from it for Trillium for our modules - so unusually I get to feel smug Jenn Colt, Tod Olson:😂

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: Schema linting does not occur if the schemas are in YAML format. There are issues with resolving some deeper references during API linting. 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. From my perspective, pr template is not good idea. Even the biggest open source projects that are contributed by many people don't have any pr template. Currently what we have for acq modules https://github.com/folio-org/mod-orders-storage/blob/master/PULL_REQUEST_TEMPLATE.md These pr template is inconsistent in different teams. 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.