Page Comparison

Florian Gleixner 

Reminder:  Please copy/paste the Zoom chat into the notes.  If you miss it, this is saved along with the meeting recording, but having it here has benefits.

Maccabee Levine Tod Olson  Jakub Skoczen  Craig McNally Jenn Colt 

• CC: Maccabee Levine
  
  • Two applications for the developer advocate position, group decides to invite one.
  • IndexData is dropping back from some adimistration tasks. Maybe Ebsco will take over some.
• PC: Tod Olson 
  • PC meetins meetings slot was used by the 3Tri-council meeting
• RMS Group: Jakub Skoczen 
  • No updates
• Security Team: Craig McNally No updates, triaging issues.
  • No important updates - business as usual
• Tri-council Application Formalization: Jenn Colt is not here.

All

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key TCR-33

  - update from Tod Olson No meeting

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key TCR-35

  - Jeremy Huff Meeting scheduled not yet started

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key TCR-36

  - Jeremy Huff as well

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key TCR-37

    - Jeremy Huff Ingolf Kuss Meeting scheduled

• 24 Jan 2024 - Topic either Officially supported technologies or Poppy database upgrade scripts? But Ingolf Kuss will first talk to the development teams. Decision will be made offline.
  31 Jan 2024 - TCR Process Improvements 

All

Quick updates only.  If we can't find volunteers for groups, we'll need to add the topic to our backlog and address it during dedicated discussion sessions.

• Configuration group - Nothing new, Olamide Kolawole will take a look at it and will comment provide comments.
• Breaking changes - Ankita is not here today
• Translations -
  • Craig McNally will try to raise topic at the councils again
  TCRs
  • chairs meeting again
  • Maccabee Levine Dropping it when other councils show no interest is OK, but we should note that.
  • Can be pushed as a DEI (Diversity, equity, and inclusion) issue
• TCR process improvements
  
  • Maccabee Levine
    •  Will present the draft to the TC on Jan. 31
    • Discussion how to get more people to participate in evaluations
  • Update next week
• Application formalization RF draft
  
  • Craig McNally is working on discussions/comments/questions. Some are resolved, but still work in progress

All

• Status/Updates:
  • Application Formalization RFC - DRAFT REFINEMENT PR:  https://github.com/folio-org/rfcs/pull/22
  • Go Programming Language for Backend Development RFC - PRELIMINARY REVIEW PR: https://github.com/folio-org/rfcs/pull/25
    
    • questions and comments are resolved
    • can advance to the next stage(s) probably up to the DRAFT REFINEMENT stage. Jakub Skoczen will work through the process
  • Distributed vs Centralized Configuration RFC - DRAFT REFINEMENT PR: https://github.com/folio-org/rfcs/pull/26 - Olamide Kolawole will help the group

RFC Process Improvements:

• We need another RFC to update the metadata retroactively to reflect the new or adjusted statuses. - Jenn Colt will do this, hasn't finished yet
  
  • nothing new today

Notes: see above

The announcements were made before the holidays.  Has anyone received questions / comments on this?  No objections. Probably need to ask testing people explicitely. 

See: DR-000038 - PostgreSQL Upgrade to 16

Notes:

Craig McNally will reach out to the Testmanager test manager to check if the postgres testing environments are ready to use 12 and 16.

Standing agenda item... is there anything in the decision log requiring attention?

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

• Check in on progress... does anything else require attention?
• Next Important Milestone:  Review Ramsons (3rd party dependencies) and move from DRAFT → ACCEPTED by 16 Feb 2024 
  • Maybe we should aim to start looking at this on 05 Feb 2024 so we have time for discussion/adjustments.
• Versions for the components:
  • Resume discussion at an upcoming dedicated topic discussion?

Notes:

Craig McNally Some entries have versions, some not. Last discussion did not lead to a conclusion. Sometimes versions come from dependencies and they are redundant. Probably we should remove versions on some to make things easier?

Marc Johnson Differentiate between infrastructure and other. We cannot support multiple postgres versions at once. Languages and build tools should be the same to make development easier.

Owen Stephens Developers should decide which version to use, TC should give guidelines like the software should be supported.

Marc Johnson For some things no versions work fine, but for some we have to have a common version, for example for stripes and postgres.

Craig McNally Maybe replace the versions on spring and so with links to the support lifecycle of the project

Marc Johnson noone is reviewing modules concerning used versions, so we should remove versions on some.

Tod Olson List supported technoligies technologies in flower release pages?

Owen Stephens Maybe list reasons, why a version is written, also helps to decide if we want to remove the versions

Marc Johnson will add reasons and links to Ramsons page.