Open timothysc opened 4 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/remove-lifecycle stale
cc: @kubernetes/owners
/milestone v1.19
Discussed this in the April 23 GitHub Management subproject meeting, there are currently no blockers to this.
The GH management team is going to take a look at this once incubator is wrapped up (https://github.com/kubernetes/community/issues/1922)
I confirmed with other steering committee members that this is fine to move - https://kubernetes.slack.com/archives/CPNFRNLTS/p1594800527229600
Moving to k/org
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/lifecycle frozen
Why I added the lowest priority label:
If someone feels strongly that this is important, and my reasoning above is incorrect, please help us out by providing a list of of suggestions and reasoning e.g.
- repo: kubernetes/foo
sig: sig-foo
subproject: https://git.k8s.io/community/sig-foo#awesome-foo
proposal: move to kubernetes-sigs/foo
reason: k8s.io/foo isn't used by any repo in the kubernetes org, but is a dependency of sigs.k8s.io/cluster-foo-* repos
- repo: kubernetes/bar
subproject: https://git.k8s.io/community/sig-foo#awesome-foo
proposal: retire
reason: k8s.io/bar was deprecated in favor of k8s.io/foo
- repo: kubernetes/qux
subproject: https://git.k8s.io/community/sig-foo#awesome-foo
proposal: remain
reason: k8s.io/qux is a dependency of a number of k8s.io repos
/sig contributor-experience /area github-management
/committee steering this originated from steering
/sig architecture this is the sig that decides whether new kubernetes org repos should be created, it seems fair to me they should decide which preexisting repos should not be in this org
/sig architecture this is the sig that decides whether new kubernetes org repos should be created, it seems fair to me they should decide which preexisting repos should not be in this org
cc @dims @derekwaynecarr @johnbelamaric
/area code-organization
@nikhita: The label(s) area/code-organization
cannot be applied, because the repository doesn't have them.
Moving to the k/community repo. See discussion in https://kubernetes.slack.com/archives/CHGFYJVAN/p1615820685088600?thread_ts=1615800656.087500&cid=CHGFYJVAN
From @spiffxp's comment above:
/sig contributor-experience /area github-management
/committee steering this originated from steering
/sig architecture /area code-organization this is the sig that decides whether new kubernetes org repos should be created, it seems fair to me they should decide which preexisting repos should not be in this org
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten
The Kubernetes project currently lacks enough active 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:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
/reopen /remove-lifecycle rotten
@MadhavJivrajani: Reopened this issue.
/lifecycle frozen
/priority awaiting-more-evidence https://github.com/kubernetes/community/issues/5635#issuecomment-795816729 explains why
(cleaning up SC project board) /unassign @spiffxp @cblecker @nikhita @mrbobbytables /help
@justaugustus: This request has been marked as needing help from a contributor.
Please ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help
command.
Over the course of the last year and a half we've created a tiered organizational structure and sigs are responsible for their subprojects. When inspecting the Kubernetes main org there is a lot of cruft repos that should either be shuffled to SIGs or moved to attic.