Review Tri-Council To Do’s from WolfCon. Ensure: clear scope owners timeline
| @Tom Cramer @Paul Kloppenborg | Tri-Council Meeting Notes - 2025-09-26. Agenda recap: conference debrief four models of software/community development AWS
Action Items from Tri-C-Meeting to follow up: Work on visibility of development requests / DIP proposal (PC) Create updated list of FOLIO modules with maintenance status (including orphaned apps) (PC). Develop dashboard for tracking Jira points and cost metrics. (TC) “Counting things” follow up from DC Summit (spring 2025) - (Jenn, Shawn, Tom C) Investigate Koha Model for community-driven development and maintenance (Lisa, Jenn, Tom T., Harry) Examine and better define Membership Value to inform a membership drive (CC) Convene AWS working group to draft cost sharing design and investigate feasibility of distributed hosting (in kind contributions of hosting env.) (Stephen, Peter, Wayne, Mark V. and/or Yogesh) It was asked how the group is sharing goals with the AWS-investigation group. This group is more on the issue of searching a new paradigma for alterative providers and needs; separate from the AWS-cost-investigation group
All to report progress at next tri-council meeting (Dec/Jan) To Do: schedule a meeting (ask other Councils about possible slots)
Line Item Contributions – engage with EBSCO (Paul, Tom)
Owners for all items? yes
Any other items? no |
Review CC To Do’s from WolfCon. Ensure: clear scope owners timeline
| |
After Tri-Concil meeting:
Community Council Meeting Notes - 2025-09-26, Agenda Items:
Membership Value Define concrete membership perks tied to infrastructure, training, and recognition. Reexamine tiers Differentiate from line item contributions.
Training Technical Council WG report on 3rd party licenses Latin American adoption Communications (deferred)
Action Items from CC-Meeting to follow up: Benefit Development: Survey of existing and potential members to gauge what resonates among possible member benefits (Shawn) Focus group at Mid-Atlantic UG meeting (Maccabee) Charter a Working Group to draft new definition of member benefits (Paul & Tom) Future (after membership benefits definition) – Membership Campaign: Group draft and lead outreach to 83+ non-member institution (ownership: defined later after 1c)
Invite FOLIO Membership Committee to CC review charge identifying FOLIO users? dovetail with member benefits & outreach?
The group is searching for a meeting with Co-Chairs (CC) to discuss further goals and the scope of the Committee. Training Program: Explore community-managed video and certification models (concept document and communitate to the Councils as potential member benefit) (Paul and Petra Schneider volonteer for a first concept draft) Licensing Working Group: Engage OLF legal resources on LGPL compliance (Paul & Tom to solicit input from OLF Exec. Committee) Latin American adoption – report from Karen (to be scheduled) - 5 Minutes Future Meetings: Revisit communications strategy, regional outreach, and developer engagement in conferences/events (get developer get together)
@spampell reaching out to Jesse about WOLFCon program committee. next meeting (quarterly) December or January. It depends on the availability of the council members.
The liaisons and representives of the councils should reach out to TC and PC and inquire about availability. |
Latin American adoption | @Karen Elena Jara Maricic | A large number of libraries in Latin America have implemented FOLIO, supported by EBSCO. They are very interested in sharing their expertise, lessons learned, and ongoing development work. They are currently in the process of translating the platform into Spanish. They advocate for stronger communication across countries and for strengthening the overall community. They have built strong regional governance structures and are pleased to have become part of the wider FOLIO community. |