...
| Time | Item | Who | Notes |
|---|---|---|---|
| 5 min | Announcements | Morning Glory release date is now September 21. Three institutions in China decided to pre-pay their dues for 5 years. | |
| 15 min | WOLFCON Updates: Attendance/Registration Full schedule: https://wolfcon2022.sched.com/ Purpose: Information sharing | Registration is strong: 167 people in person, over 250 people total. Registration for virtual attendees will continue until Aug 30th. In-person registration closed Sunday. On August 30, there will be people setting up between 2pm and 5pm...visitors welcome. Ask at the information counter at the library where we will be. More information will be coming at the Know-before-you-go email. For this year's membership, EBSCO has stated that they will cover the AWS costs for the project as their financial contribution. The Community Council will be determining how the dues will be spent for the upcoming year. See the "PC/CC meetings" document for details about the council meetings. The Sched website is nearly finalized. There are now show-and-tell demos on Thursday morning; these are informal walk-throughs/discussions and won't be broadcast to remote participants. The China update will cover all questions about FOLIO activity in China; send any questions to Lucy to have them included in the discussion. | |
| 30 min | Update and Status on Courses App Background and current status Desired state and resource needs Purpose: awareness raising, brainstorming, and searching for resources | See the RA SIG meeting notes starting in 2018 for the history of the Courses App development. The initial group met to create requirements and Jira stories. The subgroup reformed in 2019 with Kelly Drake as the product owner and subgroup convener. Simmons provided the financial support to get the app developed with Index Data; this version went live in Fameflower. There has not been sustained development since then. Duke needed the Courses app for the summer of 2021, and md331 (Deactivated) added additional features including support for LTI (for connecting a system to a learning management platform). There hasn't been development after summer 2021 and the subgroup has not met. The Index Data "Thor" development team is listed as responsible with Charlotte Whitt as the product owner, but there is no active development at this time. There is a groundswell of interest in further development of the Courses app. Efforts have been made to recruit a product owner without success. There is a Jira backlog of features with interest to be developed, but these should be reviewed in light of new experiences with FOLIO and what has happened in the product space since the Jira stories were developed in 2019. To move this forward, a convener of the subgroup and a product owner are needed to shape the discussion into actual requirements for a new or existing development team. Jana Freytag volunteered to convene as part of RA SIG activities and (OLD ACCOUNT) Erin Nettifee volunteered to help on-board a new product owner. There is also a need (being seen in the SS) to address issues that have come up with the app. One thing that is missing is a workflow for faculty to request items being put on the Courses app and the status of those requests. Recommendations: go back to institutions to see what resources for a convener and a product owner are available for the refinement of feature/function development of Courses. Product Council should review the assignments in the Team vs module FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix to see where teams are just caretakers rather than active developers of apps. | |
| 30 min | Capacity Planning Updates
| Capacity Planning didn't have a charge; a new one was drafted. This charge directly affects the PC, so PC members should review it. Capacity Planning would need to update Product Council on its activities and impact on the project. One thing is to change the name of the group since "capacity planning" isn't something the group hasn't has done in a while; something like "release planning" would be a more accurate name. There was a period of time when the group wasn't meeting, but they are meeting again now and should have a liaison with Product Council. The draft implies a large change in the scope and purpose of the group; the draft includes a list of ideal representations for the group. In addition to setting the timing of releases (including the series of dates and descriptions of tasks), it also determines what gets into hotfixes (based on the technical characteristics of the bugs being fixed). Next steps: clean up the document for further discussion next week and in-person at WOLFcon. | |
| 10 min | Agenda planning/upcoming meetings |
|
...