Alexis Manheim Charlotte Whitt Kristin Martin Paul Moeller Jennifer Eustis Owen Stephens Gang Zhou Jesse Koennecke Brooks Travis Martina Tumulla Jana Freytag Lisa McColl Tod Olson Peter Murray Ian Walls Jenn Colt Ann Della Porta Maura Byrne Khalilah Gambrell Zak_Burke
- Note taker: Charlotte Whitt, Jennifer Eustis (9/28/23), Martina Schildt, Owen Stephens
|Time||Item||Who||Notes||Decisions and Actions|
The Meeting Hygiene Subgroup has been looking at the wiki and documentation. There are old council meeting tasks and topics. Alexis will post these to the slack channel to ask people to resolve these old tasks.
The videos from WolfCon are being uploaded to YouTube now.
A reminder: "Things that could be better about FOLIO". Please add your items by tomorrow 9/29/2023.
|15 min||Time zone inclusiveness||Paul Moeller|
It seems we can find a time that works for US ET and Australia/China (7:00 PM Boston, 8:00 AM Beijing, 9:00 AM Canberra) , or Berlin with China/Australia (2:00 PM Beijing, 4:00 PM Canberra, 8:00 AM Berlin) but finding one that will work for all would be problematic. The best is probably 7 AM Boston, 7 PM Beijing, 9 PM Canberra, 1 PM Berlin. It would be even earlier/later for some of us and other regions may join if we can find a suitable time. Should be consider alternating times once or twice a month? https://www.timeanddate.com/worldclock/meetingtime.html?iso=20230928&p1=43&p2=33&p3=57&p4=37
We talked about meeting time inclusiveness. The Meeting Hygiene subgroup met last week and have provided above some options for a larger discussion. It seems like the best way forward is to alternate times according to zones around the world.
Did you get feedback from folks in time zones when there are no meetings? The subgroup reached out to one person and needs to reach out to more. It's not clear who we are trying to reach out to.
The Koha global community does most business through IRC chat. When topics need to be addressed, they rotate across the glob. Is everyone expected to be there? If it's an important topic, then people make the choice to attend.
Harry had reached out to ask about a platform for forums as an alternative to meetings. There's Discuss which was closed down. Does Slack meet our needs for these types of discussion? Some find that on Slack some discussions get lost.
Koha is much older and mature community compared to FOLIO. In FOLIO, we are still doing very fast development. Having these synchronous meetings are still important.
The other idea floated was that we could have dedicated meetings for geographic regions. This could be a good way of having a venue where people could bring concerns while not ending up having meetings outside their time zone. This could be an implementer style of meeting or we could cycle through topics. One option is to have a meeting for a time zone with different topics and another one just for that time zone.
We need to reach out to more folks like the Australians. Is there a difference between members of the PC and those that just attend? Who else do we reach out?
Can we find a way to use the asynchronous with synchronous methods? Could we use the comments to the agenda document? We can look into other options.
The Meeting Hygiene group is meeting next week and will pick up this topic and ideas.
|The Meeting Hygiene subgroup will address this topic and the questions surfaced from this discussion next week.|
|30 min||Council Updates|
Release Management: Will take recommendations for Quesnelia timeline to group. The next meeting is on next week. The group will discuss what people thought about the Quesnelia timeline and bringing back the discussions on release schedules in general. How Quesnelia might affect future releases is speculation. When the group meets, will there be a discussion? Kristin will verify this.
The subtopic of this is the number of releases per year. What number makes sense? Does it make sense to consider this with the re-architecture proposal? We also switched from hotfixes to critical services patches. The CSP approach is worth some discussion along with how often we do a named flower release. We've done more CSPs for Orchid that hotfixes for Nolana. We have to check ourselves and our teams about where we put the effort and careful where we spend our time. Some users have communicated that slowing down would be good. We need to look at the balance between stability and fixing bugs and new functionality. If there are fewer flower releases, this might be even more pressure on the TC and the review process. It does seem that one issue is that we're not finding these critical problems soon enough. Catching a P1 in bugfest is already late. How do we get our QA earlier in the development stream? This has been a problem for some time. The push to automate testing early and often has helped. We need to do better with user acceptance testing. The other challenge is that testing environments doesn't have the data or workflows of the standard FOLIO library. For the development that IndexData is doing, they are testing patron notices for reminder fees in different environments that has helped push out new code. It's great the developers can test their use cases. We need UAT testing earlier. Some cases we need a lot of data and in others we need a variety.
The Feature highlights would be great to see how the roadmap subgroup can tie into that. Is there anything that the PC can do in this area to help define what is needed at point of release for implementers and adopting libraries? There are different purposes for the types of information and we need to get this to the right people using the right language. This seems like a community driven goal. This could be a future topic/discussion.
With the release digest, the implementers SIG is taking that on to see if this is useful for people. It's difficult to predict who needs details and who needs less details.
Tod will reach out to those building the FOLIO demo sites (snapshot and snapshot 2) if this authentication method is there.
Kristin will verify when the Release Management group will make a decision about the Quesnelia release.
|5 min||Future topics||all||Future Product Council Meeting Topics|