Learn Cloud Native & CNCF - How to Get Involved: Contribution & Joining

#Introduction

Twenty episodes have built your understanding of the cloud native world and CNCF. Episode 21 turns understanding into involvement. Because no matter how good your knowledge is, its value is only felt when it's used — and there's no better way to use it than to get directly involved in the ecosystem.

The good news is that the door to involvement is wide open. You don't need to be an expert or wait for anyone's permission. All that's needed is the willingness to start, persistence, and an understanding of the available paths — exactly what we'll discuss in this episode.

One important note before we begin: involvement is a marathon, not a sprint. Those most respected in the community are the people who show up and help consistently, not those who appear once with a bang and then vanish. Start with a rhythm you can sustain.

By the end of this episode you will know the contribution paths, community roles, how to join as a member, and the first concrete step you can take this week.

#Open Contribution Paths

#contribute.cncf.io: The Starting Gate

The most official entry point is contribute.cncf.io — a page that summarizes all the ways to contribute in the CNCF ecosystem. From there you can find projects needing help, mentoring programs, and guides to get started.

This page is designed to eliminate the "where do I start" confusion. It maps paths by interest and experience level, so you don't have to guess.

#Repositories on GitHub

Most contribution activity happens on GitHub. Several organizations you should know: project repositories in the kubernetes organization, governance repositories in cncf/toc, and project acceptance repositories in cncf/sandbox. Each has its own contribution pattern.

Start by exploring the repository of the project you're most interested in. Look at the contribution files and beginner guides — almost all major projects have them, and they explicitly point to beginner-friendly tasks.

Don't hesitate to open issues tagged "good first issue". This label is deliberately made for new contributors and usually comes with adequate explanation and hints. Completing one such issue is the fastest way to build confidence.

#Roles in the Community

#Maintainer, Reviewer, and Ambassador

In the open source ecosystem, roles form naturally from sustained contribution:

• Contributor — anyone who writes code, documentation, or reports.
• Reviewer — someone trusted to assess changes before they're merged.
• Maintainer — the technical leader holding final decisions on a project.
• Ambassador — the advocate bridging a project with local communities.

The promotion pattern is always the same: start small, stay consistent, and build trust. There are no shortcuts, but there's also no limit on who can rise.

#Non-Technical Roles Are Valuable Too

Don't be fooled into thinking contribution must be code. Documentation, design, answering questions on forums, writing blog posts, and organizing meetups are highly valued contributions. Even for a large project like Kubernetes, non-technical needs always exist.

For those who just finished this conceptual series, the non-technical path is the most sensible choice: you can immediately write about what you've just learned, or help translate documentation into Indonesian. Both contributions are genuinely needed and can be done right away.

It's worth emphasizing that non-technical contributions build the same credibility. Communities respect people who make projects easier to understand — and in an increasingly complex world, the ability to explain clearly is a rarity in itself.

#Mentorship and Support Programs

#LFX Mentorship as an Accelerator

LFX Mentorship, which we discussed in episode 11, is the best accelerator for new contributors. With mentor guidance, you work on real tasks with clear direction — experience far more valuable than learning alone.

Combine mentorship with the local communities from episode 14. The two complement each other: mentorship gives technical depth, local communities give network and support.

To be clear: mentorship isn't a guarantee of instant results, but a structured learning process. You still have to work hard — but with guidance, that hard work is pointed in the right place, so the chance of success is far greater.

#Joining as Part of the Ecosystem

#Becoming a Member and Attending Events

There are several official ways to join the ecosystem: organizations can become members of CNCF, while individuals can join through community participation. Attending KubeCon and following the cncf.io/blog are the simplest ways to stay connected.

Don't forget the community Slack at slack.cncf.io — where thousands of practitioners discuss every day. Joining Slack and reading conversations is a passive yet very effective way to keep learning.

As a rule of thumb, use Slack to learn and ask, not to show off. Communities value well-thought-out questions and people who try to solve their own problems before asking — a habit that also builds a good reputation.

#A Real First Step

#Start This Week

Enough theory — let's practice. Here's a first step you can take this week:

git clone https://github.com/cncf/sandbox.git
cd cncf/sandbox
git checkout -b belajar-kontribusi
gh repo view cncf/toc

The git clone command copies the repository, git checkout -b creates a new working branch, and gh repo view shows the governance repository summary. This exercise trains the same workflow real contributors use.

#Planning the Next Three Steps

After the exercise above, set your next three steps: choose one project, find one beginner-friendly issue, and submit your first contribution — no matter how small. Remember episode 11's lesson: from one small step, community trust is built.

And don't forget to celebrate that small step. Your first accepted contribution — however simple — is an achievement marking your move from observer to participant. Save that moment, and let it fuel the next step.

#Closing

Episode 21 turned understanding into involvement: contribution paths through contribute.cncf.io and GitHub, roles from contributor to maintainer and ambassador, valuable non-technical paths, and the first real step you can take this week.

The key to all of it is starting — now, no matter how small. Twenty episodes gave you understanding, and understanding is only valuable when turned into real involvement.

Key takeaways:

• contribute.cncf.io is the official gate to start contributing.
• Repositories in kubernetes, cncf/toc, and cncf/sandbox are the main entry points.
• Community roles grow from consistent, trusted contribution.
• Non-technical contribution is as valuable as code.
• LFX Mentorship is the best accelerator for beginners.
• Join through membership, KubeCon, the blog, and community Slack.

In episode 22 — the final episode of this series — we'll summarize everything: ecosystems, alternatives, and a final reflection — a comparison of CNCF with other foundations, when to go deeper, and a recap of your 22-episode journey.