Page Comparison

 Maccabee Levine is next, followed by Tod Olson 

All

• [TCR-28] Request for Technical Evaluation of a edge-courses - FOLIO Issue Tracker - Jeremy Huff volunteered
• TCR-29 - mod-fqm-manager 
• TCR-30 - edge-fqm 
• TCR-31 - mod-lists 
• TCR-32 - ui-lists 

• PC approval?  Seems like yes. → list app has been approved by the PC

Maccabee Levine / Tod Olson / Jakub Skoczen 

• CC: Maccabee Levine no CC meeting this week
• PC: Tod Olson 
  • Presentation on Application Formalization by VBar and Craig McNally 
  • See 2023-09-14 Product Council Agenda and Meeting Notes for details.
• RMS Group: Jakub Skoczen 
• Security Team: Craig McNally 

All

• Nothing new

All

Standing agenda item to review/discuss any requested or required changes to officially supported technology lists

• Postgres 12 EOL Fall 2024...  
• Handle in Quesnelia page Quesnelia - Technical Council - FOLIO Wiki
• Typescript needs to be addressed
• Open question: Timelines
• Want to give people more lead time before the Poppy release

Maccabee Levine 

See slack post from Tom Cramer:

At the August 25, 2023 meeting of the Tri-Council at University of Chicago, it was agreed that we would repeat the “List of Things that Could Be Better About FOLIO” survey that was conducted after WOLFcon at Hamburg (Sept ’22).

We ask all Council members to each survey three community members for a list of three things that could be better about FOLIO. Please enter the results into this document by September 29, 2023.

In October, we will report back both on this year’s responses as well as an analysis on progress made against the 2022 goals.

Thank you.
-Tom Cramer (CC), Jesse Koennecke (PC) and Maccabee Levine (TC)

Questions/Notes:

• "Things that could be better about FOLIO" presentation slide deck:

  Widget Connector
  url https://docs.google.com/presentation/d/1x2jON9yjEQboPlXiwFm8pqPT69g0wCDCD_4atR04atw/edit

Jeremy Huff /All

https://docs.google.com/document/d/1OLae-eGN3_dEOXbAr7Tr1cvudBzqNA7TttzH9QmvuR8/edit?usp=sharing

Any objections to sharing this with the PC?

Tod Olson / All

See slack post from Tod Olson:

Looking ahead to the late fall, I see that Refresh Token Rotation is coming in Poppy, that's a big change and the new API token management API is still in progress. In any case, it appears this will require changes to any scripts or integrations that hit the (non-edge) APIs. Does TC have a role in publicizing and making recommendations for how to prepare for this change? Or am I misunderstanding the impact? 

Notes:

• Does the TC has a role in this ?
• @Steve Ellis seems to be the contact person

Matt Weaver / VBar / All

Continue discussion from Monday and try to make a decision on how to proceed.

• have conversations about architectural discussions
• Would like to have this discussion in the context of an RFC.
• Do we want to weaken the constraints arcoss the board ?
• Concerns that it gets out of hand
• RFC could propose some privileged access
• The decision to keep data boundaries up is being challenged by implementations. An RFC would be a great format to have those discussions.
• Consider risk of suggested approach vs. the alternatives
• We won't get the RFC done by Poppy. If we grant an exception, it will be part of Poppy. Otherwise not. We could make mod-fqm-manager a special being. Anyway, we have to address the immediate question.
• Tasking fqm with being responsible for cross-domain queries. That would be a reasonable way to frame it as an RFC. Instead of an exception, it could be framed that way.
• TCR review and architectural implications should be separated. The discussion whether we want to make an exception or not is independent of the TCR/RFC.
• Release schedule for Poppy is less significant than the bigger question. 
• mod-fqm-manager is a component, a sub-system, that has the sole responsibility for making cross-module queries. An RFC should be taking that one position.
• Marc Johnson : But that is the same as making an exception. Then this one module has a very significant amount of power in the system. We have to move that topic forward in the next week.
• Jeremy Huff : I have 3 weeks to do the evaluation. I will follow the process. The Poppy deadline is irrelevant.
• Marc Johnson :  That will be effectively a fail for the module getting into Poppy. We have to represent the politics that goes with it to the rest of the community.
• Jeremy Huff : I am aiming to keep the deadline. The module was probably in a state that tickets could have been created two weeks earlier.
• Maccabee Levine : It already missed the 3-week-deadline. The reviews take the time they take. The TC had many cycles to improve the TCR process.
• Craig McNally : This deserves more communication. Let us do that in Slack.
• Mark Veksler : Can we have an additional meeting on this ? Can we decide on Monday's meeting (Sept 18) ?
• Jeremy Huff : We should adhere to and preserve the TCR process.

• 20 Sep 2023 - Dedicated Discussion - Topic?