Skip to content

Commit 1b6f332

Browse files
cbleckernatalisucks
andcommitted
Add candidate bio for Natali Vlatko (natalisucks)
Co-Authored-By: Natali Vlatko <[email protected]>
1 parent a46daf1 commit 1b6f332

File tree

1 file changed

+37
-0
lines changed

1 file changed

+37
-0
lines changed
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
-------------------------------------------------------------
2+
name: Natali Vlatko
3+
ID: natalisucks
4+
info:
5+
- employer: Cisco
6+
- slack: Natali
7+
-------------------------------------------------------------
8+
9+
## SIGS
10+
11+
- SIG Docs / Co-Chair
12+
- SIG Contributor Experience / Contributor Summit Team, Maintainer Summit 2025 Program Chair
13+
- SIG Release / v1.30 Release Comms Shadow
14+
15+
## What I have done
16+
17+
I've served as the Co-chair of SIG Docs since 2022, with my Kubernetes contribution journey starting in 2020 via SIG Auth. Some highlights:
18+
- I led the launch of the official Localization Subproject for Kubernetes, which earned me the [2021 Kubernetes Contributor Award](https://www.kubernetes.dev/community/awards/2021/) for SIG Docs. Kubernetes documentation is now available in 16 different languages, and I spearheaded greater recognition of localization contributions via Kubernetes organization membership for new contributors
19+
- I helped launch the regular issue triage sessions for SIG Auth. This triaging helped the SIG organize work on various KEPs, such as [improvements to the KMS API](https://kubernetes.io/blog/2022/09/09/kms-v2-improvements/)
20+
- I've lead several areas for the Kubernetes Contributor Summit since 2021, and am currently Program Chair of the CNCF Manintainer Summit across EU (London) and NA (Atlanta) for 2025
21+
- I served on the Release Team for v1.30 as a Release Comms Shadow to foster greater collaboration between my SIG and the Release Team
22+
23+
24+
## What I’ll do
25+
26+
The Steering Committee has lacked gender diversity for many years. One of my motivations for running has been to address this issue, which means that voting for either Kat, Priyanka, Rita, or myself could unlock the ability for Steering to return to the Maintainer Track at KubeCon/CloudNativeCon and speak directly to users and new potential contributors. I believe that Kat, Priyanka, Rita, and I are all exceptional leaders who can represent Kubernetes well if we, as a community, choose to prioritize better representation of our maintainers.
27+
As for me, I plan to continue working for the project authentically and transparently. I have served on various steering committees and understand that this is an operational role, meant to help bridge collaboration gaps that exist across ownership areas of the project. This also means triaging the whims of major cloud providers, while ensuring maintainers can still feel supported by our governance and processes. I like helping people achieve great things, and that's what I want to be doing as an elected member of Steering.
28+
29+
## Resources About Me
30+
31+
- Some of my KubeCon/CloudNativeCon talks:
32+
- [Bridge the Gap to OSS Adoption With Documentation: A Kubernetes Story (KubeCon/CloudNativeCon EU 2025)](https://www.youtube.com/watch?v=Q40yLLLIW9Q)
33+
- [Dungeons and Deployments v2: The Clusters of Chaos (KubeCon/CloudNativeCon EU 2024)](https://youtu.be/EWJ6Ih_bQbo?si=XRuQ7zcivfFEoz0L)
34+
- [Dungeons and Deployments: Leveling Up in Kubernetes (KubeCon/CloudNativeCon NA 2023)](https://youtu.be/-CPrDLFM1Aw?si=i-hPLzvFZHg5mAdr)
35+
- [How To Localize Kubernetes Documentation: A Guide For Everyone (KubeCon/CloudNativeCon EU 2023)](https://kccnceu2023.sched.com/event/1HyUP)
36+
- Find me on [GitHub](https://github.com/natalisucks)
37+
- Check out my [LinkedIn](https://www.linkedin.com/in/natalivlatko)

0 commit comments

Comments
 (0)