Page Comparison

 Tod Olson is next, followed by Ankita Sen

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
  • Ongoing shift of Index Data stepping back from work around Jenkin, CI, etc. and looking for replacement. EBSCO offered a costed option.
  • FOLIO community trying to generate more money, CC can only do so much; funding AWS might mean community dev advocate cannot go forward. Not really getting new members in, rates willing to pay are not going up.
    • How to sell membership, what influence do members have? Perception is that some libraries are paying for SaS, but not being active in the larger community.
  • Paula Sullenger is stepping down as Treasurer
• PC: Tod Olson 
  • Retro on the last six months of Evaluation Process for New FOLIO Functionality.
  • EasyRetro: Evaluation Process for new FOLIO Functionality: PC Review Process
  • Most development by vendors is for given customers, will happen due to contractual obligations, point here is to ensure that these development done is such a was as to work for the community as a whole.
  • Compared to TC, PC process is more qualitative, more concerned with opinions of the community.
• RMS Group: Jakub Skoczen 
• Security Team: Craig McNally No updates, triaging issues.
  • No important updates - business as usual
• Tri-council Application Formalization: Jenn Colt 
  • No meeting last week, working on council questions this week

All

• TCR-37 (and TCR-35 and TCR-36)
  • TCR-37 moving forward, have list of questions for the developers
• TCR-33
  • In progress, would like to bring to TC on Monday
• Deadline on both is March 1st
• Expect Serials app to come to PC and TC soon-ish. (Had gone to PC months ago, but no formal decision.)

• 14 Feb 2024 - Dedicated Topic Discussion - Ramsons Page moving from DRAFT to ACCEPTED soon
• 19 Feb 2024 - Regular TC Meeting
• 21 Feb 2024 - Communicating Breaking Changes

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.

Distributed / Centralized Config

• going to public review as soon as we can

Communicating Breaking Changes

• Wednesday topic?

Translation

• Was discussed at the Folio chairs meeting.  TC has an action item to make sure details are documented in the JIRA/elsewhere.  If so, leave a comment in the Jira at-mentioning the submitter suggesting an RFC.

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

• Want to work with Knowledgeware on an RFC
• Will set aside time during a M or W meeting to go over this

TCR Process Improvements

• Working on communications plan for subgroup meeting next week.

Application Formalization

• Have followed up on comment threads, waiting for input confirming can close comments.

All

• Application Formalization RFC - DRAFT REFINEMENT PR:  https://github.com/folio-org/rfcs/pull/22
  • Comment threads responded to.  Still waiting to hear back if these can be resolved or not...
• Go Programming Language for Backend Development RFC - PRELIMINARY REVIEW PR: https://github.com/folio-org/rfcs/pull/25
  • From last week:
    
    • Jakub Skoczen will finish steps on Preliminary Review, push to next phase, Draft Refinement.  Get feedback from TC members and others.
    • Subgroup volunteers: Jeremy Huff Matt Weaver Ingolf Kuss 
    • Ensure we have membership from people familiar and not familiar with Go.  Maybe post in #development
• Distributed vs Centralized Configuration RFC - DRAFT REFINEMENT PR: https://github.com/folio-org/rfcs/pull/26

RFC Process Improvements:

• We need another RFC to update the metadata retroactively to reflect the new or adjusted statuses. - Jenn Colt

The announcements were made before the holidays.  No objections. Probably need to ask testing people explicitly. 

See: DR-000038 - PostgreSQL Upgrade to 16

Notes:

• Craig McNally had a call with Yogesh Kumar and Oleksii Petrenko.  There were some questions for FSE which have been answered.  Follow-up conversations will happen this week.

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

• No, not this week

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
• Notes from this meeting:
  • Maccabee Levine described updates to the process examples and walked through the example with Craig McNally who raised minor amendments
  • Marc Johnson suggested that there will only be 2 releases in 2024. Owen Stephens  and Craig McNally asked if anyone was aware of an official announcement on this
  • Craig McNally asked when there would be 4 active flower releases? Marc Johnson advised that there will be 4 releases when the previous 2 are in support, the current one is being released (and has not become generally available) and the next release has started development (after the feature freeze for the current release)
  • Marc Johnson shared the draft inclusion of policy decisions and reasoning for each type of technology in the Ramsons OST page
    
    • Craig McNally asked TC members to provide feedback on these changes

Notes:

• Marc Johnson last week fixed an OST example about timing at feature development freeze.
• TCR Process Improvement PR now refers to "most recent ACTIVE" release.
• Ramsons will move to ACCEPTED later this month 2/16.  So should start looking at it.
  • This means we have to now (by 2/16) nail down the third-party dependencies.
  • Need versions on FE languages.  Need FE review of FE build tools, etc.  Craig McNally flagged Zak Burke Yogesh Kumar on various parts of the page.
  • BE: No plans to move to new Java, Groovy.  Julian Ladisch made several wiki page comments on versions.
  • For "unspecified versions" items, we should not be listing versions?  Have to either adopt new policy or not.
• We'll discuss this Wednesday.
• Marc Johnson brief recap:
  • Three policies and reasons behind them.
    • Unspecified Versions. 
      • Dev teams take responsibility for using the latest version they can sensibly use.  Needs to be supported. 
      • TC doesn't dictate version because the version doesn't have to be aligned across modules.  It may be de facto aligned anyway, i.e. Vertx may be constrained by version of RAML Modules.  Similarly FOLIO Spring Base.  Or Stripes will dictate the version of React.
    • One of Specified Versions. 
      • Expect module developers to comply with one of the specified versions, i.e. Java 17 or 21.  The platform will support both.  Individual modules just need to run on one or the other.
    • All of Specified Versions. 
      • Modules are supposed to work with all of the specified versions.  I.e. Postgres during Quesnelia, modules have to work with 14-17.  At any one time it would only be run with one, but has to be able to run with any of them.
  • Allocation of each software to a policy depends how much project-wide alignment we need about that tool.  There is a reasoning statement for each one explaining why.
• Craig McNally helpful to link to products' support pages so dev teams can see which versions are supported easily.  Not a blocker on Ramsons moving to ACCEPTED.
  • Marc Johnson agree
  • Everyone read to be able to discuss on Wednesday.
  • Glossary will be moved out of Ramsons page.  Maybe to a separate page or the OST homepage.