Versions Compared

Key

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

...

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
1 minUpcoming MeetingsAll
  • - Regular TC meeting - Include Developer Advocate Update
  • - Dedicated dicussion: Static code group?
  • -  Regular TC meeting
  • - Dedicated discussion: ?
15 20 minTCR Board ReviewAll

Today:

  • Need approval of TCR-42

Last time:

mod-reporting, a Go rewrite of mod-ldp, has been submitted. As Go is not yet supported it requires work regarding static code checks, code coverage automation, etc.

We should first complete the existing TCR requests.


Should we merge the PR that removes the snapshot criterium from our module acceptance criterium? This will solve the issue with the TCR.

Depending on a SNAPSHOT version is bad practice. Maven rejects a release when trying to release a module with SNAPSHOT dependency. It is also bad practice during development because the build is not reproducible. However, as FOLIO libraries are provided as SNAPSHOT version only the modules are forced to use SNAPSHOT versions during development.

When merging the PR we can appove the submitted module without explaining why we overwrite the SNAPSHOT criterium.

Instead of removing the SNAPSHOT criterium it should be a requirement that can be ignored if reasonably justified.

A warning not to use a SNAPSHOT dependency is in the module release documentation for maven based modules: https://dev.folio.org/guidelines/release-procedures/#prepare-and-perform-the-source-release

We don't know how non-maven modules prevent SNAPSHOT dependencies.

It's up to the development teams how to prevent SNAPSHOT dependencies.


Go modul mod-reporting:

When accepted as a module we indirectly adopt Go as a language.

Should we first accept Go as a language including specific criteria regarding static code analysis, security, etc.?

In the past PoCs have been used to add new stuff to FOLIO without evaluation/approval.

We had been discussing the Go RfC for months.

Regarding adding the Go stack we need more feedback from the community.


5 min

Technical Council Sub-Groups Updates

All



1 minRFCs

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
1 minDecision LogAll

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

5-10 15 min

Officially Supported Technologies (OST)

All

Check Recurring Calendar...

We still need to transition the Sunflower page from DRAFT → ACCEPTED... ASAP.  What is preventing this from happening? 


*WOLFcon recapAll

Highlights from WOLFcon... Sessions, In-person TC meeting, Tri-council meeting, etc.

  • ...
NAZoom Chat



...