2023-07-05 Meeting notes

Maccabee Levine  is next, followed by Tod Olson 

As of July 1, member-elect Taras Spashchenko is now officially a TC member, replacing Raman Auramau.  Welcome Taras, and thank you for your service Raman!

Wiki pages have been updated to reflect this change.

All

• TCR-27 - Getting issue details... STATUS draft PR
• Zak Burke waiting to hear back from the contact on that ticket, will follow up this week.

Maccabee Levine / Tod Olson / Jakub Skoczen 

• Updates from CC:
  • No meeting this week.
• Updates from PC:
  • Reported out from meeting in Chicago, 
  • Update on Developer Advocate role: CC looking for feedback before July 10 & 24 meetings; questions about how Dev. Adv. would interact with current development teams, and
    • Craig McNally : add ???
  • Sorted out election results and roles for the new PC.
  • No PC meeting this week.
• Updates from Release Management Stakeholder Group:
  • Jakub Skoczen not present so Mark Veksler shared.  CSP release delayed because of issues with QA environment, but will be released once they give green light.

All

• AWS Costs: later today
• Breaking changes: no update, Jeremy Huff unavailable
• Improve TCR process
  • Craig McNally next step is subgroup to review the video, then start sharing that link.
• Distributed / Centralized Configuration:
  • Florian Gleixner did a doodle poll, will start a recurring meeting next week.
• Architecture Review
  • Craig McNally : discussed in slack last week, will hold off until after WOLFcon since overlap with what VBar will be sharing.

• Previous notes:
  • 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.
  • From Craig McNally via #tech-council slack: 

Here's the retro board for the RFC retrospective scheduled for July 10.  Please add your cards prior to the meeting.
https://easyretro.io/publicboard/dY8fCRqguiSDP3wtvSLhNzlULdM2/61b6d545-2d94-4007-93fa-d6263efb49a1

Today:

• Everyone should look at retro board for RFC.

Maccabee Levine/ Craig McNally 

Previous notes:

• The deadline for submission ideas has past.
• No updates on shoulder sessions (TC or tri-council)
• Some agenda planning for the in-person meeting
• Expected in-person attendance of TC: 4 definitely, 2 maybe
• A Workflow SIG is being formed. Related to the work going on at TAMU on mod-workflow and mod-camunda. A kind of SIG-level guidance.

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

• Craig McNally : Jira to upgrade Grails from 4 to 5.  Proposed now.
  • Tod Olson Grails is a narrow set of modules?  Craig McNally yes, ERM
  • No disagreement.  Craig McNally will mark for Poppy & Quesnalia.
• Does this informal process make sense?
  • Consensus: fine for now.

Craig McNally 

• 10 Jul 2023 RFC Retrospective
• 17 Jul 2023 Application formalization
• 24 Jul 2023 Officially Supported Technologies - Upkeep Process
• 31 Jul 2023 
• 07 Aug 2023 
• 14 Aug 2023 
• 21 Aug 2023 WOLFcon 2023

Maccabee Levine 

Previous Notes:

• A workflow for these pages. When do they transition from one state to another. Do we even need statuses at all ?
• Stripes architecture group has some questions for the Poppy release.
• Zak: A handshake between developers, dev ops and the TC. Who makes that decision and how to we pass along that knowledge ? E.g. changes in Nodes and in the UI boxes. How to communicate this ? We have a large number of teams, all have to be aware of it.  TC should be alerted that changes are happening. We have a couple of dedicated channels for that. Most dev ops have subscribed to these channels. How can dev ops folk raise issues to the next level of community awareness ? There hasn't been a specific piece of TC to move that along.
• Craig: There is a fourth group, "Capacity Planning" or "Release Planning". Slack is the de facto communication channel.  There are no objections to using Slack. An example is the Java 17 RFC. 
• Craig: The TC gets it on the agenda and we will discuss it. The TC gets the final say.
• Marc Johnson: We shouldn’t use the DevOps Channel. The dev ops folks have made it clear that it should only be used for support requests made to them.
• Jakub: Our responsibility is to avoid piling up technical debt.
• Marc: Some set of people have to actually make the call. Who lowers the chequered flag ?
• Craig: It needs to ultimately come to the TC at least for awareness. There is a missing piece. Capacity Planning needs to provide input here. 
• Marc: Stakeholders / Capacity Planning could make that decision. Who makes the decision ? Is it the government or is it some parts of the body ?
• Marc: the developers community, the dev ops community and sys ops are involved. For example the Spring Framework discussion or the Java 17 discussion. But it was completely separate to the TC decision. It is a coordination and communication effort.
• Marc: Maybe the TC needs to let go that they are the decision makers so that they be a moderating group.
• Jakub: I agree with Marc. But we are not a system operating group. Dependency management should be in the responsibility of Release management. There are structures in the project for that.
• Jason Root: I agree with Jakub and with Marc also. Policies should drive operational/release/support aspects of Folio.
• Jason Root: If the idea of “support” is that frameworks are supported, then of course the project should meet that.
• Marc Johnson
  Some group needs to inform OleksAii when a relevant policy event occurs.
  These documents effectively ARE the manifestation of the policy.
• Craig: This is a topic for the next Monday session.

• Craig to see if Oleksii Petrenko could join us to discuss the process for updating the officially supported technologies lists.