From 19e8c3dce37dd66c7af7a00398f86680584e500f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Frederico=20Mu=C3=B1oz?= Date: Mon, 27 Mar 2023 09:38:59 +0100 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Josh Berkus Co-authored-by: Tim Bannister --- .../blog/2023/from-zero-to-subproject-lead.md | 21 ++++++++++--------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/content/en/blog/2023/from-zero-to-subproject-lead.md b/content/en/blog/2023/from-zero-to-subproject-lead.md index 28059f4a0..b7e4e7c0d 100644 --- a/content/en/blog/2023/from-zero-to-subproject-lead.md +++ b/content/en/blog/2023/from-zero-to-subproject-lead.md @@ -7,18 +7,18 @@ author: "Ala Dewberry (VMware)" --- Getting started in any open-source community can be daunting, especially if it’s a big one like -Kubernetes. I wanted to write this post to share my experience and encourage others to join up. All +Kubernetes. I wrote this post to share my experience and encourage others to join up. All it takes is some curiosity and a willingness to show up! Here’s how my journey unfolded at a high level: 1. What am I interested in? Is there a SIG (Special Interest Group) or a WG (Working Group) that is dedicated to that topic, or something similar?  -2. Sign up for their mailing list and start hopping on meetings! +2. Sign up for their mailing list and start hopping on meetings. 3. When (never if!) there are opportunities to help out and it aligns with your skills and desired - growth areas, raise your hand! + growth areas, raise your hand. 4. Ask for lots of help and don’t be shy about not knowing everything (or anything!) -5. Keep plugging along, even if progress isn’t as fast as you would like it to be +5. Keep plugging along, even if progress isn’t as fast as you would like it to be. ## Starting up @@ -28,7 +28,7 @@ show up and participate will be so much easier if you think what you are doing i interesting. Likewise, continued participation is what keeps the community thriving, so that interest will drive you to have more of an impact.  -The following is also essential - it’s ok to show up knowing nothing! I remember showing up knowing +Also: it’s ok to show up knowing nothing! I remember showing up knowing very little about Kubernetes or how the community itself worked. And while I know more about how the community functions today, I am still learning all the time about it and the project. Fortunately, the community is full of friendly people who want to help you learn. Learning as you go is expected @@ -38,9 +38,10 @@ cheer and help you along the way.  This method was my exact story. It was my first or second meeting with [SIG Security](https://github.com/kubernetes/community/tree/master/sig-security), and [Pushkar Joglekar](https://github.com/PushkarJ) mentioned that he needed a lead for a subproject he was -creating after having done a security assessment of CAPI. Everyone was so friendly in the meeting -that I thought - hey, why not try it out? And since then, I have received so much support and -encouragement from my co-leads who are delighted to have me, _especially_ because I am a beginner: +creating after having done a security assessment of [Cluster API](https://cluster-api.sigs.k8s.io/). +Everyone was so friendly in the meeting +that I thought, "Hey, why not try it out?" And since then, I have received so much support and +encouragement from my co-leads who are delighted to have me, _especially_ because I am a beginner; new participation is what keeps the community healthy. ## Always learning @@ -54,8 +55,8 @@ transparent, inviting way simply takes time.  I also have to be patient with myself and remember that I am learning as I go. The [Kubernetes git repo](https://github.com/kubernetes/kubernetes) can be daunting to navigate. Knowing the next best -step isn’t always obvious. But this is where my third learning curve - how to engage the community -to get what I need - comes into play. It turns out that asking questions in the [Kubernetes Slack +step isn’t always obvious. But this is where my third learning curve, how to engage the community +to get what I need, comes into play. It turns out that asking questions in the [Kubernetes Slack workspace](https://slack.k8s.io/) and bringing my topics to the SIG Security meetings when I need help is an amazing way to get what I need! Again, simple stuff, but until you do it, it’s not always obvious.