2025-03-27 Product Council Agenda & Meeting Notes

5 min

Announcements

all

Reminder to vote on FOLIO Governance Model revision by Friday (see PC only slack). The changes to the document in regards to voting was accepted.

5 min

Eureka early adopters and Permissions updates

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

Jeremy: Had some recent success. Things are going along and having conversations internally. It will be difficult to endorse it if it is not working. There has been discussion about the level of deployment operation. The idea is to deploy something in a repeatable and consistent way. They are still on target. GBV is a little ahead of Texas A&M.

10 min

Report on DC Summit

@Caitlin Stewart

The CC and Council Chairs had a summit. The original goal was to look at the membership model and how to grow it. EBSCO will be scaling down with their development teams. What does a sustainable and mature FOLIO look like? A small group will be working on vision. There will be short term asks for financial support. There is also a goal to develop a long term model of responsibilities and community (infrastructure to support community development). There is to develop a vision of a healthy development network (like the marketplace). There is a rapid turnaround and should have updates in the next month.

Martin: These topics will be discussed. How and where will they be discussed? We are in charge of the product version. How will this happen? The vision is an overarching vision for the community. The discussion was Community Council oriented. We need to look at our charter. On Tuesday, we mentioned that having PC liaisons on some of these working groups.

Martina: This information is on its way. We need to talk about the visions for the product at WOLFcon.

Martin: 2nd this. WOLFcon is a good place to talk about these working groups and include the whole community.

Alexis: Was the idea to talk about this at WOLFcon? The short turn around time was to be able to discuss in Community Council. Kristin is our liaison to Community Council.

Jeremy: I appreciate the distinction. It’s exciting to hear about a community vision. Do we have plans for a product vision?

Caitlin took notes to plan on a workshop or series of workshops.

25 min

WOLFCon session planning

all

The plan is to have council meetings on Friday.

Jeremy: One of the questions to answer is what community developers work on? Is it an aws run by the community? There are self-hosting members that have hosting environments. These institutions could have in kind contributions. The community development depends on this (cost, coordination, resources).

Charlotte: Are you talking about this community development instead of FOLIO snapshot? It’s more the at will environments or the rancher ones. At IndexData, developers have FOLIO on their local machines, and then have one to do more testing and then push to the community.

Caitlin: This is a good topic for a workshop. How do we quantify in kind resources like development hours? It would be good to have all 3 councils.

Martin: This community development idea has a lot of facets. Maybe we could split this up into multiple sessions. We are lacking an idea of what is community development. Is it a FOLIO module or something around FOLIO?

Please add all of your ideas down.

Jeremy: What do we mean when we say community development is important. Does the community direct development? It’d be great to have the answer to that question be yes

Alexis: We need to define community development.

Jeremy: Use the term community directed development because community development is already happening.

Charlotte: We started out with this core functional and platform team. Maybe it is time to go back to this idea.

Alexis: In reading through the charter, there is a line about a core team to maintain the platform. This doesn’t exist.

Jeremy: This was the original approach to development. It’s worth looking at why this original team didn’t last. It was harder to streamline work as well. Strong management of a community team would help it be more successful.

What about product vision?

Jeremy: People who are interested in the proposals to work asynchronously on them.

Caitlin: We should get as much done asynchronously as much as possible.

Jeremy, Martin, Charlotte will work on the community develop proposals.

Should we look at the charter to look at the product vision?

Charlotte: We start with the product vision. We shouldn’t start with the charter.

Martin: I agree with Charlotte. For WOLFcon, the product vision would be a good place to present it there. The charter can be discussed internally.

Tod: It’s probably right not to focus on the charter. The charters don’t line up with how responsibilities are executed. It might be good to line up the responsibilities with what one excepts from an open source project. How do we line up the charters with reality? This is more a tricouncil activity.

Alexis: At the DC meeting, there was a review of open source projects. There is nothing like FOLIO. This needs to be a tricouncil thing.

Caitlin: What if we took some time to start an asynchronous product visioning session? Yes. this makes sense.

Martin: Do we have to hurry?

Caitlin: We’re talking about community development. This and other ideas link into product vision. Having this discussion soon presents opportunities.

Martin: If we need a vision right now, that we’ll rush things. Working on the vision should be an ongoing process.

Alexis: We don’t want to rush things.

Caitlin: Proposing an iterative process over 6 months to refine the vision and use WOLFcon as a way to get feedback.

Alexis: We’ll work on it. The proposed vision will be presented in WOLFcon. We can use a virtual board. In addition to the charter, we need to look at the vision.

Is the calendar working? We’ll talk about this next week.

5 min

Future topics

all

Calendar, Community-wide prioritization