|
| 1 | +--- |
| 2 | +layout: blog |
| 3 | +title: "Spotlight on SIG ContribEx" |
| 4 | +date: 2023-08-14 |
| 5 | +slug: sig-contribex-spotlight-2023 |
| 6 | +canonicalUrl: https://www.kubernetes.dev/blog/2023/08/14/sig-contribex-spotlight-2023/ |
| 7 | +--- |
| 8 | + |
| 9 | +**Author**: Fyka Ansari |
| 10 | + |
| 11 | +Welcome to the world of Kubernetes and its vibrant contributor |
| 12 | +community! In this blog post, we'll be shining a spotlight on the |
| 13 | +[Special Interest Group for Contributor |
| 14 | +Experience](https://github.com/kubernetes/community/blob/master/sig-contributor-experience/README.md) |
| 15 | +(SIG ContribEx), an essential component of the Kubernetes project. |
| 16 | + |
| 17 | +SIG ContribEx in Kubernetes is responsible for developing and |
| 18 | +maintaining a healthy and productive community of contributors to the |
| 19 | +project. This involves identifying and addressing bottlenecks that may |
| 20 | +hinder the project's growth and feature velocity, such as pull request |
| 21 | +latency and the number of open pull requests and issues. |
| 22 | + |
| 23 | +SIG ContribEx works to improve the overall contributor experience by |
| 24 | +creating and maintaining guidelines, tools, and processes that |
| 25 | +facilitate collaboration and communication among contributors. They |
| 26 | +also focus on community building and support, including outreach |
| 27 | +programs and mentorship initiatives to onboard and retain new |
| 28 | +contributors. |
| 29 | + |
| 30 | +Ultimately, the role of SIG ContribEx is to foster a welcoming and |
| 31 | +inclusive environment that encourages contribution and supports the |
| 32 | +long-term sustainability of the Kubernetes project. |
| 33 | + |
| 34 | +In this blog post, [Fyka Ansari](https://twitter.com/1fyka) interviews |
| 35 | +[Kaslin Fields](https://twitter.com/kaslinfields), a DevRel Engineer |
| 36 | +at Google, who is a chair of SIG ContribEx, and [Madhav |
| 37 | +Jivrajani](https://twitter.com/MadhavJivrajani), a Software Engineer |
| 38 | +at VMWare who serves as a SIG ContribEx Tech Lead. This interview |
| 39 | +covers various aspects of SIG ContribEx, including current |
| 40 | +initiatives, exciting developments, and how interested individuals can |
| 41 | +get involved and contribute to the group. It provides valuable |
| 42 | +insights into the workings of SIG ContribEx and highlights the |
| 43 | +importance of its role in the Kubernetes ecosystem. |
| 44 | + |
| 45 | +### Introductions |
| 46 | + |
| 47 | +**Fyka:** Let's start by diving into your background and how you got |
| 48 | +involved in the Kubernetes ecosystem. Can you tell us more about that |
| 49 | +journey? |
| 50 | + |
| 51 | +**Kaslin:** I first got involved in the Kubernetes ecosystem through |
| 52 | +my mentor, Jonathan Rippy, who introduced me to containers during my |
| 53 | +early days in tech. Eventually, I transitioned to a team working with |
| 54 | +containers, which sparked my interest in Kubernetes when it was |
| 55 | +announced. While researching Kubernetes in that role, I eagerly sought |
| 56 | +opportunities to engage with the containers/Kubernetes community. It |
| 57 | +was not until my subsequent job that I found a suitable role to |
| 58 | +contribute consistently. I joined SIG ContribEx, specifically in the |
| 59 | +Contributor Comms subproject, to both deepen my knowledge of |
| 60 | +Kubernetes and support the community better. |
| 61 | + |
| 62 | +**Madhav:** My journey with Kubernetes began when I was a student, |
| 63 | +searching for interesting and exciting projects to work on. With my |
| 64 | +peers, I discovered open source and attended The New Contributor |
| 65 | +Workshop organized by the Kubernetes community. The workshop not only |
| 66 | +provided valuable insights into the community structure but also gave |
| 67 | +me a sense of warmth and welcome, which motivated me to join and |
| 68 | +remain involved. I realized that collaboration is at the heart of |
| 69 | +open-source communities, and to get answers and support, I needed to |
| 70 | +contribute and do my part. I started working on issues in ContribEx, |
| 71 | +particularly focusing on GitHub automation, despite not fully |
| 72 | +understanding the task at first. I continued to contribute for various |
| 73 | +technical and non-technical aspects of the project, finding it to be |
| 74 | +one of the most professionally rewarding experiences in my life. |
| 75 | + |
| 76 | +**Fyka:** That's such an inspiration in itself! I'm sure beginners who |
| 77 | +are reading this got the ultimate motivation to take their first |
| 78 | +steps. Embracing the Learning journey, seeking mentorship, and |
| 79 | +engaging with the Kubernetes community can pave the way for exciting |
| 80 | +opportunities in the tech industry. Your stories proved the importance |
| 81 | +of starting small and being proactive, just like Madhav said Don't be |
| 82 | +afraid to take on tasks, even if you're uncertain at first. |
| 83 | + |
| 84 | +### Primary goals and scope |
| 85 | + |
| 86 | +**Fyka:** Given your experience as a member of SIG ContribEx, could |
| 87 | +you tell us a bit about the group's primary goals and initiatives? Its |
| 88 | +current focus areas? What do you see as the scope of SIG ContribEx and |
| 89 | +the impact it has on the Kubernetes community? |
| 90 | + |
| 91 | +**Kaslin:** SIG ContribEx's primary goals are to simplify the |
| 92 | +contributions of Kubernetes contributors and foster a welcoming |
| 93 | +community. It collaborates with other Kubernetes SIGs, such as |
| 94 | +planning the Contributor Summit at KubeCon, ensuring it meets the |
| 95 | +needs of various groups. The group's impact is evident in projects |
| 96 | +like updating org membership policies and managing critical platforms |
| 97 | +like Zoom, YouTube, and Slack. Its scope encompasses making the |
| 98 | +contributor experience smoother and supporting the overall Kubernetes |
| 99 | +community. |
| 100 | + |
| 101 | +**Madhav:** The Kubernetes project has vertical SIGs and cross-cutting |
| 102 | +SIGs, ContribEx is a deeply cross-cutting SIG, impacting virtually |
| 103 | +every area of the Kubernetes community. Adding to Kaslin, |
| 104 | +sustainability in the Kubernetes project and community is critical now |
| 105 | +more than ever, it plays a central role in addressing critical issues, |
| 106 | +such as maintainer succession, by facilitating cohorts for SIGs to |
| 107 | +train experienced community members to take on leadership |
| 108 | +roles. Excellent examples include SIG CLI and SIG Apps, leading to the |
| 109 | +onboarding of new reviewers. Additionally, SIG ContribEx is essential |
| 110 | +in managing GitHub automation tools, including bots and commands used |
| 111 | +by contributors for interacting with [Prow](https://docs.prow.k8s.io/) |
| 112 | +and other automation (label syncing, group and GitHub team management, |
| 113 | +etc). |
| 114 | + |
| 115 | +### Beginner's guide! |
| 116 | + |
| 117 | +**Fyka:** I'll never forget talking to Kaslin when I joined the |
| 118 | +community and needed help with contributing. Kaslin, your quick and |
| 119 | +clear answers were a huge help in getting me started. Can you both |
| 120 | +give some tips for people new to contributing to Kubernetes? What |
| 121 | +makes SIG ContribEx a great starting point? Why should beginners and |
| 122 | +current contributors consider it? And what cool opportunities are |
| 123 | +there for newbies to jump in? |
| 124 | + |
| 125 | +**Kaslin:** If you want to contribute to Kubernetes for the first |
| 126 | +time, it can be overwhelming to know where to start. A good option is |
| 127 | +to join SIG ContribEx as it offers great opportunities to know and |
| 128 | +serve the community. Within SIG ContribEx, various subprojects allow |
| 129 | +you to explore different parts of the Kubernetes project while you |
| 130 | +learn how contributions work. Once you know a bit more, it’s common |
| 131 | +for you to move to other SIGs within the project, and we think that’s |
| 132 | +wonderful. While many newcomers look for "good first issues" to start |
| 133 | +with, these opportunities can be scarce and get claimed |
| 134 | +quickly. Instead, the real benefit lies in attending meetings and |
| 135 | +getting to know the community. As you learn more about the project and |
| 136 | +the people involved, you'll be better equipped to offer your help, and |
| 137 | +the community will be more inclined to seek your assistance when |
| 138 | +needed. As a co-lead for the Contributor Comms subproject, I can |
| 139 | +confidently say that it's an excellent place for beginners to get |
| 140 | +involved. We have supportive leads and particularly beginner-friendly |
| 141 | +projects too. |
| 142 | + |
| 143 | +**Madhav:** To begin, read the [SIG |
| 144 | +README](https://github.com/kubernetes/community/tree/master#readme) on |
| 145 | +GitHub, which provides an overview of the projects the SIG |
| 146 | +manages. While attending meetings is beneficial for all SIGs, it's |
| 147 | +especially recommended for SIG ContribEx, as each subproject gets |
| 148 | +dedicated slots for updates and areas that need help. If you can't |
| 149 | +attend in real-time due to time zone differences, you can catch the |
| 150 | +meeting recordings or |
| 151 | +[Notes](https://docs.google.com/document/d/1K3vjCZ9C3LwYrOJOhztQtFuDQCe-urv-ewx1bI8IPVQ/edit?usp=sharing) |
| 152 | +later. |
| 153 | + |
| 154 | +### Skills you learn! |
| 155 | + |
| 156 | +**Fyka:** What skills do you look for when bringing in new |
| 157 | +contributors to SIG ContribEx, from passion to expertise? |
| 158 | +Additionally, what skills can contributors expect to develop while |
| 159 | +working with SIG ContribEx? |
| 160 | + |
| 161 | +**Kaslin:** Skills folks need to have or will acquire vary depending |
| 162 | +on what area of ContribEx they work upon. Even within a subproject, a |
| 163 | +range of skills can be useful and/or developed. For example, the tech |
| 164 | +lead role involves technical tasks and overseeing automation, while |
| 165 | +the social media lead role requires excellent communication |
| 166 | +skills. Working with SIG ContribEx allows contributors to acquire |
| 167 | +various skills based on their chosen subproject. By participating in |
| 168 | +meetings, listening, learning, and taking on tasks related to their |
| 169 | +interests, they can develop and hone these skills. Some subprojects |
| 170 | +may require more specialized skills, like program management for the |
| 171 | +mentoring project, but all contributors can benefit from offering |
| 172 | +their talents to help teach others and contribute to the community. |
| 173 | + |
| 174 | +### Sub-projects under SIG ContribEx |
| 175 | + |
| 176 | +**Fyka:** SIG ContribEx has several smaller projects. Can you tell me |
| 177 | +about the aims of these projects and how they've impacted the |
| 178 | +Kubernetes community? |
| 179 | + |
| 180 | +**Kaslin:** Some SIGs have one or two subprojects and some have none |
| 181 | +at all, but in SIG ContribEx, we have ELEVEN! |
| 182 | + |
| 183 | +Here’s a list of them and their respective mission statements |
| 184 | + |
| 185 | +1. **Community**: Manages the community repository, documentation, |
| 186 | + and operations. |
| 187 | +2. **Community management**: Handles communication platforms and |
| 188 | + policies for the community. |
| 189 | +3. **Contributor-comms**: Focuses on promoting the success of |
| 190 | + Kubernetes contributors through marketing. |
| 191 | +4. **Contributors-documentation**: Writes and maintains documentation |
| 192 | + for contributing to Kubernetes. |
| 193 | +5. **Devstats**: Maintains and updates the [Kubernetes |
| 194 | + statistics](https://k8s.devstats.cncf.io) website. |
| 195 | +6. **Elections**: Oversees community elections and maintains related |
| 196 | + documentation and software. |
| 197 | +7. **Events**: Organizes contributor-focused events like the |
| 198 | + Contributor Summit. |
| 199 | +8. **Github management**: Manages permissions, repositories, and |
| 200 | + groups on GitHub. |
| 201 | +9. **Mentoring**: Develop programs to help contributors progress in |
| 202 | + their contributions. |
| 203 | +10. **Sigs-GitHub-actions**: Repository for GitHub actions related to |
| 204 | + all SIGs in Kubernetes. |
| 205 | +11. **Slack-infra**: Creates and maintains tools and automation for |
| 206 | + Kubernetes Slack. |
| 207 | + |
| 208 | + |
| 209 | +**Madhav:** Also, Devstats is critical from a sustainability |
| 210 | +standpoint! |
| 211 | + |
| 212 | +_(If you are willing to learn more and get involved with any of these |
| 213 | +sub-projects, check out the_ [SIG ContribEx |
| 214 | +README](https://github.com/kubernetes/community/blob/master/sig-contributor-experience/README.md#subprojects))._ |
| 215 | + |
| 216 | +### Accomplishments |
| 217 | + |
| 218 | +**Fyka:** With that said, any SIG-related accomplishment that you’re |
| 219 | +proud of? |
| 220 | + |
| 221 | +**Kaslin:** I'm proud of the accomplishments made by SIG ContribEx and |
| 222 | +its contributors in supporting the community. Some of the recent |
| 223 | +achievements include: |
| 224 | + |
| 225 | +1. _Establishment of the elections subproject_: Kubernetes is a massive |
| 226 | + project, and ensuring smooth leadership transitions is |
| 227 | + crucial. The contributors in this subproject organize fair and |
| 228 | + consistent elections, which helps keep the project running |
| 229 | + effectively. |
| 230 | +2. _New issue triage proces_: With such a large open-source project |
| 231 | + like Kubernetes, there's always a lot of work to be done. To |
| 232 | + ensure things progress safely, we implemented new labels and |
| 233 | + updated functionality for issue triage using our PROW tool. This |
| 234 | + reduces bottlenecks in the workflow and allows leaders to |
| 235 | + accomplish more. |
| 236 | +3. _New org membership requirements_: Becoming an org member in |
| 237 | + Kubernetes can be overwhelming for newcomers. We view org |
| 238 | + membership as a significant milestone for contributors aiming to |
| 239 | + take on leadership roles. We recently updated the rules to |
| 240 | + automatically remove privileges from inactive members, making sure |
| 241 | + that the right people have access to the necessary tools and |
| 242 | + responsibilities. |
| 243 | + |
| 244 | +Overall, these accomplishments have greatly benefited our fellow |
| 245 | +contributors and strengthened the Kubernetes community. |
| 246 | + |
| 247 | +### Upcoming initiatives |
| 248 | + |
| 249 | +**Fyka:** Could you give us a sneak peek into what's next for the |
| 250 | +group? We're excited to hear about upcoming projects and initiatives |
| 251 | +from this dynamic team. |
| 252 | + |
| 253 | +**Madhav:** We’d love for more groups to sign up for mentoring |
| 254 | +cohorts! We’re probably going to have to spend some time polishing the |
| 255 | +process around that. |
| 256 | + |
| 257 | +### Final thoughts |
| 258 | + |
| 259 | +**Fyka:** As we wrap up our conversation, would you like to share some |
| 260 | +final thoughts for those interested in contributing to SIG ContribEx |
| 261 | +or getting involved with Kubernetes? |
| 262 | + |
| 263 | +**Madhav**: Kubernetes is meant to be overwhelming and difficult |
| 264 | +initially! You’re coming into something that’s taken multiple people, |
| 265 | +from multiple countries, multiple years to build. Embrace that |
| 266 | +diversity! Use the high entropy initially to collide around and gain |
| 267 | +as much knowledge about the project and community as possible before |
| 268 | +you decide to settle in your niche. |
| 269 | + |
| 270 | +**Fyka:** Thank You Madhav and Kaslin, it was an absolute pleasure |
| 271 | +chatting about SIG ContribEx and your experiences as a member. It's |
| 272 | +clear that the role of SIG ContribEx in Kubernetes is significant and |
| 273 | +essential, ensuring scalability, growth and productivity, and I hope |
| 274 | +this interview inspires more people to get involved and contribute to |
| 275 | +Kubernetes. I wish SIG ContribEx all the best, and can't wait to see |
| 276 | +what exciting things lie ahead! |
| 277 | + |
| 278 | +## What next? |
| 279 | + |
| 280 | +We love meeting new contributors and helping them in investigating |
| 281 | +different Kubernetes project spaces. If you are interested in getting |
| 282 | +more involved with SIG ContribEx, here are some resources for you to |
| 283 | +get started: |
| 284 | + |
| 285 | +* [GitHub](https://github.com/kubernetes/community/tree/master/sig-contributor-experience#contributor-experience-special-interest-group) |
| 286 | +* [Mailing list](https://groups.google.com/g/kubernetes-sig-contribex) |
| 287 | +* [Open Community |
| 288 | + Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fcontributor-experience) |
| 289 | +* [Slack](https://slack.k8s.io/) |
| 290 | +* [Slack channel |
| 291 | + #sig-contribex](https://kubernetes.slack.com/messages/sig-contribex) |
| 292 | +* SIG Contribex also hosted a [KubeCon |
| 293 | + talk](https://youtu.be/5Bs1bs6iFmY) about studying Kubernetes |
| 294 | + Contributor experiences. |
0 commit comments