SIG Scalability / Release Team process improvements

[guineveresaenger]

Per agenda item in #806, we should schedule once-monthly f2f meetings with:

• SIG Scalability +SIG Release Chairs + 1.17 RT Leads + CI Signal team throughout the cycle.

Notes for this effort available here.

• for 1.17 - Schedule meetings and invite folks on list above
• Add this action item to the CI Signal and RT Lead handbooks
• Add this item to SIG-Scalability process (up to the SIG 😄)
• Consider a Performance Engineering RT role or SIG Scalability liaison

/sig release
/sig scalability
/area release-team
/cc @alenkacz
/cc @alejandrox1
/cc @mariantalla
/cc @justaugustus
/cc @wojtek-t

/kind documentation
/milestone v1.17
/priority critical-urgent

[guineveresaenger]

Update 11/4:

@mariantalla will attend SIG-scalability's meeting this week, and put forward some of the questions mentioned in the draft doc.

[guineveresaenger]

Next TODO: schedule a November meeting with CI Signal leads

[guineveresaenger]

Summary for 1.17 team's progress on this:

• we have a weekly written update from a SIG representative in the release team agenda doc
• we have the CI Signal Lead communiacte with SIG-scalability on the regular
• we have sent a RT representative to SIG-scalability's regular meeting and checked in on specifics. (mentioned in the doc linked in this issue).

Going forward, we should:

• send a RT representative from Lead or CI team to SIg-scalability's regular meeting with questions, check-ins, and concerns (note they are in EU timezone so plan accordingly)
• establish expectation on part of SIG-scalability that we will need these updates and communications going forward
• update the requisite handbooks.

[justaugustus]

/assign @guineveresaenger @alejandrox1 @alenkacz @droslean

[guineveresaenger]

Handbooks are being updated via #917.