Reminder: Please copy/paste the Zoom chat into the notes. If you miss it, this is saved along with the meeting recording, but having it here has benefits.
I shared the "TC Wolfcon 2025 brainstorming" doc, explained (some of) these topics would need participation from CC (and PC) since the issues are more in their domains.
CC introduced a new lower-cost "Friends of FOLIO" contribution option for more fundraising. Membership subgroup is separately working on better articulating the value of FOLIO memberhsip, for view in a few weeks. Several libraries looking for reasons to pay more.
CC also working on a draft letter to send to new customers / potential community members. Comments open until Friday.
Drafted a vision statement for the website
The Future Of Libraries Is Open Community as 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. Product as Mission: (Guide/influence/govern/whatever)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.
Discussion about various aspects. Re "The community directs the development of FOLIO", folks agreed this is not the current reality, but some wanted it there as an aspirational statement, others did not even think it should be an aspiration. I brought up the governance guiding principles (about community, and also about local decision making authority) and asked CC for further clarity on this to inform TC, i.e. whether we should be aspiration or current-reality-based, and what those aspirations are.
Line item contributions via EBSCO and IndexData hosting.
Election voting will be open to people who have logged into FOLIO's Jira/Confluence since the cloud migration. Not based on Slack usage, since Slack workspace is scoped to OLF not FOLIO.
Community support for FOLIO infrastructure. What infrastructure should be community supported, as opposed to a requirement for whoever supports dev team(s) etc. Earlier discussions were inconclusive. Committee needs more voices on this, Mike G. will participate. Others should as well, active attention is important.
Craig McNally asked for volunteers to help update the RFC process documentation and update the existing RFCs to include stub entries. None were forthcoming
Still need to do this
Craig McNally will reach out to RFC proposer to create stub wiki pages that refer to the github RFCs
Still need to do this
Notes:
FQM vote on Wednesday - what is the meaning of the vote - do we consider implications or just review based on the RFC itself?
Consider impacts of non-acceptance?
Removal vs documentation vs special nature of FQM
Can change text in RFC
Other module wanting special privileges could be a separate vote when it comes up
How much does the scope of our 'power' matter? Can we address concerns with this at all?
Mixing together RFC and module processes by mistake? RFC is an independent process voting on an architectural design choice
If this is just about documentation we didn't need to do this whole process
RFC gives TC an opportunity to discuss the architectural changes
Is this a bookkeeping exercise or does it have impact?
TC has power to make architectural decisions but there are practical limitations
Do we need to know impacts before voting?
Schema issue is an architectural change being done here
there was a conditional acceptance because we needed it but we still needed to know how it worked. so this is documentation in the sense of backfilling what should have been there originally
documentation reflects current state, way of completing the RFC/acceptance
Craig McNally asked about whether we could update the calendar page. Marc Johnson advised that we are waiting for a Trillium timeline. Craig McNally will follow up with Oleksii Petrenko about when the schedule might be published