2024-03-20 - WOLFCon Proposals and Static Code Analysis

• Individual council meetings after WOLFcon in addition to the Tri-council meeting?
  • If so, let's nail down details sooner than last time so those attending can make the necessary travel plans.
  • WOLFcon planning has apparently already allocated time for these council meetings.  Tod Olson will find out details.
  • Some members term limits will mean they will not be TC members at WOLFcon (including Jeremy).
  • Do we want to make this an open or closed meeting? 
• How exactly do we see Roll-on/off of TC members working in general?
  • What about chairs?  Do we select someone to take Jeremy's spot before the election?
  • We need to be careful about who we select so that we don't have both chairs term limits running up at the same time.
  • Maybe this is a good topic for a dedicated discussion next Wednesday?
• Potential topics for WOLFcon...
  • Applying the TCR process to existing modules
    • Give the community an update on where things stand, plans, etc.
    • While we don't typically have many devs at WOLFcon, we do have POs.
    • The expectation is there there will be many opinions on this
    • Even if Jeremy's assumption that we will be further along on what this mechanism might look like by WOLFcon isn't false, the feeling is that there are still aspects of this which are worth discussing at WOLFcon, e.g. possibly a workshop?
      • Potentially look closer at the criteria... the criteria we think are directly applicable, and gaps where the criteria is insufficient, or unnecessary.
    • Who is interested in participating?
      • Jeremy Huff
        • The feeling is that official TC membership is not a requirement for being involved in planning/running this discussion/workshop.  It's more important to be familiar with the current process, criteria, etc.
      • Maccabee Levine
    • How sure is the TC that they want to evaluate existing modules?
      • Yes for fairness, to address technical debt, etc.
    • Discussion delved into the specifics/details of this.  It's clear there's plenty to discuss and there's sufficient interested to warrant a WOLFcon session
  • Managing Technical Debt?
  • Recent RFCs?
    • golang → e.g. Folio as a polyglot
    • application formalization / bounded contexts / architectural PoC 
      • It's very likely that EBSCO will have sessions on these topics, but details are still TBD.
  • TC relationship with dev teams.  How can we improve how these two entities interact?
    • Will likely need to touch on things like what power does the TC actually have
    • Maybe the developer advocate plays a role here?
    • Revive tech leads group?
    • Is it worthwhile to have more developer participation at WOLFcon?  Even if virtually?
• Likelihood of the March 31 deadline being pushed out?  Tod Olson has heard that it will be, but nothing is official yet.

The FOLIO Security Team runs Snyk's Static Application Security Testing (SAST) Tool on all https://github.com/folio-org/ repositories, see Snyk.

Not discussed - we ran out of time.

11:09:27 From Jenn Colt to Everyone:
I’m up for re-election also (but not required roll off)
11:09:31 From Maccabee Levine to Everyone:
https://folio-org.atlassian.net/wiki/spaces/TC/pages/5052393/Technical+Council+Membership+History
11:09:56 From Maccabee Levine to Everyone:
Looks to me like Jeremy is actually the only one ending his second term this summer
11:10:04 From Craig McNally to Everyone:
Reacted to "Looks to me like Jer..." with 👍
11:10:11 From Maccabee Levine to Everyone:
(Lots of people next summer)
11:10:40 From Jenn Colt to Everyone:
And make sure there are virtual options
11:10:48 From Jenn Colt to Everyone:
Someone elected in summer might not be able to get funding
11:11:46 From Jenn Colt to Everyone:
It’s an election though...
11:25:26 From Maccabee Levine to Everyone:
I'd be willing to be involved in that
11:25:40 From Maccabee Levine to Everyone:
Pending discussion of other proposals :)
11:28:05 From Marc Johnson to Everyone:
Does the TC really want to do this?
11:32:12 From Jenn Colt to Everyone:
https://folio-org.atlassian.net/wiki/spaces/TC/pages/59637761/2024-02-28+-+Criteria+for+evaluating+existing+modules
11:32:56 From Maccabee Levine to Everyone:
Reacted to "https://folio-org.at..." with 👍🏻
11:33:47 From Ingolf Kuss to Everyone:
How often would exsiting modules be (re-)evaluated ? It is not practical to evaluate all (100 ?) modules of a release each release.
11:35:49 From Jenn Colt to Everyone:
Introducing yet another evaluation that will be overridden frequently in favor of practicalities is not super enticing
11:36:01 From Ingolf Kuss to Everyone:
Reacted to "Introducing yet anot..." with 👍
11:36:12 From Maccabee Levine to Everyone:
"Existing FOLIO modules ideally conform to the same Values and Criteria. It is understoo