Action Item for PC: Okay to officially close down the Discuss platform?
Report from meetings: Nov. 28, 2022, Jan. 01 and 23, 2023 (next meeting is on Feb., 13, 2023 )
Council elections: preparations will start early and will be let by Hkaplanian and the CC chairs → qualified volunteers are very welcome!
Treasurer's update: funding is sufficient so far for the ongoing expenses
Technical Editor funding initiative: $ 15,800 are committed → means 4 month funding ($3520,00 per month) and a gap of $1800.- for 5 month to let Marcia Borenstaijn work along with Paul Kloppenborg for onboarding, training and support. CC chair works with OLF accountant at the details.
Filling Anton's Q/A role: Discussion about understanding his jobs scope and qualification - no conclusion
"Member organizations will be relied upon to provide the resources that make FOLIO viable and sustainable. The Community Council shall be responsible for determining and updating the FOLIO Membership Levels, including contribution amounts and any associated benefits."
Holly and I discussed UNAM no longer developing for Orchid so that Holly can focus on testing development.
IF testing cannot be completed by Holly's last day then Khalilah (yes me) will either complete testing or identify a PO/community member who can complete testing.
New PO: Christine Schultz-Richert (EBSCO) will focus on MARC cataloging requirements (Spitfire dev team) has already been introduced to the quickMARC subgroup
Still would like to have more information shared in advanced regarding meetings, scope, and activities on wiki
Also brief discussion on the future of the Prokopovych team, which is depleted of resources. This has been an ongoing issue and the responsibility of the team remains unclear.
What role does PC have in managing development teams and what teams are there?
What role does release planning have for managing team composition?