2026-03-05 Product Council Agenda and Minutes

5 min

Welcome & Announcements

Linked Data Editor for Data Import endorsed

• https://folio-org.atlassian.net/wiki/spaces/PC/pages/1723367425

• Passed with strong support

Daylight Savings Time Reminder

• Beginning next week: daylight saving time time slot shifts for EU and others

WolfCon Call for Proposals (Jennifer)

• Due March 25.

• Guidelines now available.

• Pre‑conference proposals should go through @Thomas Trutt

Liaison updates

TC: no meeting this week

CC (Alexis)

• https://docs.google.com/presentation/d/1Q7SpEhuKH_MlR2Uz1HxzkamEuM-h5Gc1f44l7IH4D5I/edit?slide=id.g386ad7f06f3_0_10#slide=id.g386ad7f06f3_0_10

• Discussion focused on membership benefits, especially enhanced training offerings:

  • Ideas include member‑only shared training materials or curated demo videos.

  • SIG demos could be repackaged into shorter training modules.

  • Work is exploratory—evaluating feasibility and workload.

• Additional context from RMC WG and Data Import SIG

  • Both groups also discussing training, documentation, and member‑only vs community‑wide support.

  • Potential opportunity for coordination with CC.

Release Management Stakeholders (Jennifer)

1. Sunflower CSP 6 expected next Wednesday (3/11).

2. Ramsons CSP 9 scheduling TBD; team focused on Sunflower.

3. Migration ongoing for Spring Route 4 / Spring 7 / vert.x

4. Umbrellaleaf target date still TBD.

Housekeeping

10 min

None this week

Updates on Active Initiatives

10 min

Release Management & Communication WG update

@Jennifer Eustis

1. New press-release style template created for http://folio.org updates.

2. Considering LinkedIn developer spotlights.

3. Need clarity around:

   • Who owns http://folio.org content

   • Who manages social media

   • Who approves communications (Community Council? A tri‑council group?)

4. Current communication process is bottlenecked; suggestion:

   • Establish a tri‑council outreach/communications group for quick approval and coordination.

5. Simeon Warner is the new FOLIO project manager (per Alexis).

6. Recognized that current Release Digest is unsustainable; PC and CC may be able to assess/assist.

New Topics

20 min

WOLFCon PC Submissions

Subgroup Presentation Plans

• Slides on the planning to be presented at CC next Monday.

• Data Import SIG

  • Considering presentations on data import roadmap + documentation roadmap.

• Release Management Communication Working Group

  • Aim to have deliverables completed by WolfCon; may present outcomes.

• Community Priorities Dashboard Group

  • Planning a deliverable/update for WolfCon; meeting after PC.

• DIP / Jeremy’s group

  • Expecting to submit a proposal?

• Tools & Integration / Implementers SIG

  • Joint presentation with Implementers SIG (Martin & Charlotte), draft slides.

Additional Suggestions

• Presentation on the Prioritization Process.

• Use WolfCon for in‑person discussions that do not work well remotely (Tod), e.g. architecture previews, technical debt review.

20 min

Experiment: review current scope of Umbrellaleaf features for potential PC review

@Caitlin Stewart

Pre-planning

During this Thursday's PC meeting, we are going to move our conversation about proactively monitoring upcoming releases for new development that needs PC input to the next level by experimentally reviewing the current scope of Umbrellaleaf together. Hopefully we will learn a little bit about what is in the release, but the main goal of this exercise is to help us determine whether this is a good strategy for PC and what the process should look like.

• I propose we use this Umbrellaleaf dashboard and use the PC Values as a mental checklist for whether a feature might need PC input

• We are not going to be able to review the whole scope in one meeting, and since this review is experimental, I recommend we exclude features that are in Open, Draft, or Blocked for Thursday's meeting.- that's currently 31 features. If anyone feels strongly about doing this a different way, please let us know.

• SIG Liaisons, please reach out to your SIGs and ask if there is anything specific in the Umbrellaleaf release that PC should look into.

Questions to consider during review:

• Process

  • What needs to happen before PC reviews release

  • How does the PC review the release?

    • What status should trigger review

  • How does PC communicate with TC, SIGs, POs after release is reviewed?

  • Is it iterative

• Criteria

  • What are we looking for? Is it Dependencies? Opportunities to affect change? use PC values as checklist?

  • How do we advocate? Ask about what isn’t there

Meeting discussion

Goals

• Shift PC’s evaluation/endorsement earlier, ideally before development begins, so feedback is useful and not post‑hoc.

• Test out some potential approaches for this work.

Proposed Excercise

With PC Values as a guiding rubric, review Umbrellaleaf dashboard (see filtered dashboard below) to identify early features for discussion; is this a feasible approach for PC to adopt?

• Here is a filter that includes all features that are In Refinement, Analysis Complete, In Progress, or Closed

Observations

• Release scopes change frequently; early lists are fluid (per Khalilah).

• Still valuable to begin early engagement.

Where to Look in JIRA?

• “Open” status best indicator (per Thomas).

  • Indicates features refined and ready for dev.

  • “In Refinement” varies widely by PO; not consistently used.

  • Many features are “NFRs” (technical tasks), not user‑facing features.

• Some large parent features (e.g., “tech debt and bug fixes”) contain smaller tasks of real impact.

Practical Challenges

• 130+ issues in release; not feasible to review all synchronously.

• Some SIGs already deeply aware of their functional areas; PC’s strength is cross‑functional awareness.

Possible Processes

1. Liaison‑Driven Review (Jennifer’s suggestion)

   • Liaisons monitor their SIG’s roadmap dashboards.

   • Bring notable/impactful features to PC.

2. Divide & Conquer (Martin’s suggestion)

   • Export issues → split among PC members.

   • Each person reviews ~5 issues; ideally double‑assigned for redundancy.

   • Bring only notable ones forward.

3. Identify High‑Impact Categories
   PC may focus on features with:

   • High impact across institutions or workflows

   • Cross-app dependencies

   • Consistency implications (e.g., Delete behavior, search patterns)

   • Architectural ripple effects

   • New apps or major new functionality

Examples of Cross‑App Consistency Issues

• Delete functionality—handled differently across apps; unclear standards; DR04 recommends unified approach.

• Search patterns differ across apps (wildcards, syntax).

• PC could help articulate product‑level “style guide” expectations.

Next Steps

• General agreement: systematic early review will benefit PC’s evaluation, release notes coordination, and product coherence.

• Caitlin will consult with Jeremy and Charlotte on:

  • When PC should begin the Umbrellaleaf review

  • Whether to divide tasks, use liaisons, or combine approaches

  • How to schedule review sessions

• PC will revisit with concrete plan in future meeting.

Planning

5 min

Newsletter topics

10 min

Define agendas for next 2 meetings

• Check Jira board

• Check Calendar

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