Attendees

Guests: Jesse Koennecke (PC); Ian Walls (ByWater); Marc Johnson

Discussion items

Item	Who	Notes
Treasurer's report	Paula	Update - not much new to report Timescale for developer funding (current commitment is through end Dec 2022)? Funding for the full FY is possible - see CC Google Drive / treasurer As long as no others expenses are pressing: keep him until June 2023 - Tom, Kirstin Decision CC: Proposal accepted! What reserve level we would like to aim for (currently have $90k which is about 3 months, best practice is 3-6 months)? Decision CC: have 6 month reserve right now is accepted - better a year in the long run Set up 3-month reserve now
Cross council meetings	Mike	Discussion with other chair/co-chairs re. quarterly cross-council meetings and more frequent chairs' touch base Ensure update from the meetings to the councils / keep minutes
FOLIO resourcing group	Tom, Harry, Ians	Update (notes in https://docs.google.com/document/d/1sZFdV6FgvtfBOgRFTuXQ3ipUcroQTch0Y7itELqt-58/edit) Summary by Tom Cramer - 4 meetings so far Discussion of 2 models ("Ian Walls model" / "centralized model"), one more will be provided by Marko Paula: be aware of changing the governance model itself - it is still quite fresh instead of try to change things in the recent structures → we might get stuck in longish discussions otherwise
Proposed group to create vision for FOLIO builds	Simeon	"Pitch for Proposed vision for future FOLIO builds" from Julie Bickle Summary by Simeon
Things that Could be Better About FOLIO	Tom	Discuss responses in https://docs.google.com/document/d/1-F613EM2d4pOwgRQobRQyS0k5T2T9RjoprNcfA_NLa0/edit Tom presented the results 50 - 60 feedbacks Feedback from CC? Next steps? Mike G.: needs to be reviewed Marc: positive: very open, frank feedback; good, that people are speaking up Ian W.: "Quality of data analysis" as a tool to analyse the results? Paula, Kirstin: "I've read through them but haven't been able to really think about it yet" Simeon: Collect a set of themes would be helpful - nothing shocking, but the openness is impressing Mike G: Any volunteers? Action item: Collect more feedback for 1 or 2 weeks is fine - be aware not to ask the same people again Tom: Be aware to collect the input from all 3 areas, we might identify: functional, technical, strategical Action item: Ian W. volunteers to start the analysis ! Action item: set up a new document ordered by themes → Tom! Action item: Proposal by Tom to present the feedback questions to TC / PC to let them ask their "3 people" as well → Mike G., Simeon
Additional agenda items	CC	Harry: Takeaway from WOLFcon: "How can I inform myself about the project / status of development"? Jira Dashboard about Releases, e.g. like "Morning Glory" Who is doing what? Status about features? List of new functionality / NFR's Function "Manage dashboard" Confluence (FOLIO Wiki) provides Release Notes for each release incl. "known issues" connection to Jira by shwoing a list of issues Regular updates Overview is done by PO's and Head of PO → Khalilah To a certain extend its produced automatized Alexij Petrenko: Release Manager of FOLIO Questions: How often do the development team informs the community? Presentation to PC for every release and a report every 4 weeks For the whole community: FOLIO quarterly meetings? Jesse: advertise the PC reports to the broader community Work on the roadmap for the broader picture Mark: the process is not new - how do we ensure, that people are using the offers? More documentation on understanding how the project works? I think a narrative for each release would be great Tom: As the project grows and matures, the need for this kind of training / orientation / understanding of how the project works will only grow Kirstin: work with mentors from Community Councils for general entry and point people to the more detailed information - what about the Community Outreach SIG? More about this in the next meeting
		Next week: LOC joining FOLIO

Browser not supported