2025-05-12 Community Council Meeting Minutes

Note taker

@Simeon Warner

Note taker for May 23? @Edwin Pretz

NOTE CHANGE OF NEXT MEETING: Friday May 23, 10am ET

Updates / Checkins

@Simeon Warner

• @Joseph Grobelny @Boaz Nadav Manes - Working on elections, nominations forms will go out today

Budget discussion

@Kathleen Berry

• Draft budget from treasurer based on current spending patterns

  • Kat presented 3 2026 budget scenarios. Two dip into reserves.

• Discussion

  • Dev ops will be kept at $100k per year.

  • Biggest issue is still AWS: we shouldn’t be using reserves for annual operations.

  • Its not confirmed which of the AWS-related costs will continue to be covered by EBSCO.

  • Texas A&M looking at an option for development teams to unbox a FOLIO test environment, so they can self-host and pay for those costs locally.

  • Suggestion that we set a date to sunset use of FOLIO budget for AWS for all community dev environments, giving a concrete tast for the community.

  • Savings could be put towards staff to support coordination.

  • Move to approve a 4th budget option subject to confirming two AWS line item coverage from EBSCO. This covers $380k in AWS costs, compared to Scenario 1 which covered $360k. It would leave reserves intact.

  • Is a flat membership income estimation realistic? It’s based on discussions to date RE membership.

  • FY26 will be the last year of a 5-year membership from Chinese institutions.

• Vote: Agree to the budget as Kat presented with $380k for AWS expenses contingent upon:

  • EBSCO continuing to pay for the two items they currently pay for ($101,400);

  • the intention to resolve by the end of FY26 the costs for shared community infrastructure vs development teams supporting their own development environments ; and

  • EBSCO will continue to pledge community tech support of $30k

• The proposal is approved.

FOLIO Vision Statement

@spampell @Joseph Grobelny @Shawn Nicholson @Jesse Koennecke

From 2025-03-18/19 CC, PC & TC chairs and Officer In-Person Summit. Held over from 2025-04-28 Community Council Meeting Minutes to make a decision on whether “Guide” the Community or “Directs” the Community development is the best word choice

• There were no objections on adopting this vision statement, and so the document is adopted.

• Stephen will speak to EBSCO about getting the statement online.

• Adopted Mission and Vision statements:

  • Vision: The FOLIO community is open to all. Consisting of libraries, developers, vendors, consortia, and networks, we work together to build and maintain an open source library services platform that enables innovation and delivers both traditional and new resource management capabilities to libraries across the world.

     

    Mission: The community directs the development of FOLIO as an open source platform for libraries that provides choice and protection from vendor lock-in. Its modular, adaptable architecture provides a stable platform to meet current needs while being forward-thinking, empowering libraries to lead innovation, respond to change, and shape their digital futures.

FOLIO Contribution Network

@Mike Gorrell

• Aim is to ensure organizations get a cut of dues to support maintenance.

• It will be tricky since a lot of maintenance occures during active development, and confirming the socpe of maintenance is difficult.

• This will be discussed further on May 23: CC should comment on the document in the meantime.

FOLIO Community Blueprint

@Simeon Warner

From 2024-10-14 Community Council Meeting Minutes  everyone to review/comment on draft:

• Where do we want to take this?