Notes - KubeVirt - SIGs - What's next? (Aug 17, 2023)

[Lee Yarwood]

Thanks again to everyone who attended for accommodating the earlier timeslot this week, apologies to folks who couldn't make it.

A recording is currently pending and will be updated in the agenda document once ready.

Please feel free to comment on the agenda if anything has been missed or if folks that didn't attend have questions!

https://docs.google.com/document/d/1yOtxWS2eIgA2VT71NbFaDEzGyVfmiDCwoRBHKow0K6c/edit 

Cheers,

Lee

Notes

• Recording: Pending

• Lee Yarwood - My current approach to these meetings and tasks

• Define the high level aspects of SIGs

• What is a SIG?

• How do we add and remove SIGs?

• Define our initial set of SIGs

• Populate an initial SIG with current kubevirt/kubevirt approvers and code-reviewers

• Create any required collateral for an initial SIG, such as documentation and slack channels etc.

• Apply this initial SIG to kubevirt/kubevirt as an example

• Repeat this process across other SIGs and subprojects

• Lee Yarwood - Still looking for feedback on the introduction to SIGs documentation: 

• https://github.com/kubevirt/community/pull/236/commits/7da6ba5b492024c243cd0038340660dce1c6289d 

• Lee Yarwood - Fabian Deutsch suggested the introduction of sig-governance to oversee the SIG process, any objections?

• Lee Yarwood I assume the group would be initially populated by the current MAINTAINERS list?

• Lee Yarwood I also assume they would follow something like https://github.com/kubernetes/community/blob/master/sig-wg-lifecycle.md 

• Lee Yarwood Agreed to hold off on introducing sig-governance until we’ve worked through the initial introduction and maybe even adding a single SIG to work out processes.

• Lee Yarwood - Also looking for feedback on the PR as a whole, especially the SIGs being introduced, removed and modified:

• https://github.com/kubevirt/community/pull/236

• Lee Yarwood - Was there agreement on moving all SIG related documentation and tracking to another repo?

• If so I can look into this ahead of the next call.

• Lee Yarwood not yet, everything remains in project-infra and community

• Andrew Burden Moving org.yaml to own folder: https://github.com/kubevirt/project-infra/pull/2933 

• Lee Yarwood - Was there agreement on using Charters?

• If so I can post an example in my community PR ahead of the next call.

• Lee Yarwood - Do we have automation to create and manage slack channels for each SIG?

• If so I can look into creating these ahead of the next call

• Andrew Burden: https://www.kubernetes.dev/docs/comms/slack/#requesting-a-channel
  But might need to do it in CNCF workspace

• Lee Yarwood - Once the above is in place or at least drafted I’d like to start to look at restructuring the OWNERS files within kubevirt/kubevirt to use these groups.

• Lee Yarwood - For now SMEs will not be discussed further until the initial SIG implementation is finished, if we still need SMEs at that point we can then look into introducing them.

Action items

• Lee Yarwood drop sig-api and sig-observability from PR for now and use it to run through SIG introduction process eventually.

• Lee Yarwood using sig-compute as an example, define an example charter, add a slack channel and draft changes to kubevirt/kubevirt.