2024-01-08 Community Council Meeting notes

Date

08 Jan 2024

Attendees

Simeon Warner

Guests: Maccabee Levine, Ludwig Liebl (BSZ),

Regrets: Mike Gorrell Kristin Martin

Discussion items

Item	Who	Notes
Treasurer's update	Paula Sullenger	Delayed from before winter break All membership fees are paid! Budget looks good
Outreach and Marketing WG	Boaz Nadav Manes	Ref. COM WG charge from 2023: https://docs.google.com/document/d/1ZTOUOhwUtWaEjywKkS0cA41t1h0Wzhv_F9FR5Cyhqzk/edit
Other Business
Backlog of topics to discuss
FOLIO Developer Advocate	Mike Gorrell	Before break we had 2 candidates (both from outside FOLIO)
Action items to follow up with
FOLIO System Administration and DevOps	Mike Gorrell	Index Data needs to pull back from some System Administration tasks - we will end our support by March 1, 2024. Announced and first discussed 2023-11-27 Community Council Meeting notes, next step is a list of duties to transition, then develop a plan, aim to have candidate teams by February 1.
Community survey	Tom Cramer	Survey closed Friday Sep 29. Tom shared a first draft / summary of grouped items in 2023-11-27 Community Council Meeting notes NEXT STEPS: Tom, Maccabee, Jesse - will produce summary to share early in the new year All - feel free to add comments as you read/review, can also suggest new high-level categories
Community communication norms	Tom Cramer Ian Ibbotson (Use this one) Christopher Spalding	From 2023-08-25 Meeting notes idea about changing the ask on SIG's! Information and discussion in the SIGs and a transport of summaries to upper levels asking how communication flows across the project, new people don't know, need some guidance for the project no update
Architecture group	Ian Ibbotson (Use this one) (liaison to CC)	Addendum from Ian - 28th Nov. I didn't think it was worth taking peoples time in the call with an update so posting here - Formally: the group has met twice and is trying to define it's scope - I don't think there is consensus yet. Informally: I felt the last meeting we had was possibly one of the most constructive governance meetings we've had in a long time. A lot of the structural challenges we have were talked about (The way the three-council split can lead us into undecidable propositions). I felt we strayed into some old archetypes "The end users aren't consulted", and "Concern over derailment of the TC process". But then it felt like we started to synthesize a scope for a tri-council group as a group tasked with understanding a proposal, communicating it to the wider community, gathering and organising feedback, and then communicating that feedback to the source. TBC but I think the meetings are worthwhile - we didn't get into the detail of the app architecture itself, but progress on the question of what a tri-council group is/should be and how it relates to this specific question.