2025-10-30 Product Council Agenda and Meeting Notes

5 min

Welcome & Announcements

@Jeremy Huff

• Sunflower CSP Released

Housekeeping

3 - 5 min

Liaison Updates

@Tod Olson , @Alexis Manheim , @Jennifer Eustis

TC:

• Pilot for eval of existing modules

• Support periods

• Dedicated discussion: conventions for and management of environment variables (affects dev & deployment)

CC: No Update

RMS: No Update

3 - 5 min

Action Item Review

@Jeremy Huff

Updates on Active Initiatives

5 - 10 min

Working Group Updates

@Jeremy Huff

The Community Priorities Dashboard
- In process of defining charter, refining a draft.

Community Directed Development Framework

- Met this week, not as far along.

RMS/PC Roles, Relations and Communication.
- Discuss handling Release, 80% done with charter

Announcements (@Jennifer Eustis)

New Topics

15 - 20 min

Consortia SIG Top 5 Priorities Presentation

@Lucy Harrison

Priorities:

1. [UXPROD-4998] Build a framework for generating bulk edit forms based on user-defined configurations

2. [UXPROD-4839] Allow user to "unshare" or demote a shared Instance to be a local instance

   1. Galileo dealing with this now. Many migrations included very local things like hardware, and need this ticket to clean up the catalog.

3. [UXPROD-4713] Enhanced inventory record suppression for Consortia

4. [UXPROD-4798] Ability to create centrally managed import profiles

5. [UXPROD-4825] Cooperative Collection Development notifications for last copy and subscription

Process:

Voted, and then refined based on discussion within the SIG. Have promoted the prioritization process, have had voting, but not a huge amount. Used votes to seed discussion.

Some factors in prioritization discussion included whether X was a prereq for Y (e.g. #1 priority enables the item that was #1 in voting), ensuring that priority tickets were defined enough to be acted upon.

Priorities are not set forever, could change over time.

Discussion of SIG Experience/Feedback:

For Galileo, not great timing as go-live decision is tomorrow; looks like it will become more useful going forward.

From Mobius, already live and useful process. Interesting because SIG is combination ECS sites and non-ECS sites.

Consensus: messy, but useful.

Cadence: annually or semi-annually

Any guidance or tools that would help?

• The SIG’s intuitive process seemed to work well for the SIG.

• What do Jira statuses mean?

• Some of our items have releases assigned, should we prioritize those?

  • Easy to de-prioritize tickets, priority list informs PO

  • Working group to take this up.

Need to close loop of communication, so priorities come to POs. Also useful as resource for community-driven development.

10 - 15 min

Begin Discussion on TC Support Cycle Decision

All

https://folio-org.atlassian.net/wiki/spaces/TC/pages/1187348628

We will record our response the TC’s proposal here: https://folio-org.atlassian.net/wiki/spaces/PC/pages/4883942

Summary

Current process is to support current version plus two previous versions.

Proposal is to make support based on date. Key idea is that underlying libraries have limited support period, typically one year. Recommendation originated in Security team. Coming up with Ramsons because Trillium is the first release where we have fewer than two release per year.

TC asking for endorsement from PC. PC is a stakeholder and this overrides the long-term and regular release recommendations. If there are functional issues, PC may change functional aspects of proposal.

PC Process

Begin discussion today, continue and vote next week.

Discussion

What does this override?

• PC Supports long-term release and regular release recommendations

• LTS recommendations (Long Term Support) [also contains the regular release recommendations]

What considerations go into setting the support dates? Spring Boot is the main driver, has two releases per year.

If we have another situation where a big delay puts us out of sync with 3rd-party support, can we revisit? Realistically, as a development community we cannot provide security fixes for software libraries that have gone out of support. Security Team can monitor and give alerts or make recommendations, but cannot spend development resources. If there are functional problem, e.g. bugs affecting data, could make functional fixes and mint new CSP.

Issues from product perspective:

• having insufficient support windows or time between versions to do upgrades will be challenging

Planning

5 min

Newsletter topics

All

10 min

Define agendas for next 2 meetings

All

• Check Jira board

• Check Calendar

• Seehttps://folio-org.atlassian.net/wiki/x/koARJQ