...
Boaz Nadav Manes
Tom Cramer
Ian Ibbotson (Use this one)
Christopher Spalding (later)
Guests: Maccabee Levine, Ludwig Liebl (BSZ), Ian Walls
Regrets: Mike Gorrell Kristin Martin
| Item | Who | Notes |
|---|
| Treasurer's update | | Delayed from before winter break - All membership fees are paid!
 - Budget looks good
|
| Outreach and Marketing WG | | Ref. COM WG charge from 2023: https://docs.google.com/document/d/1ZTOUOhwUtWaEjywKkS0cA41t1h0Wzhv_F9FR5Cyhqzk/edit - Working group reporting to CC, 7-8 members
- Definition of themes per year and follow up
- Rachel and Boaz are founding members → ACTION ITEM: find volunteers
- marketing profs → we need professionals!
- FOLIO experienced people
- people from vendors
- 1 h/week would be the effort
- 2024:
- Focus on Innovation
- Youtubes, forums, global insight
- WolfCon 2024: how to attract UK institutions? Involve JISC?
- Interested persons shall address Boaz for next steps!
|
| Survey results | | Grouped list: https://docs.google.com/document/d/1jqETlhc3x5-JLGrKYG0u3ppilVMefycbrSsXrBfr9WA/edit#heading=h.m83ixy3abjcu - end - Toms question: which next steps to do for CC are useful to make use of the results of the survey?
- Paula: From the list: FOLIO governance, especially when it comes to the budget, is opaque. It has been a long while since we've pointed anyone to the Finance pages
- Maccabee: birng the list into a formalized form, publish it, folow up each year
- Boaz: publish who is in charge for what actions
- Prioritze areas of work the community cdecided to pick up
- Tom: here is a work in progress tracking sheet from last year: https://docs.google.com/document/d/1BVTrXq4b098uAtcDL3ZLIJan65dIIbaNY1_hDhsvcQ4/edit
and here is the 2022 summary: https://docs.google.com/presentation/d/1x2jON9yjEQboPlXiwFm8pqPT69g0wCDCD_4atR04atw/edit#slide=id.p - Tom:
- present the picked up topics from last year and tell what happened
- Simeon:
- Tri.-Council: what are peoples top 3 prios for 2024
- data should be available to all members before discussion
- Read until next week!
- Ian:
- Would be great to discuss topics / questions in the paper with the authors and document the feedback
- would be necessary to go back to the original paper
Action item: Council chairs shall figure out the next steps - how to discuss the summary, Tom will provide in the next 2 weeks
- Everyone shall read the full version and come back with prios.
- Buckets to categorize the questions
|
Application and Platform Formalization Proposals WG | | - good process
- edge modules and other apps: how to differentiate and what to achive?
|
| Other Business | |
|
| Backlog of topics to discuss |
| FOLIO Developer Advocate | | 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 | | 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 | | 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 | |
)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.