2025-10-02 Product Council Agenda and Minutes

2-5 Min

Welcome & Announcements

Housekeeping

5 Min

Interim Co-Chair

Due to the US Government Shutdown @Caitlin Stewart will be unable to participate with the FOLIO Community until that situation has been resolved. In the meantime, we will ask for volunteers to serve as Interim Co-Chair.

Tod Olson has volunteered to step in.

5 Min

Continued SIG Engagement

• The continued scheduling of the SIG’s to discuss their top 5 priorities: There are SIGs that haven’t come to PC for their top 5 priorities. Liaisons: Please look at your SIGs and if they haven’t signed up, have them sign up

Question: There are the SIGs who come and then there’s the rolling schedule. Should the SIGs just sign in themselves? Is this for the priorities or just updates? These are 2 different things. Signing up is for the priorities only at this time.

Question: There are the top 5 priorities. Has a process been set up yet for the top 5 for the project? No, this hasn’t been defined. Caitlin might have a clearer idea. Once we have all the priorities, PC will engage a process.

SIGs can use the PC Topic Calender to sign up for a day and time to present.

• The beginning of the SIG update rotation schedule

Standing Updates

10 Min

RMS

TC

CC

RMS: Draft Proposal from TC about Support Periods. Timeline for NLS and Klemming work. We will require approximately 6–8 weeks to refine and define the new Trillium release dates. The process will consist of the following sprints:

• Sprint 226: Compile a list of key issues that must be addressed for Trillium (identifying P1/P2 items for each category).

• Sprint 227: Build a preliminary ('strawman') timeline based on the compiled list of issues.

• Sprint 228: Review the proposed timeline and scope with the RMS.

• Sprint 229: Incorporate community feedback and finalise the Trillium release schedule and date.

Due to this significant release delay, "critical" Trillium features will be backported to the Sunflower as a CSP.

Dates will slip a bit as CSP 2 has been delayed.

Support Periods: This document is still being discussed in TC and no consensus has been reached yet. The TC co-chairs will put together a list of potential scenarios and recomendations for actions.

TC:

• Pilot review of existing modules: mod-ebsconet and ui-export-manager

• Ongoing work w/ OSS license reviews, issues with LGPL

• Working on guidance around best practices for breaking changes

CC:

• No meeting.

New Topics

25 Min

Select Our Top Three Priorities

We will review and then select our top three priorities from those discussed at the WolfCon Shoulder Meeting. The Retro Board can be found here.

Comment: At Friday’s tricouncil, there was a group created to investigate Koha’s governance model.

We need to work on the framework. But whatever we can do in the meantime to engage the community would be beneficial.

We need to make sure that we don’t forget about anything on the back burner. That’s a great idea. We need to make sure we clean up our future topics and back burner lists.

Our top 3:

• Continue to build out community priorities dashboard

• Define relationship between PC and RMS

• CDD work

It would be great if everyone in PC engaged in one of the groups.

15 Min

Sub Group Formation and Clean Up

We will discuss the formation of subgroups dedicated to accomplishing each of our selected priorities. We will spend some time cleaning up our current list of subgroups to ensure that we have capacity to focus on our selected priorities.

Volunteers to chair:

Can we post this in our Slack channel? This will allow people time to figure things out. Yes and will ask if anyone can do it now.

We should post because we are missing several PC members.

Would we be open to a group member not being a PC member? It can be convened by a member of PC and have any members.

The Tricouncil working group on CDD was to bring something to WOLFcon to present. This group will meet next week to go over feedback from WOLFcon. The future of this group is uncertain. This group and the PC’s future group needs to have some synergy around it. At the shoulder meeting, there was talk of a lightweight DIP process.

The CDD working group’s goal was to have a ready proposal. This group can be redefined. But the whole process shouldn’t be siloed. There needs to be a tricouncil group to make sure whole process is being coordinated.

Conversations shouldn’t be siloed. There’s a lot of overlap. The main idea was to have visibility on what other teams are working on. We should focus on something really simple. This is along the idea of system demos.