Page Comparison

Jason Root is next, followed by Jakub Skoczen

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
  • ...Nothing from CC
• PC: Marc Johnson (covering for Tod Olson)
  • ...Reporting in Folio - Multiple options. What is the PC's role in finding the direction in the ecosystem - how does the PC navigate that?
• RMS Group:
  • ...No updates
• Security Team: 
  • Business as usual
• Tri-council Application Formalization:  
  • ...Upcoming meeting has been scheduled

• 23 Oct 2024 - Dedicated discussion: TBD
• 24 Oct 2024 - Community Update (PC meeting & time slot)
• 28 Oct 2024 - Regular TC meeting
• 30 Oct 2024 - Dedicated discussion: TBDGolang - w/ guests (David Crossley or someone else from DevOps familiar with what was done for CI/CD for Go modules)
• 04 Nov 2024 - Regular TC meeting

Today:

Julian Ladisch will link story in TCR-44 for mod-reporting

Marc says: Go might change dependency in code analysis group if the tool-set is changed

All

Reminder(s)

• Review of open items, such as the need for decision log records and the application of the "Go" RFC.
  • Still need merge and decision log entry
• The RFC Process document was never updated after adopting the wiki-based approach.
  • Any volunteers to take a swing at cleaning this up?  In theory the process is quite similar, only the parts about branching and creating PRs should be adjusted.
  • Should we try to update it as we move through the RFC process for 0010-eureka?

Today:

• Craig McNally has migrated the RFC template to the wiki:  RFC Template (Title goes here)
• FQM RFC - What is the status of this?
  • VBar is out this week, but Craig McNally did sync-up with him on this last week.  An RFC was written and nearly complete a while ago, but never made it across the finish line.  Vince asks for guidance on how to proceed:
    • Option #1 - Finish up the RFC page which represents the state from last year OR
    • Option #2 - Update it to reflect the latest state of FQM - including things like the security improvements covered at WOLFcon
    • Also, should the page be reformatted to:
      • Conform to the wiki-based RFC template? OR
      • Convert it to more of a documentation / whitepaper page - which could then become a living document
• 0010-eureka - Preliminary Review
  • Review:  Summary, Scope, Motivation, and Timing.

Notes:

• Static Code analysis
  • mod-reporting criteria approved?
• Golang - adopt or not - may or may not be a prerequisite because Go not in the list of officially supported language
• RFC Template: Craig pulled together the template from Git to Wiki
  • Craig asked for thoughts on how to clean up the process doc
  • Marc recalls doing a run-thru 1st
  • Craig will update 2 stages after the meeting

• FQM: It was written, but not really touched - did not cross the finish line

  • Marc mentioned one of the ideas behind RFC process - The amount of effort was supposed to decrease, keep it high level

  • Cross-database access privilege of modules?

  • Marc suggests re-framing RFCs to be more about policies and less about the details - Maccabee agrees

• Two things that are important to the RFC:

  • Cross-database module access?

  • One-off or not for this process?

• Eureka RFC: Abstract is ready from Craig, copy and paste from Ebsco's own internal docs

Need to log decisions for the following:  (see above)

Check Recurring Calendar...