kubernetes / kubernetes/community
process for summit team shadows
Open
area/contributor-summit
lifecycle/frozen
sig/contributor-experience
- Dominant language
- Jupyter Notebook
- Stars
- 13k
- Forks
- 5.4k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 29
Description
recruiting shadows for future events outside of setting a github link needs some work. maybe we can mirror the release process and include a form? scribing this issue so we remember.
Contributor guide
Research direction
Review the existing release process and the current summit shadow recruiting flow described in this issue. Define the desired form and GitHub-link workflow, then document the process so future event shadow recruitment has a clear, repeatable path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100