2023-06-14 Meeting notes

Jeremy Huff is next, followed by Marc Johnson 

All

• TCR-27 - Getting issue details... STATUS
  • ...

Maccabee Levine / Tod Olson / Jakub Skoczen 

• updates from CC: 
  • Maccabee Levine via slack:

There was a brief discussion about the funding proposals from TC and PC;  they were initially focused only on the joint TC/PC Community Developer Advocate proposal which Alexis, Owen and I recently updated, but I reminded them there were several others as well submitted by the two councils.  CC has not made progress on defining a process to consider them but recommitted to doing so before the next meeting.  And it sounds like they will meet at WOLFcon to consider the proposals specifically.

• updates from the PC Tod Olson :
  • List App: EBSCO heard from a lot of former Innovative Interfaces customers that they really wanted actionable lists, the List App is being developed, to be offered to the community. Expect review requests to PC and TC.
  • WOLFcon planning update: 56 proposals as of meeting time, room for some more.
  • Tomorrow: Browser support statement will be a topic in PC. Have already introduced in Slack, expect PC to discuss and vote tomorrow.
• updates from CSP group:
  • ...

Maccabee Levine/ Craig McNally 

• Call out for ideas for WOLFcon sessions is out.
• Deadline for submission has been extended to 19 Jun 2023 
• A shoulder session request has been submitted for Friday 25 Aug 2023 (morning)
• Possibly Cross-council shoulder session(s) Friday 25 Aug 2023 (afternoon)
  • Was discussed at Folio Chairs meeting, specifics/details are TBD

All

• ...

Discuss as a group and try to reach a decision, then updated the DR.

See DR-000034 - Java 17 Support

Java 11 Support ends Sept. 2023

Development freeze for Poppy was yesterday, so migrating all modules to Java 17 will not work for Poppy, but support for Poppy runs longer than Java 11 support.

Marc Johnson Merging Poppy and Quesnelia may be rather skipping the release schedule for Poppy and the next Release will still be named Poppy, but it is not clear and confusing. This affects updating the officially supported technologies page.

Craig McNally proposes to update the DRs scope to "the release happening toward the end of this year".  After some discussion, changed to "For the release happening in Fall/Q4 2023 (release name to be added later) all java-based FOLIO modules must be implemented using Java 17, and the use of Java 11 for FOLIO modules is no longer acceptable."

The TC accepts the DR using lazy consensus.

Today:

• Leaving this on the agenda as a reminder to update the DR once a decision has been made about the P/Q release(s).

• Java 17 RFC - let's close this one - who has the ball here?
• Wrapping up the Kafka topics RFC
  • PR is merged; the next step - Final Review stage; the discussion will continue next week, hopefully, with voting
  • Marc Johnson Different options require decision which option is in officially tested. Mark Veksler This will be considered in testing environments.
  • Accepted using lazy consensus
  • Next is a Post review, Craig McNally will do a doodle poll
  • Olamide Kolawole will write a DR
• Cleanup effort required:
  • filename prefix - all RFCs currently use 0000- defeating the purpose
  • conflicting process documentation between the wiki and github...
  • renaming can be done by RFC submitters, leave comments on the RFCs that still need it
  • Jenn will take on the documentation clean up, Work has started, some discussion in tc-internal slack.

Today:

• Instead of a doodle poll, should we just use a Monday time slot?
• Status of DR?
• How do we indicate that the RFC has been approved/accepted?  Looking at GitHub it isn't clear to me.

Craig McNally 

• 12 Jun 2023 Continuation of our conversation about Cross-tenant/consortia and tenant checks.  Calendar already updated. Olamide Kolawole explained some details in last meeting.
  • Cancelled due to scheduling confusion
• 19 Jun 2023 is holiday for several members - probably won't meet 
• 26 Jun 2023 Continuation of our conversation about Cross-tenant/consortia and tenant checks.  Calendar already updated. Olamide Kolawole explained some details in last meeting
  • I need someone to run this meeting as I'll be out on vacation.
• 03 Jul 2023 RFC Retrospective?

• Craig McNally successfully locked down the pages so that only TC members can edit
• Craig McNally will roll out the headers to the remaining pages
• Review the page status enumeration from the perspective of how/when/which modules are affected
• Lock down is done, headers are there and now labels are added so things are appearing as they should be! Good progress.
• Does "accepting" imply once and done or can things circle back through the statuses? How do we expect the statuses to drive what we are going to do? What process ties the statuses together?
• It would be helpful to have a workflow diagram (like what JIRA has) about how the statuses transition from one to another. Need something written down.
  • As far as new modules, trying to show only the active one applies to a module being released right now
• Some process is needed because of impact on scope. Impact can be at product level because of scope but the knowledge is at the dev level.
• RFC too heavyweight for these decisions
  • Due diligence/communication to not surprise people
  • Who needs to be told? PO meeting and they communicate back
• Bring to a monday meeting
• ADRs might be a good solution
• Should move Poppy to active, need to get Quesnelia up soon

Today:

• Didn't get to this today - defer to next week.

• Craig McNally the term "platform" is something that we wanted to revisit but the terminology document otherwise has been accepted by the three councils
• Craig McNally what is the urgency on this?
• Jenn Colt has been talking with Marc Johnson on Slack and was thinking that could be part of a larger conversation about architecture
• Marc Johnson is okay leading this conversation and rolling it into the Architecture discussion,  we could use platform as the first topic on the Architecture sub-group
• The Folio Chairs were asking if we thought this could be sorted out in time for WOLFcon...