Prune/shuffle projects under the kubernetes/*org

[timothysc]

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.

[fejta-bot]

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

[nikhita]

/remove-lifecycle stale

[cblecker]

cc: @kubernetes/owners

[spiffxp]

/milestone v1.19

[nikhita]

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 (#1922)

[nikhita]

I confirmed with other steering committee members that this is fine to move - https://kubernetes.slack.com/archives/CPNFRNLTS/p1594800527229600

Moving to k/org

[fejta-bot]

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

[nikhita]

/lifecycle frozen

[spiffxp]

Why I added the lowest priority label:

• I really feel like this is going to continue to get punted because this team is super busy all over the project, and this is a high-activation-energy issue
• Pushing this forward will involve time and energy and a lot of people (e.g. if packages are getting renamed)
• Speaking for myself at least, I'm not super motivated to take this on without understanding why the community will appreciate this vs. feel like we're generating a lot of churn/drama

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

[nikhita]

/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

[nikhita]

/area code-organization

[k8s-ci-robot]

@nikhita: The label(s) area/code-organization cannot be applied, because the repository doesn't have them.

In response to this:

/area code-organization

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[nikhita]

Moving to the k/community repo. See discussion in https://kubernetes.slack.com/archives/CHGFYJVAN/p1615820685088600?thread_ts=1615800656.087500&cid=CHGFYJVAN

[nikhita]

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

[fejta-bot]

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

[fejta-bot]

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

[k8s-triage-robot]

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:

• 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:

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

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

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:

• 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:

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

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

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[MadhavJivrajani]

/reopen
/remove-lifecycle rotten

[k8s-ci-robot]

@MadhavJivrajani: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[MadhavJivrajani]

/lifecycle frozen

[spiffxp]

/priority awaiting-more-evidence
#5635 (comment) explains why

[justaugustus]

(cleaning up SC project board)
/unassign @spiffxp @cblecker @nikhita @mrbobbytables
/help

[k8s-ci-robot]

@justaugustus:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

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.

In response to this:

(cleaning up SC project board)
/unassign @spiffxp @cblecker @nikhita @mrbobbytables
/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.