2025-04-24 Product Council Agenda and Meeting Notes

5 min

Announcements and PC Calendar review

all

• European Labor Day holiday on May 1 – cancel PC meeting?

  • May 1 meeting will be canceled and the planning meeting (April 29) will be canceled too.

  • May 8 - “Better Sample Data” update

  • May 9 - Friday - 11 am EST community update

  • May 15 - Tri-Council meeting during the Product Council time slot

• WOLFCon presentations – Reminder to submit your proposals by this Friday, 4/25!

  • Roadmap update / Architectural blueprint presentations - Discussed at yesterday’s TC meeting. Marc Johnson reported that there is a Google Doc we can get from Jen Colt. They are considering a number of sessions surrounding “where are we now”, “where do we want to go”, “how do we get there”? A large part of the conversation will cover effects of Eureka. Where are we ‘post-Eureka’ ?

  • Jesse will submit a roadmap proposal

• No other announcements

5 min

Eureka early adopters updates

@Jeremy Huff @Charlotte Whitt
GBV, Texas A&M, Index Data

GBV: a test tenant with FOLIO complete (as a monolith) is up and can be logged into. We have not loaded data yet.

Jeremey: They are close to have it running at TAMU. They have the UI built and backend built and deployed. The user configuration process for creating a password not working the way they think it should. They will be collaborating with the Kitfox Team from EPAM to get that part figured out. They made an effort to make sure the process is repeatable.

Christopher Spalding reported that GBV is up and running on Eureka. They are working on thin thread now to build rest of apps on Eureka.

35 min

Community Priorities

@Caitlin Stewart

Caitlin reviewed the DRAFT Community Priorities <https://folio-org.atlassian.net/wiki/spaces/PC/pages/931070022/DRAFT+Community+Priorities >

• Majority of priorities stated have not yet been developed.

• Charlotte - suggested going over every Jira listed to make sure there are stories for every open Jira. A development team will need this information. Caitlyn suggested making PC responsible for making sure there are user stories where needed. “We should ask for feature level - so only UXPRODs” (chat)

• Jennifer Eustis - Data import does not have a development team - that team is working on bulk edit. Jennifer also suggested keeping some of the working group apart as was done.

• Caitlyn asked: What is useful and for whom? A single ranking or multiple?

• Alexis - suggested make SIGs aware and say, in order to make this a priority, the Jira should be fully fleshed out with a user story and everything needed to move towards development. Caitlyn asked if it is still valuable to include something on priorities list if it is not complete?

• Kristin - Kristin suggested addressing SIGs directly to let them know their Jira’s referenced need more work in order to move forward. Kristin noted that because MM covers a large swath of functionality, not as much development has happed for that SIG. She recommends keeping the working groups for MM separated to offset the needs for development.

• Concluded that UXPROD is the appropriate level for identifying priorities.

• Jennifer Eustis confirmed that there is a lot of work needed for MM and many of its facets. How can things like data import needs be prioritized and how can PC help?

• Caitlyn - Should the PC submit their own priorities, or should we just pull from the community priorities?

  • Jennifer - We need to find a balance and have an equitable approach. How can we measure the need of one SIG against the need of another SIG?

  • Alexis - Would be helpful to know the technical debt.

  • Jennifer - Do we need to talk about a baseline for FOLIO functionality again? A baseline would help to identify gaps and then help establish priorities.

  • Kristin - Can we find gaps that are not reflected in current priorities list.

  • Brooks - “For a formal, project-level system to pool those resources for targeted work.”

  • Alexis - Addressed the difficulty of onboarding developers, and doesn’t think we have solved that problem.

  • Charlotte - “Not to mention half the time to get the development environment up and running”

  • Marc - Onboarding is an ongoing challenge. There is a long lead time

  • Brooks - “Some kind of “retainer” arrangement with one/some of the existing FOLIO development shops?”

  • Christopher Spalding - There is a CC subgroup on changing the model so multiple organizations can join to pool money towards a development project. This group will be presenting this Monday at the CC.

• Caitlyn next step:

  • Two dashboards: One for PC priorities, second for interest groups' top five. Jira’s without UX Prods or fleshed out prods will be flagged. This will be revisited

5 min

Future topics

all

Better Sample Data in FOLIO Working Group would like to give an update to the PC on May 8