Skip to content

Prune/shuffle projects under the kubernetes/*org  #5635

Open
@timothysc

Description

@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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/code-organizationIssues or PRs related to kubernetes code organizationarea/github-managementIssues or PRs related to GitHub Management subprojectcommittee/steeringDenotes an issue or PR intended to be handled by the steering committee.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/awaiting-more-evidenceLowest priority. Possibly useful, but not yet enough support to actually get it done.sig/architectureCategorizes an issue or PR as relevant to SIG Architecture.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions