Page Comparison

Florian Gleixner is next, followed by Jeremy Huff 

All

Maccabee Levine / Tod Olson 

Any updates from the PC and/or CC?

CC:  

• For the Evaluation Process for New Modules, forming a subgroup to develop the new MOU.  Maccabee Levine volunteered, others welcome.
• TC Elections upcoming.  Nominations will be collected 4/10 to 4/17.    Relatively short election period follows.

PC: report from Marc Johnson 

• No feedback about TCR-9 reject
• Approved Terminology proposals from TC
• They are working on their own Module evaluation process. Seems, that PC evaluates Apps and not modules.
  • Jeremy Huff shall the TC give feedback for PCs app evaluation process?
• Working group for the Roadmap. Work from developers may not match the roadmap, and it is not easy to monitor or enforce match with roadmap.
  • Jenn Colt 

All

• TODO:  Revisit the "Monitoring AWS Hosting Costs" subgroup - reform with a new set of participants.  Review and adjust deliverables/goals as needed, etc.

Notes:

Translation Subgroup: group will be closed

Monitoring AWS Hosting Costs: New group will be formed. Maccabee Levine will be owner of the group. Mark Veksler and Peter Murray will hopefully also be part of the group.

Breaking changes: Needs another meeting.

TCR Process Improvements: Jeremy Huff has prepared a slidedeck and will present it next TC meeting

Architecture Review Subgroup: Marc Johnson will start the group whenever other subgroups are wrapped up.

Distributed vs. centralized: Nothing new.

• https://github.com/folio-org/rfcs/pull/6
• https://github.com/folio-org/rfcs/pull/58

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.

Today:

Craig McNally / Jeremy Huff 

See https://docs.google.com/document/d/15WJ3bcNgHW5-oalsPx7G9RiZAKzJDTWRhaL34upZkys/edit?usp=sharing

We met again on Monday 27 Mar 2023 and left some suggestions in the document.

Craig McNally notified the FOLIO chairs that the TC's review is completed and that feedback was given.

Craig McNally 

• TC dedicated discussion:  03 Apr 2023 11:00 AM ET
  • Topic:  Breaking changes RFC?  Onboarding Docs?
• Tri-Council meeting:  13 Apr 2023 9:30 - 11:00 AM ET
  • Agenda:  2023-04-13 Tri-Council Meeting (WIP)
  • We need to pull together an update for the other councils (what we've been doing since last Tri-council meeting in January)