docs: propose systematic SIG/WG activity tracking

[dhiller]

Summary

• Proposes extending existing org membership automation to cover SIG/WG leadership lifecycle, reviewer/approver cleanup, health checks, and retirement criteria
• Documents what KubeVirt already has in place (quarterly Prow periodic, contribution checker, emeritus_leads in sigs.yaml, inactivity policy in membership_policy.md, presubmit validation)
• Identifies remaining gaps and proposes 6 concrete actions to close them

Context

KubeVirt's quarterly periodic-community-remove-inactive-users-from-orgs-yaml Prow job already handles org-level membership hygiene. This proposal extends that model to SIG/WG chairs, leads, and OWNERS_ALIASES reviewers/approvers — areas where inactivity detection exists (via the contribution checker) but automated action does not.

Modeled after the Kubernetes community's SIG governance, tailored to KubeVirt's scale as a CNCF Incubating project.

🤖 Assisted by Claude Opus 4.6

[kubevirt-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign fabiand for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dhiller]

/cc @aburdenthehand

WDYT about this? Basically this came up as we noticed that i.e. wg-arch-arm has no active leader: https://github.com/kubevirt/community/blob/main/sig-list.md

[dhiller]

FYI @dollierp

[aburdenthehand]

@dhiller Thanks for proposing this. If I understand correctly then it is expanding the scope and complexity of what we currently automate for org membership, with additional governance concerns when it comes to SIGs/WGs in terms of flagging lagging leadership and retiring the group.
It looks good to me. I only have one question/quibble with having this in the root folder of this repo. Would it be better served in /design-proposals? Or could it serve as an issue if it's a static file of intended improvements?

[dhiller]

@dhiller Thanks for proposing this. If I understand correctly then it is expanding the scope and complexity of what we currently automate for org membership, with additional governance concerns when it comes to SIGs/WGs in terms of flagging lagging leadership and retiring the group. It looks good to me. I only have one question/quibble with having this in the root folder of this repo. Would it be better served in /design-proposals? Or could it serve as an issue if it's a static file of intended improvements?

Yeah, pretty much this. I was just noticing that i.e. a wg chair is absent for quite a while already and thus we might have a gap here, thus I brought this up.