Note taker: Charlotte Whitt (7/27/2023), Martina Schildt, Jennifer Eustis, Owen Stephens
Phoenix is live on FOLIO, and Linköping University (Sweden) is also live as of this week as self hosting institution.
Stanford is about three weeks away from going live, when the old system is to shut down on 8/18, and then go live on 8/29. Stanford is also testing split on taxing issues.
Chicago, Cornell and 5College have all successfully done their FYRO.
|30 min|| |
PC topics for WOLFcon and processes for moving forward
WOLFcon 2023 PC/SIGs ideas:
Topic: How to wrap up discussions, and get decisions done, and move on.
Jenn Colt shared an article about wicked questions, and paradoxes in agile development. A suggestion: List 'wicked' questions in the FOLIO project.
Jenn mentioned that a suggestion like this takes time. One example is the two Summit meetings, where they had the luxury to really discuss things together. Our regular time slot is not always enough, and sometimes discussions overlap. Charlotte suggested the possibility to have extended PC meetings once a quarter / every second month.
Tod pointed out that the PC is dedicated to handle several topics which serve as facilitating the communication within the community. The CC now only meet every second week. The TC is in practice meeting twice a week because they have a bit of a back log.
Ian Walls finds that the way the FOLIO Governance model is architected is modelled as a commercial organisation, and not so much as an open source project.
Evaluating the governance model would be a topic for all three councils.
In chat: Jenn Colt to Everyone (Jul 27, 2023, 3:55 PM)
Community Council, Technical Council, Product Owner, and Release Stakeholder updates
2. New PO: Ryan Taylor (EBSCO) will join as a Data import PO.
3. Initial planning of WOLFCon accepted sessions
4. Gathering Release notes feedback - https://easyretro.io/publicboard/5hfJUmkkV2ZVcizFWGG8293glmj1/31685873-9f62-4d3e-9b50-bfcc458afcfa
5. Organizing a Localization Overview + Q&A discussion
|20 min||Support SIG procedural updates||Charlotte Whitt|
The support SIG has introduced a numbering label on bug tickets where the Support SIG repeatedly ask for a status, and the SIG's comments stay unanswered; like STSMACOM-715. This ticket has the labels "support", "3" (for three unanswered status questions from Support SIG) and the "5" (for five unanswered status questions from Support SIG)
In the Support Dashboard we will add a 'pie' diagram where we can easily identify these support bugs being unanswered.
The PC wants to know how the Support SIG is planning on to escalate an issue after e.g. five times, and here one way could be to give a ping on the PO channel or raise this at a PO meeting.
Harry asked about review of old bugs, which might not be relevant anymore. Review of these aged bugs are happening per team. Khalilah acknowledge that the team could do a new effort on addressing these old issues.
|5 min||Future agenda items||All||No new topics raised.|