2025-12-04 Product Council Agenda and Meeting Notes

5 min

Welcome & Announcements

@Jeremy Huff

• SIG Reports are due on the December 18th (not the 4th)

• @Caitlin Stewart is resuming co-chair duties. Thank you @Tod Olson and @Alexis Manheim

Housekeeping

3 - 5 min

Liaison Updates

@Tod Olson , @Alexis Manheim , @Jennifer Eustis

CC: CC meeting on Nov 24th

Qulto Monguz new FOLIO contributing member (Hungarian vendor)

Continued discussion on value of membership. Looked more closely at the 3 most voted for items of the list of 14. Three that got the most votes were Development priority influence (needs structure and resources behind it), Technical expertise access (One-on-one access to community experts for specific technical questions, could be around subject matter expertise, functional expertise, or technical expertise) and Training materials and resources.

Open items for Councils from WOLFcon. Nine listed, two belong to the PC (1. Work on visibility of development requests / DIP proposal and 2. Create updated list of FOLIO modules with maintenance status (including orphaned apps). Reports on all of these will be presented at the next tri-council meeting (to be scheduled for sometime in mid-January.)

TC:

• Proposal to upgrade version of Docker in build environments

• Discussion of technical options for handling tenant-global configuration. Weighing simplest, immediate fix vs modifying or adding API for better long-term positioning.

• Related to support windows and third-party libraries: Discussion of whether to use Spring Boot release candidates (RC) during development as a way of having a longer support window. RC becomes production sometime late in the dev cycle, and is supported further into the future. Decision: bring in RMS as stakeholders.

RMS: Ramsons CSP 9 might be delayed to early January. More information to come. The group is currently working on the roadmap dates for Trillium and the spring calendar.

3 - 5 min

Action Item Review

@Jeremy Huff

Tabled

3 - 5 min

Calendar Calming Proposal

@Charlotte Whitt @Alexis Manheim

• Thanksgiving holiday resulted in a work week with few meetings and a lot of progress on tasks for European colleagues. This was really meaningful and helpful!

• Many SIG meetings are cancelled, often just a couple of hours ahead of time. This gives an hour back to attendees, but makes it hard to plan ahead of time.

• Could the FOLIO community attempt a pilot of designating certain windows of time or given weeks that should be meeting free?

  • This could begin with the SIGs, and perhaps the Councils too.

  • Stanford University does this on a quarterly basis; they have found this really valuable.

• Another idea: setting aside time in meetings for housekeeping, task time, etc.

• Discussion

  • TC has a lot of work and meets twice per week; the Monday meeting has become a business meeting with routine topics/tasks, while the Wednesday meeting is dedicated to discussion.

  • Most FOLIO community participants also have responsibilities at their institutions or vendor workplaces and FOLIO time demands can be difficult to manage.

  • Concerns about getting everything done in a timely way; TC has a lot on its docket, for instance.

• Generally there is interest in exploring this; @Charlotte Whitt will bring a more formalized proposal for a future meeting.

Updates on Active Initiatives

5 - 10 min

Working Group Check-in

All

• Community Dashboard group met with Product Owners; discussion was productive. See notes and follow-up activity here.

New Topics

5 - 10 min

Support SIG Presentation

@Jaleh Fazelian

• Jaleh is from University of Missouri, longstanding member of the Support SIG

• Slides:

• Support SIG reviews newly submitted Jiras for bugs, ensures each one has been assigned the correct priority and that the appropriate product owner has been tagged

  • Also uses comments to ping stakeholders and ensure the issue is getting attention and moving forward in the resolution process

• Trends observed:

  • Fewer Jira tickets overall, improved turnaround time

  • Too many service patches, some frustration from users around that

• Question: Would Support SIG be willing to share insights with PC regarding larger observed issues, development needs, etc.?

  • Definitely open to this

• Question: Are there longstanding unresolved pain points or issues on the SIG’s radar?

  • Yes. SIG wiki tracks long open tickets that we periodically review and continue to ping stakeholders for status updates.

• Your questions are always welcome – reach out to us in Slack or at our weekly meeting, Monday 10am ET

10 - 15 min

Working Group Charter Review: RMS/PC Roles, Relations and Communication

@Autumn Faulkner

• Charter final draft

There have been good discussions about the scope of the working group. The primary focus is how RMS drives priorities and timetables. As we learn more in our environmental scan, we’ll propose recommendations for governance, hierarchy, and communication. We want to document how things are happening now, make recommendations and updates to charters and process, and improve communication.

For translating UXPRODs into real life functionality, on the dashboard, it is just tickets. What does this mean in terms of functionality? How is this going to help? What is the real life functionality that these issues bring to FOLIO as a product?

Is there a need for a technical writer? Yes there is a lot of documentation. Could we recommend new roles if those help with communication and documentation?

As we are thinking of each new release, we may want to think of permanent roles. We need to think of the skills needed for these roles. We could have technical writer to write up the digest in a human readable manner. There could also be a QA lead who could rally people to test.

Planning

5 min

Newsletter topics

All

• Pausing on this for the moment as Caitlin is still determining the status of some initiatives after time away.

10 min

Define agendas for next 2 meetings

All

• RFID App Development presentation slated for Dec 11, 2025

  • See demo of app functionality in Implementers SIG meeting recording from Nov 4, 2025

• Also for Dec 11, 2025

  • Calendar calming

  • Unresolved action items