2023-06-07 Meeting notes

Florian Gleixner is next, followed by Jeremy Huff 

All

• TCR-27 - Getting issue details... STATUS
  • Maccabee Levine offered to shadow the evaluator

Maccabee Levine / Tod Olson / Jakub Skoczen 

• updates from CC: 
• updates from the PC:
• updates from CSP:

Results are in. 

The following were elected to the Technical Council:

• Tod Olson (University of Chicago)
• Craig McNally (EBSCO Information Services)
• Marc Johnson (Knowledge Integration)
• Jakub Skoczen (Index Data)
• Taras Spashchenko (EPAM)

Congratulations!

Effectively, the only change is Raman will be replaced by Taras.  This change officially takes effect July 1.  

Craig McNally will reach out to Taras Spashchenko to see if he'd like to start attending sooner to get involved sooner.

Do we want to revisit roles, or are we happy to keep things as-is?  Wait until after July 1, or at least until Taras is present?

• Chair
• Deputy-chair
• Liaisons to PC/CC

Maccabee Levine 

• Call out for ideas for WOLFcon sessions is out.
• Deadline for submission has been extended to 19 Jun 2023 

All

• 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
• 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

Craig McNally 

• 12 Jun 2023 Continuation of our conversation about Cross-tenant/consortia and tenant checks.  Calendar already updated.
• 19 Jun 2023 is holiday for several members - probably won't meet 

• 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:

• Zak Burke more time is needed to collect support from the community

Today:

• Update on where this stands?
• Zak Burke A slack channel is created, there was a good discussion on this recently; keep this in the agenda for 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