Approach to handling policy related outcomes from Annual Reports (and elsewhere)

[dims]

There have been instances of things we mandate policy-wise / governance-wise for SIGs and WGs. The recent Annual Reports process has surfaced some of the disconnects and hardships faced by SIGs and WGs in following them. So what we need to think through here is how to get to the point where we track things we need SIGs to fix up and/or figure out how to make things easier given these trying times.

So the steps probably would look like this:

• Identify things that seem to not work well across SIGs
• Discuss the value of these things to the overall community
• Open Github Issues with detailed why(s) and exactly what needs to be done by SIGs and WGs
• Detail owners in various SIGs that can help rectify a specific item
• Track over time with full transparency to get things back into compliance

We can use the same for things that we identify not necessarily from the annual report as well.

[parispittman]

#207

[mrbobbytables]

/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[dims]

/remove-lifecycle stale

[mrbobbytables]

Ugh, my bad - I let this drop. It's back on my radar

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[mrbobbytables]

/remove-lifecycle stale
/lifecycle frozen