2023-09-25 Meeting notes

 Tod Olson is next, followed by Ankita Sen 

All

• A one-business-day exception has been granted to us from the RMS group.  This is the last day for new module acceptance into Poppy.
• Revote on TCR-29 - mod-fqm-manager
  • on 22 Sep 2023 the TC voted to accept this module on a conditional basis.
    • Conditions:  Depending on the outcome of an RFC about the use of views to query data from multiple modules, changes to mod-fqm-manager may be required in the future.
      • Team has agreed to draft the RFC.
  • The vote last Friday ended with 5 for, 4 against.  Given the clarified rules above, we will hold a revote today.
  • Revote: aye: 7 nay: 3, motion carries.
• TCR-31 - mod-lists (Tod Olson / Craig McNally)
  • Issues: 
    • SonarQube code smells on number of parents for Exceptions.
    • MinIO/S3 buckets not technically approved, decision still in DRAFT status
      • practically speaking, this is a gap in our process, have used other 
    •  mod-lists uses /query and /entity-types APIs, module descriptor needs to be updated
  • Vote: Aye: 7, Nay: 1; motion carries
• TCR-32 - ui-lists (Zak Burke  / Maccabee Levine) 
  • Aye: 10, Nay: 0; motion carries
• TCR-30 - edge-fqm (Kevin Day /  Jeremy Huff)
  • Not all endpoints show up in the generated API documentation. Reason is that some lives in a shared library used by both mod-fqm-manager and edge-fqm. Documentation is all in the OpenAPI spec, but generation tool is not picking up the library code.
  • Aye: 10, Nay: 0; motion carries

Much discussion centered around the integrity of the TC review process and whether we are setting precedents by accepting these modules, whether conditionally or by accepting a missed but easily-corrected requirement. There is a real concern that we are setting precedents that undermine the review process.

Steve Ellis 

Steve Ellis will share an updated rollout plan (proposal) for refresh token rotation.

• Original plan for Poppy to be a hard cutover, and there was concern about enough time to transition scripts and integration to the new authentication method.
• The current proposal to support both methods during Poppy and allow a transition period, asking for buy-in from the TC.

Maccabee Levine / Tod Olson / Jakub Skoczen / Craig McNally 

• CC: Maccabee Levine
  • Looking for someone new to manage Lokalize
  • Developer advocate next steps.  Second TC rep (Jeremy Huff ?)
• PC: Tod Olson 
• RMS Group: Jakub Skoczen 
• Security Team: Craig McNally 

All

Quick updates... 1 minute each

All

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: https://docs.google.com/presentation/d/1x2jON9yjEQboPlXiwFm8pqPT69g0wCDCD_4atR04atw/edit

• 27 Sep 2023 - Dedicated Discussion:  Officially Supported Technologies Upkeep

Skipped today due to time constraints

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

Today:

• Check in on progress
  • Florian Gleixner (postgres 13? 14? 15?) 
  • Jeremy Huff / Zak Burke (typescript)
• Lombok?
• MinIO/S3?
• Need to bring Quesnelia page up to date

Previous Notes:

• A workflow for these pages. When do they transition from one state to another. Do we even need statuses at all ?
• Stripes architecture group has some questions about the Poppy release.
• Zak: A handshake between developers, dev ops and the TC. Who makes that decision and how do we pass along that knowledge ? E.g. changes in Nodes and in the UI boxes. How to communicate this ? We have a large number of teams, all have to be aware of it.  TC should be alerted that changes are happening. We have a couple of dedicated channels for that. Most dev ops have subscribed to these channels. How can dev ops folk raise issues to the next level of community awareness ? There hasn't been a specific piece of TC to move that along.
• Craig: There is a fourth group, "Capacity Planning" or "Release Planning". Slack is the de facto communication channel.  There are no objections to using Slack. An example is the Java 17 RFC. 
• Craig: The TC gets it on the agenda and we will discuss it. The TC gets the final say.
• Marc Johnson: We shouldn’t use the DevOps Channel. The dev ops folks have made it clear that it should only be used for support requests made to them.
• Jakub: Our responsibility is to avoid piling up technical debt.
• Marc: Some set of people have to actually make the call. Who lowers the chequered flag ?
• Craig: It needs to ultimately come to the TC at least for awareness. There is a missing piece. Capacity Planning needs to provide input here. 
• Marc: Stakeholders / Capacity Planning could make that decision. Who makes the decision ? Is it the government or is it some parts of the body ?
• Marc: the developers community, the dev ops community and sys ops are involved. For example the Spring Framework discussion or the Java 17 discussion. But it was completely separate to the TC decision. It is a coordination and communication effort.
• Marc: Maybe the TC needs to let go that they are the decision makers so that they be a moderating group.
• Jakub: I agree with Marc. But we are not a system operating group. Dependency management should be in the responsibility of Release management. There are structures in the project for that.
• Jason Root: I agree with Jakub and with Marc also. Policies should drive operational/release/support aspects of Folio.
• Jason Root: If the idea of “support” is that frameworks are supported, then of course the project should meet that.
• Marc Johnson
  Some group needs to inform OleksAii when a relevant policy event occurs.
  These documents effectively ARE the manifestation of the policy.
• Craig: This is a topic for the next Monday session.

• Craig to see if Oleksii Petrenko could join us to discuss the process for updating the officially supported technologies lists.