kubernetes / kubernetes/community
Prune/shuffle projects under the kubernetes/*org
Open
area/code-organization
area/github-management
committee/steering
help wanted
lifecycle/frozen
priority/awaiting-more-evidence
sig/architecture
sig/contributor-experience
- Dominant language
- Jupyter Notebook
- Stars
- 13k
- Forks
- 5.4k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 29
Description
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.
Contributor guide
Research direction
Start by reviewing the repositories in the Kubernetes main organization against the tiered organizational structure described in the issue. Identify repositories that should move to a SIG or the attic, then confirm that each affected repository has an agreed destination; the issue does not name specific repositories or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100