/
2025-03-18/19 CC, PC & TC chairs and Officer In-Person Summit

2025-03-18/19 CC, PC & TC chairs and Officer In-Person Summit

Date: 2025-03-18 (full day), 2025-03-19 (morning)

Location: Cornell in Washington, DC, USA

Present:

  • Caitlin Stewart (PC co-chair)

  • Simeon Warner (CC co-chair)

  • Shawn Nicholson (CC member)

  • Stephen Pampell (CC member)

  • Jesse Koennecke (FOLIO SMLLC Manager)

  • Kirstin Kemner-Heek (CC member, FOLIO SMLLC secretary)

  • Jenn Colt (TC co-chair)

  • Maike Osters (CC member)

  • Alexis Manheim (PC co-chair)

  • Tom Cramer (OLF President)

  • Mike Gorrell (CC member)

  • Christopher Spalding (CC co-chair, OLF secretary)

  • Joseph Grobelny (CC member)

  • Boaz Nadav Manes (CC member)

  • Kat Berry (Treasurer)

  • Rachael Kotarski (CC member)

Regrets, unable to attend:

  • Craig McNally (TC co-chair)

  • Edwin Pretz (CC member)

  • Johanna Radding (CC member)

Goals

  • Establish budget priorities and financial sustainability plans.

  • Define a clear vision for the FOLIO community’s future.

  • Evaluate structures for sustainability.

  • Develop strategies for outreach, membership growth, and engagement.

  • Align membership levels and funding models with community needs.

  • Strengthen collaboration and contributions beyond existing commercial partnerships.

Outcomes and action items

  • Consensus in discussion that the community should have have a key role in the sustainability of FOLIO. We need to better articulate what is needed for sustainability and need to increase funds raised. This will best be done by increasing community participation with a broader base of institutions.

  • AGREEMENT of CC by vote that we are OK to encourage representatives to stand for Council positions with a promise of FY26 membership (membership is a requirement to be seated)

  • Small group to develop short-term FY26 changes in membership model/levels - Simeon (lead), Kat, Steven, Kirstin.

    • Think about a mechanism for collecting information about contributions (perhaps option for MOU or other reporting)

    • Do ready for April 28 CC meeting

  • Longer term contribution/membership/budget/community responsibility modeling - Christopher (lead), Kat, Simeon, Shawn, Mike

    • Suggest P&L approach breaking down income streams and expense types for dev/maintenance/infra/etc/

    • Christopher (with input from Mike) to do pre-work on costs

    • Start after April

  • Develop approach to measure what the community does and how much it costs now - Tom, Jenn (lead), Shawn, Kat (fly on wall)

    • Want to develop process for ongoing measurement

    • Counting has implicit suggestion of what has value

  • Form group to create a vision for how to cultivate an active healthy software development contribution network: Mike (lead), Boaz, Stephen, Christopher

    • First draft by April 28 CC meeting

  • Group for vision statement - stephen (lead), joe, shawn/claude, jesse

    • Deadline 14th april to share at CC meeting

    • Christopher will ask whether Hannah Murphy can join

  • TC is working on plans for app approval process; still need to get around to platform definition but will likely deal with bugfest and testing plans first

    • Ongoing

  • Agreement that it is too early to ask PC to do further work on App grouping. TC is currently working on App specification and these proposals will come to PC for review, app by app.

  • Refinement of letter to non-member institutions - Shawn, Joe, Kat

    • Include possibility of end-of-year donation

  • End of year contributions to be pushed via the OLF newsletter. Ask to Hannah Murphy (Christopher) to include.

  • Line item contributions via EBSCO and IndexData hosting - NO ACTION YET

    • Need a description of how funds used

    • CC needs to send to vendors as proposal

    • Naming: 

      • Suggest not membership

      • “Free as in kitten not beer fund”

      • Community operations / test env. / sustainability

    • Scope questions

      • Does it include support for staffing?

      • Need to think about longer term plan so we don’t keep coming back with additional asks

    • Timeline: before WOLFcon

  • Develop plan for developing blueprint for FOLIO community and software ecosystem and marketplace - Tom (on the plane)

    • Want to have timeline of when things need to be developed

Community council will follow up on actions

Related content