Recording
...
| Time | Item | Who | Notes |
|---|---|---|---|
| 5 min | Announcements
| All | Planning on having the first go-around ready near Christmas and start the pilot next year. How do we put our needs in front of new members in a way that is welcoming and expresses the needs of the project? The idea is to have a slide deck that anyone can use to onboard or mentor a new organization to the community. There has been a response from the community about the need for the documentation coordinator, and outreach continues for that. Bugfest is starting on November 7th and runs until November 18th. There are test cases that need to be claiming. Reach out to Anton to get set up in Test Rails. (There are a limited number of TestRail accounts, so people that have done it previously but not recently may need to be set up again.) Also add your name to FOLIO Testing Community Members. Two new libraries added to the China FOLIO community. |
SIG Conversations
| Conversations are continuing to happen. Kristin noted several themes that have come out, and she has added them to her notes on conversations. Next step: look to pull out general themes from the notes documents. There are frustrations coming from the Metadata Management SIG, which seems related to the lack of development capacity to build to the specifications they are developing. The MM SIG has been an early warning indicator of issues that later affect live sites. The aim is to provide places where new organizations can come in and make an impact on the project. There was an extensive discussion of how resources in the project are allocated and what can be done to influence that allocation. | ||
Community Council feedback: From Tom Cramer on Slack: Since September, the CC, PC and TC have canvassed many community members on “what are things that could be better about FOLIO?” This came out of discussions at WOLFcon in Hamburg about what the priorities were for advancing & investing the project. 20+ council members interviewed 60+ informants from the community, producing a list of 175 items. These items can be found in a grouped list that sorts the input into 13 different categories. This is a rich gauge of where many community members find the project--I recommend reading through this doc all at once to capture the gestalt. (~15 min)A synthesis of all the input can be found in this presentation. The last three slides contain some specific and actionable opportunities for the FOLIO councils to consider and adopt as priority items around which to organize community effort. | Community Council has not yet had a chance to talk about this; the Tech Council did discuss at its meeting yesterday. It is easier to prioritize as a small group, and—if that group has development resources—to move the activity forward. In potential-action-items-1, there is an item for "attention on growing the community through marketing, supporting adoption, onboarding" which is related to the discussion of the onboarding group from earlier in the meeting. There is a discussion in the chat about the ARLEF group. Can this be an agenda item for a future product council meeting? The group was formed in part as a response to the resourcing discussion that has been happening in the community. On the developer topic, if more contributions are desired then there needs to be a cohesion of design. The "flower release" is the locus of control at the moment; if that changes, then the nature of how development teams contribute effort will change as well. This also ties into concerns about how to scale the project in keeping with the vision of a platform for library apps. | ||
| 5 min | Agenda Topics:
| Next week is a SIG update week (template), and Kristin Martin with talk with Jesse Koennecke about whether the roadmap/prioritization work is ready for presentation. Review our development process where an institution has given a developer that has worked successfully. What can be learned from that? |
...