2026-03-09 Community Council Meeting Minutes

Attendees: @Tom Cramer @Johanna Radding @Stephen Short @Rachael Kotarski @Vanessa French @Karen Elena Jara Maricic @Shawn Nicholson @Peter Murray @spampell @Kristin Martin @Maccabee Levine @Petra Schneider @Martina Schildt

Guests: @Kirstin Kemner-Heek @Kristin Martin @Mike Gorrell

Regrets:

Note Taker: @Martina Schildt

Discussion items

Item	Who	@Notes

Item	Who	@Notes
Note Taker		Note taker for today: Martina Schildt Note taker for next meeting: Stephen Pampell
AWS FY27 Costs	@Shawn Nicholson	The AWS Cost Group AWS Costs Review Group Home - AWS Costs Review Group - FOLIO Wiki met to review the FY 27 budget request. The proposed budget maintains the $30,000/month spending rate for Development, Testing, and Performance environments. Bugfest environments continue to be fully funded exclusively by EBSCO. ACTIONS: 1) Kitfox and Index Data will finalize the non-Rancher environment costs, 2) @Yogesh Kumar will send the spreadsheet to @Kathleen Berry the FOLIO Treasurer.
Announcement and Encouragement to Participate	@Shawn Nicholson	The Better Sample Data Working Group (BSDWG) of the Product Council is pursuing the contribution of a large FOLIO dataset from an implementing library, to use as the basis for a new FOLIO Bugfest dataset. The dataset depends on a successful anonymization process. The BSDWG requests that FOLIO’s governance Councils, as well as the POs, endorse and help distribute a call for development contributions from the community. The anonymization scripts written for proof-of-concept were successful, but more development is required before the scripts are ready to implement. Developer volunteers would be working with Lee Braginsky from EBSCO to finish and deploy the anonymization scripts on a test dataset. Needs and requirements Number of developers: 2 180 hours Languages and platforms: Java Python & Airflow (as an alternative, used in post-POC preliminary efforts ) FOLIO Schematool There are some institutions that are - if everything works as expected - willing to contribute their data to be de-identified.
Membership subgroup to bring revised charge for confirmation	@Mike Gorrell @Kirstin Kemner-Heek	Review of comments and thoughts: minor comments have been provided Open question: Is the name appropriate? We considered “subgroup,” “subcommittee,” and “committee” and determined that “committee” is appropriate given the standing nature of this group. Outcome: CC agrees to “committee” Outcome: CC approves the charge Membership committee asks for input from CC on goals for members meeting. Will join another CC meeting to discuss ideas. Membership Committee will create some Wiki pages as subpages to the CC. New members to the Membership Committee are welcome.
agenda items for the next meeting March, 23		The Release Management & Communication a working group of the Product Council with the idea of short blog style post of new functionality that is released with each flower release. (not confirmed yet) Trainings as members benefits (not confirmed yet) Both topics need confirmation - Paul will check and get back to CC.