k8s-triage-robot
commented
7 months ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
jsoref
I've just spent some time browsing https://www.kubernetes.dev/docs/onboarding/ and I don't think it was remotely helpful.
Nothing in any of this content gives any hint to anyone as to how to identify a SIG or AREA or a working group or a committee for that matter for an issue or a PR for https://github.com/kubernetes/kubernetes/ .
Nothing in it explains that if you make a PR, a bot might automatically suggest the proper something. And really, nothing suggests a way to figure out how the bot determines the right answer so you could do the same for an issue in case you've identified the precise file but don't have code ready to fix the issue. (Or are justifiably intimidated by the bots.)q