|
| 1 | +------------------------------------------------------------- |
| 2 | +name: Marko Mudrinić |
| 3 | +ID: xmudrii |
| 4 | +info: |
| 5 | + - employer: Kubermatic |
| 6 | + - slack: xmudrii |
| 7 | +------------------------------------------------------------- |
| 8 | + |
| 9 | +## SIGS |
| 10 | + |
| 11 | +- SIG Release (Release Engineering Subproject Lead and Release Manager) |
| 12 | +- SIG K8s Infra (Tech Lead) |
| 13 | + |
| 14 | +## What I have done |
| 15 | + |
| 16 | +I started contributing to Kubernetes in 2018 through a Google Summer of Code internship, where I worked with SIG API Machinery on improving aggregated API servers and CRDs. Shortly after, I began my journey with SIG Release. I have worked on important features and releases, mentored new Release Managers and SIG Release contributors, coordinated cross-SIG efforts, and much more. This led me to become a Release Manager and later a Subproject Lead for Release Engineering. |
| 17 | + |
| 18 | +In the meantime, I joined SIG K8s Infra to help optimize the Kubernetes infrastructure and cloud spending. My key achievements include building a new community-owned infrastructure for hosting and serving Debian and RPM packages, as well as being part of the team that built an AWS-based CI cluster and moved many jobs to it. |
| 19 | + |
| 20 | +I got several community awards, including a [Lift and Shift award from CNCF](https://www.cncf.io/announcements/2024/11/14/cloud-native-computing-foundation-announces-the-2024-community-awards-winners/) and four [Kubernetes Contributor awards](https://www.kubernetes.dev/community/awards/) (2024, two in 2023, and 2022). |
| 21 | + |
| 22 | +I've also been a [CNCF Ambassador](https://www.cncf.io/people/ambassadors/) since November 2023. |
| 23 | + |
| 24 | +## What I'll do |
| 25 | + |
| 26 | +Many open source projects are going through a hard time, including Kubernetes and its community. As a Steering Committee member, I would advocate for prioritizing efforts to mitigate the effects of that. The Steering Committee cannot fix technical problems, but it can support people and ensure the wellbeing of the project. |
| 27 | + |
| 28 | +I would especially stand for more support for SIGs by providing a clear set of guidelines with a focus on attracting new and retaining existing contributors, strengthening inclusivity, and further improving and documenting the contributor ladder. Besides that, I would especially stand for resolving one of the longest standing problems — having proper recognition for all the hard work done by our community members. The Kubernetes project can only succeed with a healthy community, where everyone can join, be welcomed, and feel valued. |
| 29 | + |
| 30 | +## Resources About Me |
| 31 | + |
| 32 | +- [GitHub](https://github.com/xmudrii) |
| 33 | +- [LinkedIn](https://linkedin.com/in/xmudrii/) |
| 34 | +- [Bluesky](https://bsky.app/profile/xmudrii.bsky.social) |
| 35 | +- [X (Twitter)](https://twitter.com/xmudrii) |
| 36 | +- [Talks playlist on YouTube](https://www.youtube.com/playlist?list=PLvNBqHHXyMOBufmiuBrIQvtgOp3smF1Jx) |
| 37 | +- My publications on kubernetes.io |
| 38 | + - [pkgs.k8s.io: Introducing Kubernetes Community-Owned Package Repositories](https://kubernetes.io/blog/2023/08/15/pkgs-k8s-io-introduction/) |
| 39 | + - [Kubernetes Legacy Package Repositories Will Be Frozen On September 13, 2023](https://kubernetes.io/blog/2023/08/31/legacy-package-repository-deprecation/) |
0 commit comments