CC was instantiated in April 2021
Focus so far has been on:
- Logistics
- Treasurer activities: Managing funding and membership dues is a substantial undertaking
- Funding
- Cover FOLIO "infrastructure" and fund resources formerly funded by Mellon
- infrastructure (AWS, GitHub, TestRails...)
- Established 3 groups:
- Solicit existing members; successful
- attract/sign up new members: many are involved but not yet committed/paying dues
- identify grant opportunities
- hopefully very fruitful, but also long-term: IMLS grant calendar is fall 2021 for 2022 procurement
- create a proposal for a project that aligns with the grantor, rather than general FOLIO sustainability
- Communication and Onboarding emphasis
- outreach, FOLIO forums, etc
- cuts across CC/PC/TC; CC to lead and form a cross-council group to move this forward
- Elections for Product Council and Technical Council
- votes close this Friday; targeting 2021-07-12 as first "new council" meetings
- Reviewing FOLIO Strategic Objectives to set our agenda for FY22
- make sure there is common understanding of these goals
- make sure activities and interests align with these goals
- figure out which the CC should lead vs participate in
What advice/questions/requests do TC have for the CC?
- Jeremy Huff : What is the TC's role WRT finances; we haven't been empowered to make financial decisions, but we sometimes are asked to assess financial impact of tech decisions
- CC feels TC should continue own AWS budget
- governance model clearly puts financial responsibility in the hands of the TC
- md331 (Deactivated): there's a bunch of infrastructure that is AWS, GitHub etc, but also people (e.g. people doing component development, people doing dev-ops, etc). Institutions donate people right now, but could re-task those people at any moment. Yikes.
- should a "core team" of those kinds of folks who keep the project running rather than just handling feature mgmt, be in scope for funding?
- current ops costs ~$135k; funding people is far more expensive
- not having this commitment this causes some discomfort among others
- current membership model has institutions committing people in these roles, rather than committing revenue
- Tod Olson: cross-module data sync is becoming a hot topic, e.g. bib data flowing through data-import; app interaction is looking at cross module issues; but these feel like manifestations of the same problem! A more monolithic architecture would remove some of this behind ACID transactions but remove some of the promise of FOLIO of separating concerns into separate modules. How do we get people to align on how they see this problem?
- is this a TC/PC thing? How could/should the CC be involved?
- Brandon Tharp : stating operational philosophies/decisions that FOLIO adheres to would be helpful to set expectations: level a playing field, then make decisions within that plane.
- RFC process to establish tech norms never really took off
- there is some motion on this from the exec PC side at present; Tod Olson to pursue this for now