Versions Compared

Old Version 3

changes.mady.by.user Jeremy Huff

Saved on

compared with

New Version Current

changes.mady.by.user Jakub Skoczen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

5 10-15
TimeItemWhoNotes
1 minScribeAll
Jakub Skoczen is next, followed by Jenn Colt 

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

Maccabee Levine

Tod Olson

Jakub Skoczen

Craig McNally

Jenn Colt 

  • CC: Maccabee Levine 
    • no meeting this week
  • PC: Tod Olson
  • RMS Group: Jakub Skoczen
    • Quesnelia R1 is considered GO
    • RFC wording  to be added to the release timeline starting from Sunflower
  • Security Team: Craig McNally
    • Updates regarding planned penetration testing
  • Tri-council Application Formalization: Jenn Colt
    • Met last week but no firm conclusion on the next steps
    • the group is going to meet over the summer on a lighter schedule
1 minUpcoming MeetingsAll
  •  - 8pm EST meeting for China and Australia topics
  •   - Regular TC Meeting
  •   - Dedicated Discussion - Topic TBD
  •   - Regular TC Meeting
  •   - Dedicated Discussion - Topic TBD
  •   - Regular TC Meeting
  •   - Dedicated Discussion - Topic TBD
4 1 minTCR Board ReviewAll
  • Jeremy Huff action item regarding TCR-41 (mod-reading-room) to reach out to the PC: the item is not on the PC's radar so TC should wait and hold off with assigning the evaluator
  • Discussion if the TC should head start on the evaluation without PCs approval
  • Maccabee Levine: one of the evaluation criteria requires that the module is approved by the PC before the TC can accept it
5 min

Technical Council Sub-Groups Updates

All

5

1 minRFCs

All

  • Application Formalization: When will we do the final review?
    • The following Monday  
5 1 minAction Items

Jeremy Huff

10-15 minGo Language RFCJakub Skoczen

We will begin the final review of the Go Language RFC: https://github.com/folio-org/rfcs/pull/33

  • Jakub Skoczen: summarized the RFC and updates that were made to the RFC
  • Craig McNally: general concerns about extending the OST list, tooling (especially CI/CD tooling like static code and security analysis like Snyk or SonarQube)
  • Maccabee Levine: should we first identify what the CI/CD tooling requirements are?
  • Jakub Skoczen: the proposal is that we discover this as part of the module PoC
  • Maccabee Levine: proposed to update the RFC so that the iterative nature is explicitly mentioned
  • Jeremy Huff: there are benefits if the project is open to new technologies
  • Craig McNally: underlines that Snyk or similar is supported
  • Jakub Skoczen: a security scanning tool must be supported but it's unclear if it needs to be Snyk
  • Taras Spashchenko: Go may not support libraries or extensions required for building business logic in FOLIO. FOLIO community may be missing Go knowledge to support projects written in Go
  • Marc Johnson: Go may increase the cost for maintaining infrastructure, etc 

TC voited in favour of the RFC with 6 votes for, 1 vote against and 2 abstained

5- 10 minDeveloper Advocate Service Board PreviewPatrick Pace (Unlicensed)Patrick will demonstrate the new Jira Service board for interfacing with the Developer Advocate, to solicit feedback from the TC. https://folio-org.atlassian.net/jira/servicedesk/projects/DA
10 - 15 minTopics For upcoming dedicated discussion All

Review the suggested topics from SHL and NLA

1 minDecision LogAll


Time Permitting

Officially Supported Technologies (OST)

All

Standing agenda item to review/discuss any requested or required changes to officially supported technology lists

NAZoom Chat

...