Page Comparison

• GBV: TUB Hamburg live with FOLIO-ERM since Jan. 18, 2021 (one or two others will follow shortly)                 
• EBSCO: Massey University is live on FOLIO — the first library in New Zealand

• We may need another sprint cycle (or two) to complete the feature development for Lotus.  There will be more discussion at the capacity planning team meeting on Monday.      

Long Term Release recommendations 

Goal: decision on whether to endorse

LTR document: https://docs.google.com/document/d/1Un5OlutEh7M2p3AzxE8g20NmdeEhrC0KCNkfd_QLkRw/edit

FOLIO is not ready for a long-term release point because libraries are actively installing each new release to get needed functionality.  The recommendation of the task group was to revisit the decision at the end of calendar 2022.  The document linked above contains recommendations for PC to endorse regarding back-porting of functional and security fixes until a long-term release is established.

No objections from Product Council on adopting these recommendations.

Current FOLIO High-level Roadmap document.

Community Council reviewed this direction and approved. There is a need for something shorter that is useful for publicizing to groups that are not intimately familiar with the development process, and Mike Gorrell put something together based on Jesse's high-level view. 

Jesse is looking to get the roadmap group back together to create a wiki page that links to the high-level roadmap and bring definition to the process.  Then take this roadmap work to the SIGs and Product Owners to see if this is useful and that the content matches expectations/current-work. Also get input from the Technical Council on some of the non-functional aspects of the Roadmap.

Finally, the group might look to see if there is an economical and more functional way of keeping this information as compared to Google Sheets.

Community Council, Technical Council, Capacity Planning, Product Owners updates

Community Council:

• Last update to PC was Dec. 02, 2021 - this update summarizes the CC meetings Dec. 13, 2021; Jan. 10 + 24, 2022
• Update from the OLF + OLF Board: OLF Board seeks new OLF community board member  - nominations open until Jan 30, 2022
• CC retrospective discussion: reflection on last years work (what was good / what do we want to improve?)
  • Fiscal overview for 2022 was presented by the FOLIO treasurer
• Communications Strategies Working Group:
  • • FOLIO Webside Update: Mike G. introduced a concept – participation is welcomed
    • New content needs to be written as well
• CC is working on a calender to ensure, that necessary tasks and duties are followed up and done
• Membership drive
  • Action item 1: Letter to members, new leaders, interested parties
  • Action item 2: Review MoU
  • Action item 3: Setup framework for participation: Find more engaged community members as PO, developers, convener, etc.
• Community Update Meeting Feb., 11, 2022
• Community Council Meetings are in general open to participants! 

Technical Council:

• Review requests: ongoing. Approved mod-inventory-update, a sort of back-end update assistant. Re-evaluation of mod-ldp and ui-ldp are under way. Looking for review teams for three other modules: ui-bulk-edit, ui-marc-authorities, & Translation App.
  • Recommendation to include criteria around architectural fit, duplicating functions
  • Finding reviewers is not always easy, modules may require reviewers with specific skills/knowledge
  • Translation App has significant implications for our approach to translations, may be a larger review/conversation.
• Hosted AWS environments. Costs have increased over the last year, TC has been asked to review and make recommendations for changes. Will organize a group of people much closer to operations to advise.
• Council Goals/Objectives: Reviewing FOLIO Vision, Strategic Objectives and Initiatives for TC responsibilities. Drafting our own objectives/initiatives document and setting some goals. Expect to have something to report out for quarterly Community Update.
• Technical Decision Process: Main issue is how to make technical decisions without making TC a bottleneck: which decisions need to be elevated to TC, and can be made elsewhere and by whom? Has been slow to make progress, forming a subgroup to focus on this.
• Governance issues: working though through expectations for participation, how to allocate work if there are no volunteers/need to spread work around, processes for creating subgroups. The current load is driving basic questions of how we work. 
• Discussion: when reviewing modules, is targeting a release the right way to think of it?  PC also has a to-do item to develop criteria and support for new modules being proposed.

Capacity Planning:

• Has not been meeting regularly since the December holidays.  It met this week to review Jira issues surrounding the next release.  No decision yet, but as was pointed out earlier, there may be a decision on Monday to extend the Lotus feature freeze deadline by one sprint.

Product Owners:

• Lotus release: POs are working hard to wrap up this release. There are several features at risk for the release and we are addressing these risks. 
• Team discussed how to incorporate User Acceptance Testing (UAT) earlier in the release cycle. 
• User Acceptance Testing is in progress or complete for > Title Level Requests, Export orders in EDIFACT format, and Authority control. . Bulk-edit proof-of-concept UAT may get started soon.
• Morning Glory: POs are beginning to plan for this release Anya  
• Team met with Anya to discuss Support SIG and how POs can assist them. One action item: Ask FOLIO Implementers and SIGs to attend Support SIG to help review issues. 

Is it time to rethink the purpose of "Bugfest"—searching for bugs rather than testing implementation?

POSTPONED UNTIL 2/4

Authority Control

• Demo of new functionality

Discussion goals:

• Informational to learn about new features of authority control
• When does the PC need to learn about major development in functionality