contributor-site icon indicating copy to clipboard operation
contributor-site copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Onboarding doesn't explain how to identify a SIG/AREA/WG/Committee for an issue/PR

Open jsoref opened this issue 1 year ago • 6 comments

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

jsoref avatar Dec 08 '23 14:12 jsoref

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/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 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

k8s-triage-robot avatar Mar 07 '24 15:03 k8s-triage-robot

/remove-lifecycle stale

jsoref avatar Mar 07 '24 15:03 jsoref

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/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 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

k8s-triage-robot avatar Jun 05 '24 16:06 k8s-triage-robot

/remove-lifecycle stale

jsoref avatar Jun 05 '24 16:06 jsoref

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/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 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

k8s-triage-robot avatar Sep 03 '24 16:09 k8s-triage-robot

/remove-lifecycle stale

jsoref avatar Sep 03 '24 16:09 jsoref