| | |
|---|
Identify Note Taker (1 min) | | @Peter Murray this week; @Stephen Short next week |
Announcements (4 min) | @Paul Kloppenborg @Tom Cramer | Tri-Council Meeting on August 28 at 10 AM ET (during PC timeslot) Tri-Council & Community Council meeting on Friday, Sept 26 at WOLFcon from 9 AM to 4 PM Kansas City (CDT). Tri-council first, then Community Council in the afternoon. CC Member contact info: CC members please add your email & Google Account
|
Call for FOLIO Manager to replace Jesse K. (5 min) | | Context: Jesse steps down mid-September Duties: The FOLIO Project Manager is one of three named roles in the agreement between the project and the Open Library Foundation (the other two are secretary and treasurer). Primary liaison to the Open Library Foundation; sign formal documents; attend biweekly/monthly officer calls; maintain Slack channel. Call for Nominations: Open now through September 5; candidates volunteer; if >1, CC will conduct a lightweight internal selection. Jesse to assist with onboarding.
|
Report & next steps on shared reflections on software development models discussion on August 11, 2025 (15 min) | | Working Document on Shared Reflections Emerging solution buckets: Membership growth campaign Software-development marketplace platform Formal proposal process (DIP) for community-driven development Lower technical barriers to code contributions Allocate central funding for key roles (QA lead, release manager) Continue AWS hosting cost optimizations
Next Steps: Draft a positive “future state” vision for the next meeting, then map solutions to problems at WolfCon.
|
Line Item Contributions proposal (15 min) | @pampell | Proposal: Opt-out line-item fee in Index Data and EBSCO hosting contracts to fund community efforts (e.g., Bugfest, QA). Mechanics: Tiered fees based on service type (SaaS, implementation, development). Annual pass-through reporting; a public list of contributors to ensure library funds are indeed passing through to the project. Institutions may opt out.
Broad Vendor Alignment: Mike Gorrell confirmed Index Data’s commitment; EBSCO’s agreement reported. Discussion: Need a unified community letter explaining the rationale and benefits. Track opt-in/opt-out rates and reasons annually. Clarify treatment for project members vs. non-members & for self-hosted consortia.
Next Steps: Draft formal CC letter or MoU to Index Data/EBSCO; refine procurement-law guidance; finalize by WolfCon.
|
Tech Council Dependency Licensing | @Maccabee Levine | Issue: K-Int maintained dependencies under review. The development team is pausing technical upgrades pending the resolution of sustainability governance concerns. Implication: Concrete example of marketplace/governance gaps; warrants deeper CC discussion & alignment with core-problems work.
|
Prep for Tri-Council meeting on Aug 28
(10 min) | | |
Prep for Tri-Council & CC meeting at WOLFcon (10 min) | | |