|
| 1 | +------------------------------------------------------------- |
| 2 | +name: Kat Cosgrove |
| 3 | +ID: katcosgrove |
| 4 | +info: |
| 5 | + - employer: Minimus |
| 6 | + - slack: katcosgrove |
| 7 | +------------------------------------------------------------- |
| 8 | + |
| 9 | + |
| 10 | +## SIGS |
| 11 | + |
| 12 | +- SIG Release |
| 13 | + - Release Team Subproject Lead |
| 14 | + - v1.30 Release Lead |
| 15 | + - v1.29 Docs Lead |
| 16 | + - v1.27 Release Lead Shadow |
| 17 | + - v1.26 Release Lead Shadow |
| 18 | + - v1.25 Comms Lead |
| 19 | + |
| 20 | +- SIG Docs |
| 21 | + - Technical Lead |
| 22 | + |
| 23 | +## What I have done |
| 24 | + |
| 25 | +I joined Kubernetes in 2020 during the fallout of the Dockershim deprecation, quelling community fears in the wake of the deprecation and ahead of the actual removal. In 2021, I joined the Release Team. Since then, the number of subteams required to release Kubernetes has been reduced from six to four while the number of KEPs has steadily increased, without increasing the workload for SIGs. Many of the improvements to the Release Team have been due to better collaboration and improved processes with SIG Docs, SIG Node, and SIG Architecture. |
| 26 | + |
| 27 | +During the v1.28 release, I was awarded [SIG Release Contributor of the Year](https://www.kubernetes.dev/community/awards/2023/#release). As v1.30 lead, I managed the merging of CI Signal and Bug Triage. I also implemented a [Docs Freeze](https://github.com/kubernetes/sig-release/blob/master/releases/release_phases.md#docs-freeze) phase, drastically reducing the workload for SIG Docs and Release Docs. |
| 28 | + |
| 29 | +## What I'll do |
| 30 | + |
| 31 | +The Release Team is required to efficiently collaborate across SIGs, giving me a high-level view of the difficulties all parts of the project face with respect to contributor acquisition and onboarding and cross-team collaboration. I intend to bring those skills to fill gaps in processes that make collaborative progress more difficult than necessary. My number one goal is ensuring a Kubernetes that is safe, efficient, and actively pleasant for our contributors and our users. |
| 32 | + |
| 33 | +## Resources About Me |
| 34 | + |
| 35 | +- Some of my talks: |
| 36 | + - [Dungeons and Deployments v2: The Clusters of Chaos (KubeCon EU 2024)](https://youtu.be/EWJ6Ih_bQbo?si=XRuQ7zcivfFEoz0L) |
| 37 | + - [Dungeons and Deployments: Leveling Up in Kubernetes (KubeCon NA 2023)](https://youtu.be/-CPrDLFM1Aw?si=i-hPLzvFZHg5mAdr) |
| 38 | + - [Fly me to the Moon: A Kubernetes Origin Story (KCD UK Keynote)](https://www.youtube.com/watch?v=Pe9V1hG4LUQ) |
| 39 | + - [Planning for Maturity: SIG Release’s Revamp for More Stable Kubernetes (KubeCon EU 2024)](https://www.youtube.com/watch?v=UhIXUarNPKc) |
| 40 | + - [We Didn’t Start the Fire: Communication Breakdowns and How to Prevent Them (KubeCon EU 2021)](https://www.youtube.com/watch?v=a03Hh1kd6KE) |
| 41 | + |
| 42 | + |
| 43 | +- Other talks and appearances: |
| 44 | + - [Don’t Panic: Kubernetes and Docker](https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/) |
| 45 | + - [Dockershim: The Historical Context](https://kubernetes.io/blog/2022/05/03/dockershim-historical-context/) |
| 46 | + - [Is your cluster ready for v1.24?](https://kubernetes.io/blog/2022/03/31/ready-for-dockershim-removal/) |
| 47 | + |
| 48 | +- About me |
| 49 | + - [Nomination](https://github.com/kubernetes/community/issues/8584) |
| 50 | + - [GitHub](https://github.com/katcosgrove) |
| 51 | + - [LinkedIn](https://linkedin.com/in/katcosgrove) |
0 commit comments