Attendees

Guests: Paul Kloppenborg (BSZ); Julie Bickle (LMU); Marc Johnson (TC)

Discussion items

Item	Who	Notes
Announcements	Kirstin Kemner-Heek	Beware of the time switch in 2 weeks: meetings are an hour earlier for Europe Welcome to Paul Kloppenborg who is BSZ's new FOLIO project lead
Community Resource Issues	Mike Gorrell	1) FOLIO Documentation. Marcia Borensztajn's contract with EBSCO has expired (ended officially 12/2020, was funded by EBSCO until end of September 2022, now her work has really expired). A critical role when the documentation effort was getting started. How do we ensure sustainability? Explore a short term contract (announcement came as a surprise to many) for Marcia? Other ideas? Mark J: there is no one whom we can address her role to Harry / Dracine: her main work was coordination, release management for documentation, manage process for Google Season of Docs, organization and structure building, PO role for the documentation working group, address end user instructions and sync them with releases, reach out ot the SIG's for input, reach out to specific PO's, maintain different types of docs: essential platform doc and offcial end user docs Mike: evaluate the option to extend Marcias contract a bit to enable a sustainable bridge to another person taking over Boaz: is this an ongoing need or a temporary task? Dracine: it is ongoing - without Marica the documentation would not be at this point. It is critical to the project. Tom: where does Documentation live? (Dracine: https://docs.folio.org/) Is it most closely aligned with a particular council? With those who do release mgmt? Harry: Marcia received her directions from Harry. Boaz: How do we know how effective the work has been? Tom: who would manage her replacement? Dracine: Her role is a kind of a product owner → Head of PO's (Khalila) → in the end the PC Boaz: who is taking care of the transistion, funding, etc.? Who is manageing the process? Kirstin: PC discussion from Thursday → integrate the new FOLIO members into this task - work on some process with Marcia to fulfill the transition job (funding would be needed) → postponed until this week / next week Result: CC waits until the PC came to a conclusion. 2) FOLIO Reference environments - Index Data announced last spring it could no longer donate DevOps resources to manage these environments as well as making the releases. KitFox picked up the release work - these reference environments are no longer being maintained. See Slack conversation. Call for donated resources? Small contract with Index Data or EBSCO? Mark J: it was unkown, that this happened to all reference env. - it was thought just to be the latest one. But Kitfox hasn't taken over the task Harry: Kitfox are 3 people from EBSCO, Mark Veksler is their person to report to - they concentrate on the release building and the refererence env. Mark: Oleksij said, that team can't do that → conversation with Mark Veksler seems to be the right way to address this task How can the CC help? Clarify, what needs to be done about that? Conversation with Ann-Marie, Mark V., Harry is the next step. Harry has the idea, that maybe one more person from the community could join the team would help a lot. Could be an EPAM person as well. Action item: Harry will gather skills! Mark: Community needs to spec out how things are sustained the community is relying on? How does "the community" know, what is needed? Result: ???
Treasurer's report	Paula Sullenger	Created a Finances page and posted FY22 Financial Statement. $90,000 has been set aside in a separate account as the reserve fund.
Things that could b better about FOLIO	Tom	Original Doc ument (source input doc) and the grouped document We have 2 documents now. CC / PC / TC have been asked to add some feedback - 50% done until today Grouped results: more than one cluster may fit for certain feedbacks Result: Present results in 2 weeks (Oct. 24, 2022)
FOLIO Resourcing Group	Team	Working doc. Next week we will look at kernel v. distro model for parallels to FOLIO. 2 models have been discussed 1 more model to be discussed Action item: please bring forward other models in the next 2 weeks! Next step: summarize and present the results to CC Mark J: What is the expected outcome? Tom: Answers on what the CC shall found? clarity, how decisions are made around non centralized development Mark J.: How do we get more development capacity from the community? Tom: this is one goal of the mission. Mark: What are the bounds of the FOLIO governance model? Mark: TC is changeing its governance modell ???
Other		Library of Congress Harry: process is in a very early stage and a big project short-term and longer-term plan understand priorities project includes a lot of work in short time Questions: Boaz: What wants LOC do with FOLIO? Harry: Everything. 25 Mill. MARC records need to be loaded into FOLIO, ILL services needs to go on. Added security and privacy tasks to be solved → searching, publishing Mike: How does the LOC want to invlive in the community? They want to become "more involved", but have a lot of work in front of them. Regualr update to the community is an option to keep the community in the loop. Boaz: Do they have developers? Kirstin: Will LOC become a FOLIO member? Yes. And contribute everything back to the community! But will have to develop a lot of "extras just for LOC". Tom: I put LC's feature needs almost at the top of the list. Right after my Von Keven Liu an alle 05:00 PM I wonder if Eric Miller still working for EBSCO, who contributed a lot on BIBFRAME for LoC

Browser not supported