/
2024-03-18 Meeting notes

2024-03-18 Meeting notes

Date

Attendees 


Discussion items

TimeItemWhoNotes
1 minScribeAll

Maccabee Levine is next, followed by Craig McNally

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.

5-10 minLiaison Updates
  • CC: Maccabee Levine
    • No meeting this week
  • PC: Tod Olson
    • Discussion about Roadmap and Prioritization process.  Writing how requirements are written.  WOLFcon topic ideas.
    • TC should discuss its own topic suggestions (future dedicated discussion).
  • RMS Group: Jakub Skoczen 
    • Jakub not available
  • Security Team: Craig McNally 
    • Craig not available
  • Tri-council Application Formalization: Jenn Colt 
    • Jenn will post the questions for the week as usual.
5 minUpcoming MeetingsAll
  •  - Dedicated Discussion - Static Code Analysis (maybe)
  •  - Regular TC meeting
  •  - Dedicated Discussion - Topic TBD
  •  - Regular TC meeting
  •  - Dedicated Discussion - Topic TBD
  •  - Regular TC meeting
  •  - Dedicated Discussion - Topic TBD
10-15 min

Technical Council Sub Groups Updates

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

Go RFC

  • Subgroup is over, not in draft refinement anymore.

Distributed vs. Centralized Config RFC

  • Subgroup is over, not in draft refinement anymore.

TCR Process Improvements

  • Language recommendation communicated to RSMG this morning.

App Formalization RFC

  • Subgroup is over, not in draft refinement anymore.
10 minRFCs

All

  • Public review update
    • Application Formalization RFC
    • Go Programming Language for Backend Development RFC
    • Distributed vs Centralized Configuration RFC - is in public Review
1 minDecision LogAll

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

30minTCR Board ReviewAll, Maccabee Levine and Ingolf Kuss

TCR-40 MOD-Serials Ingolf Kuss:

  • Present Evaluation Continued
    • https://github.com/folio-org/tech-council/pull/70/files/
    • Most criteria passed.  Two did not.
      • Grails 6.  Module is on Grails 5.  True for all Groovy/Grails modules.  Team has committed to Grails 6 when Quesnelia is out.  Would not prevent Ingolf from preventing module; issue is larger than this module.
      • Test coverage up to 64%.  Brought down because of Grails dynamic code generation.
    • Recommend approving module.
  • Technical Council Review
    • Dev team and TC agree it will be Grails 6 by Quesnelia release.  Components have to upgrade to Grails 6 before the modules.  Working on mod-agreements upgrade first before mod-serials-management.  Goal to resolve all upgrades by end of week.
    • Jeremy Huff concerned about setting a precedent about static code analysis.  Need discussion to evolve process so a module can demonstrate the quality in an effective way, but not allow modules that don't.  Test coverage is a poor proxy for quality, but it is a common & useful one, so good to have in place.  Agree with explanation about generated code, not interested in coverage for that, but interested in coverage on original code.
      • Ingolf Kuss entire notion of unit tests doesn't apply here, using integration tests.  Then what tool, Jacoco.
      • Jeremy Huff 80% coverage of original code in automated testing is what is important to me.  Not unit vs integration.
      • Tod Olson specific requirements because we're trying to be objective.  Run into trouble with edge cases.  More important to meet the purpose of the requirements vs rigid boundaries.
      • Marc Johnson we agreed last week to disregard the language thing.  Issue of whether we accept coverage of real code.