2023-03-08 Meeting notes

Raman Auramau will take notes today, Jakub Skoczen will take next week.

All

TCR-9 - Getting issue details... STATUS - There has been no activity or interest in this task for some time now. TC agreed to close the issue.

We should evaluate the module even if TC sees issues from architecture standpoint. Maybe we need to optimize TCR process?

We can evaluate them but these modules are based on some very important architectural changes (fundamental change) to how Stripes / UI works. It actually affects all UI components (because it's about interception for translation capabilities).

Zak Burke will provide a written summary to be included in the TCR explaining why we're closing this and next steps.  We will not close the TCR until that has been done.

Maccabee Levine / Tod Olson 

Any updates from the PC and/or CC?

CC: No meeting this week.

PC:

• Bugfest is under way, Oleksii looking for help from PC on generating the release digest presentation and video. PC considering asking Roadmap group whether they could take this on.
• WOLFcon brainstorming. 
  • Wondering about some more developer-focused content.
  • Idea for a series on making FOLIO easier to install.

All

• https://github.com/folio-org/rfcs/pull/6
  • We agreed to move this to the Public Review stage at the 27 Feb 2023 dedicated topic discussion.
  • Can we wrap up the subgroup now?
• https://github.com/folio-org/rfcs/pull/5
  • Review next Monday

Tod Olson 

Goal: wrap up this effort/working group.

What needs to happen to get us there?

Tod Olson - All we need is votes whether to accept the documentation. Asked people to read on and give their votes. 

Discussion:

• "Periodically revise" → how often?  1-2x? per year?  Quarterly? 
• Jeremy Huff raised a concern over the list including things which aren't very clear.  "feels like we're signing a blank check"
• Marc Johnson provided the history of this effort, and clarified that we don't have a good way to prioritize these things
• Jenn Colt maybe we could accept this as-is, but immediately start a group to go through the list and capture the status of each item.  Also note that the charter revisions mention this type of planning/vision work.
• Do we really want to start another subgroup?  How do we prevent that group from falling into the same trap (working on this for ever)?
• Voted to accept the document in it's current form and start a conversation about next steps, e.g. how to use this document.

Craig McNally  

Update from Mark Veksler :

Two env will be shut down.

folio-perf-firebird was destroyed on Thursday (2nd March).

The team is preparing to terminate folio-perf-bulk-edit as well, but there are still some tasks that need to be completed before they can do it.

Specifically, they need to fix some issues related to handling bad data in Bulk edit (Firebird) and memory leaks in Acquisitions (Thunderjet).

The PTF team is currently working on improving the bulk edit performance, and once they complete all the necessary actions, the second environment will be destroyed.

Thoughts about pulling the cost control team together and the next steps?

Today:

• We didn't get to this, defer until next week.

Craig McNally 

• TC dedicated discussion:  13 Mar 2023 11:00 AM ET
  • Review:  https://github.com/folio-org/rfcs/pull/5

Jeremy Huff 

Review:  https://github.com/folio-org/rfcs/pull/5

Today:

• We didn't get to this, use the next Monday time slot 13 Mar 2023 to review.