2024-04-15 Meeting notes

Date

15 Apr 2024

Attendees

Discussion items

Time	Item	Who	Notes
1 min	Scribe	All	Jakub Skoczen is next, followed by Florian Gleixner 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 min	Liaison Updates	Maccabee Levine Tod Olson Jakub Skoczen Craig McNally Jenn Colt	CC: Maccabee Levine PC: Tod Olson No PC meeting last week RMS Group: Jakub Skoczen Security Team: Craig McNally Tri-council Application Formalization: Jenn Colt
5 min	Upcoming Meetings	All	17 Apr 2024 - Dedicated Discussion - Officially Supported Technologies - Upkeep 22 Apr 2024 - Regular TC meeting 24 Apr 2024 - Dedicated Discussion - Confirmed POC Q&A. POC Info: Architectural PoC Preview Feedback - ~~https://docs.google.com/spreadsheets/d/1zzW2I1xMhdUpkclQRE2NvCcvx6JlNYUG4aTOiaYraJ4/edit#gid=1733306425~~ 29 Apr 2024 - Regular TC meeting 01 May 2024 - Dedicated Discussion - Communicating Breaking Changes 06 May 2024 - Regular TC meeting
4 min	TCR Board Review	All	TCR-38: Florian Gleixner – no updates Nothing new
5-10 min	Technical Council Sub Groups Updates	All	Jeremy: a subgroup to be formed regarding static code analysis as a potential SonarCloud replacement
5 min	RFCs	All	Go: Jakub will set a final date for the public review of the RFC and announce it, conversations to be resolved, unresolved ones to be added under the "unresolved" section in the RFC App formalization: new comments added, Craig will take a look
1 min	Decision Log	All	Standing agenda item... is there anything in the decision log requiring attention?
5 min	Action Item Updates	All	Wolfcon Submission Developer Channels Slack Communication Developer Advocate Update – Jeremy will meet Patrick, the Dev Advocate soon Craig: the Dev Advocate position is for 6 months. there is a budget for an extension but we'll want to revisit Maccabee: we've gotten specific enough for the first month and given a broad description of the positions, afterward may be a good idea for the DA to come back and propose specific goals
10-15 min	Consolidation of Developer Documentation	All	Currently, Developer Documentation exists in several locations: dev.folio.org the folio wiki within GitHub repositories During last Wednesday's dedicated discussion, there seemed to be a loose consensus around the idea of consolidating this documentation into a single location. We should discuss if this is a course of action that we would like to take, and if so, how this can be done. Marc: should this be the decision for the DA to make? Maccabee: it seems that there is a general conflict about general documents on the dev site vs the wiki, arguments for not losing specific contents from the website Jeremy: the TC could define some goals for the DA but not prescribe how Jen: since the migration to the Cloud, the quality of results from the wiki is not great Jen: it might be a big project so it should be considered if that's what the DA should focus on Macabbee: docs are a time-sink,
Time Permitting	Officially Supported Technologies (OST)	All	Standing agenda item to review/discuss any requested or required changes to officially sup