Rough Notes - temporary until Jason's wiki problems are sorted out:
Code Block
PC Updates: App consistency, esp. across UI
Nothing from CC
PC: Reporting in Folio - Multuple options. What is the PC's role in finding the direction in the ecosystem - how does the PC navigate that?
RMS: No
Sec Group: No
Tri-council: Upcoming meeting scheduled
TCR-44 upcoming topic
SCRATCH THAT!
23rd open
Julian will link story in TCR-44 for mod-reporting
Marc: GO might change dependency in code analysis group if the toolset is changed
RFCs: Circling back to RFC that ended (44)
Static Code analysis
mod-reporting criteria approved?
Golang - adopt or not - may or may not be a pre-req. because Go not in an official supported lang.
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 privledge of modules?
Suggests reframing 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
TAMU's position on the TC - going to be put forward, not thru the election process.
Jackub needs to confirm with Index Data/Mike G.
Tech Council - probably go to a vote
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.
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?
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