Sep 26, 2025

PC 2025 WOLFCon Shoulder meeting notes

Goals for the next 12 months (review and prioritize)

https://easyretro.io/publicboard/p2nZ5pdHt3hnc6U7Mjf3IKbjzQm2/203e819a-96c7-4880-9a2d-464d5c9f0af5

Endorsing new functionality: The Jira process is new to the PC endorsement process and we also have the decision log on the wiki. Where should we record the decision? The wiki is where the TC currently looks for the PC's decision.

Going forward, the lightweight DIP pilot might help us decide how to handle this. Ex: Create a ticket in Jira, call for input, avoid confusion on when folks need to come to the PC, full lifecycle

Reporting as a core part of FOLIO – refine product vision and is it included?

Reporting is necessary for libraries, but there are two types: Functional and analytical.

Need to define what Core means and what are our end goals? Does it include reporting? CDDF definitions are in our future. Creating a list of apps/modules and putting them into categories. Is it better to do this at the functional level?

In CDDF, Core is platform and not functional, uses the term “components” and not apps or modules

What about a formal product vision? 

Should the PC add things to the priorities dashboard? PC would decide something needed to be done and then charge a group to do it? A SIG, perhaps?

The PC looks at the market to see where the product needs to go. Sets up a group with experts to follow this. SIGs are the ones in the hands on experience, though.

Need to keep looking at the big picture. App interaction SIG does this, but PC also needs to be aware.

Relationship between PC and RMS. RMS liaison is reporting back now to PC. What does the PC need from the RMS? More of a back and forth. Maybe make it easier to find info from RMS. PC could play a role in communicating certain aspects of the releases. Release notes are very long and in depth, PC can have a highlights/community release notes version. Translate what the RMS and POs are saying and send it out to everyone.

Review and update PC charter: Members agreed to return to this after we ID other priorities. What we do with the CDD might impact how we update the charter.

Knowing where to find documentation – the currently evaluate on product fit, but this shouldn’t be the only criteria. Documentation, for example. Sustainability should be factored in. Thin thread implementation on top of more thin threads. When will libraries get the fuller functionality?

Prioritize embracing the work of the CDDF and getting a lightweight DIP up and running. Set milestones for what to finish by the end of the calendar meeting.

Has anything changed since the Tri-Council meeting this morning regarding the CDDF? Next steps are:

• The CC needs to raise money.

• The PC is going to work on a lightweight DIP. Even if there are parts of the proposal in dispute, we can still do this.

• Surface amount of dev effort needed and the TC is going to work on that.

Milestones – how can we keep ourselves accountable? Check in in January at the Tri-Council meeting and when we will publish the priorities dashboard. Do a retrospective after we publish the dashboard.

For goals, use the format: Here is what we are doing and here is the larger purpose

Guide on how to get your feature developed. Maybe too much for this year. Or perhaps start out with lightweight documentation and flesh out more later? Also related to the DIP.

Track development from ideation through delivery. Goes with a lightweight DIP plan.

A way to show the value of being a member/part of the community. Associate it with member on-boarding. Here is how you get your functionality built.

Comment on the roadmap – too technical. PC’s role can be to translate what is in the Jira tickets.

Have POs talk to PC – explain larger tickets and what they actually will do.

Release digest – over 100 slides. Some release info material already being produced. Some dev teams do videos.

Index Data does a write up that is a translation of release notes.

We can also ask the SIGs about what is in a new release in their area. Align SIG reports with releases. What’s the big news in your area? Build that into the SIG report template?

Incorporate community tools into the wider product – LC tools, for example. Offline circ. Adjacent tools. OA module. NLA has a print service as well. Live on the outside, use APIs.

Is there a list of integrations gathered by Implementers SIG (Thomas) and Documentation SIG has a list of tools (Autumn)

What we are going to do:

1. Invest in the prioritization process/dashboard

2. Form a group to start a lightweight DIP process

3. Explore ways to communicate releases better