Open dims opened 3 years ago
/assign
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Ugh, my bad - I let this drop. It's back on my radar
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale /lifecycle frozen
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:
We can use the same for things that we identify not necessarily from the annual report as well.