TAG Workshop
summary
Continues the London thread by defining a technical community group vs a TAG, treating initiatives as time‑bound artifacts with one tech lead each, and asking tags to limit active initiatives; uses the TOC repository board to track status but notes missing tag labels and plans a stalebot to auto‑archive stalled items. Breakouts produce notes uploaded to the tag drive and action items for the public TOC call, with follow‑ups scheduled post‑KubeCon.
AI-written summary · about
chapters (7)
- 0:00TAG workshop intro
- 1:27TAGs vs community groups
- 4:21Initiatives and TOC
- 8:01Managing initiative progress
- 10:27Initiative terms and processes
- 12:55Breakout sessions
- 15:09Follow-up actions
related talks
52mBuild Your Own Tech Radar, Capture Your Org's Tech Posture
31mTurn Contributors into Maintainers with TAG Contributor Strategy
34mScaling the Developer Frontier: The TAG DevEx Roadmap for 2026
31mInsights From a k8s Newcomer Working Within the Release Process - Tim Pepper
31mThe Maintainer's Toolkit: Must-know CNCF Resources for Project O...
30mIntro: Kubernetes Contributor Experience SIG
01mProject Lightning Talks: Closing
43mTechnical Communities - What Next?
