Page Comparison

1. Funding and developer resources
   1. Update from the treasurer
   2. FOLIO can extend one developer contract another year but can't hire a second developer 
2. Continuation of process to prioritize task list for CC deliverables: https://docs.google.com/spreadsheets/d/1jfIpMOdfPQWjbWNp0_TkrNb2dr4AcIJao4CvqMGWt2o/edit#gid=
   
   1. Results will be summarized and presented to CC / PC / TC shortly 
3. Introduction of new FOLIO member UB Regensburg
4. Job ads in the FOLIO community: shall be done in a new Slack channel (tbd)
5. CC decided to keep Zak Burke as a TC member while he is changing the employer. EBSCO has now 2 votes in TC. 
6. Process of Governance amending was clarified, which includes the aligment between CC, TC and PC
7. WOLFCon: CC supports a F2F meeting - planning in progress
8. FOLIO Quarterly Community meeting scheduled for Friday October 8th - Wiki page will be set up

External Code Submissions and LDP app evaluation: TC drafted technical criteria for code contributions, see FOLIO Module Acceptance Values and Criteria v1.0. (This will be moved to a more permanent location.) These criteria were used to evaluate the LDP UI and its back-end connector module. For both modules there are some criteria that are not met and need remediation, details in MOD-LDP Acceptance Analysis and ui-ldp Acceptance Analysis. There was much discussion about both the LDP app and the eval process that we are developing, for details see the 2021-09-22 Meeting notes.  The largest gaps are in support for multi-tenancy and in some aspects of accessibility, plus where the canonical source code lives. The eval team is drawing up proposed deadlines for specific items.

Operational and SysOPs needs: Reviewed with SysOps reps the operational concerns they have, similar to what they presented to the PC. Much of this can be characterized as forms of technical debt. There is some question about what TC can do, as TC can look at approaches but does not assign resources. Next actions are unclear. Addressing these probably involves all of CC, PC, and TC.

Check Out Performance: reviewed proposal, determining actions this week deferred due to time taken by LDP evaluation.

• Optimistic Locking - Agreed on requirements and met with MM SIG for validation. Several POs are testing functionality - https://core-platform.ci.folio.org/. Still unsure if feature will be included with Kiwi.
• POs met with Roadmap team to discuss Roadmap themes and the group's goals 
• Dennis B. has proposed an additional JIRA workflow status that represents a feature/story requires additional technical requirements before development can begin. 
• This Friday (9/24) Kiwi code freeze date 
• 9/22 feature stats
  • 22 Closed features
  • 6 In Review features
  • 40 In Progress features
  • 5 Analysis Complete features
    6 Open features
    2 Draft features

Roadmap themes

Process:

• Develop new ROADMAP Jira project: Remote creation via Jira
• Create themes and subthemes categories
• POs will tag JIRAs into themes/subthemes
• Use spreadsheet to show new development
• Includes SysOps themes identified
• Update Roadmap regularly, potentially review after each release