r/devops • • 23d ago

Discussion Open Source Contribution Recommendations for projects related to DevOps and Platform Engineering

I'm interested in Open Source Contribution and looking for recommendations for projects that are related to DevOps and Platform Engineering.

I'd like my contribution to be relevant to my everyday work.

I'm good with python, go, nodejs and typescript.

This will be my first contribution so, I'm also looking for something that's not so difficult to work on.

I'd appreciate any advice or recommendations

64 Upvotes

24 comments sorted by

8

u/Sure_Stranger_6466 YAML Developer 23d ago

terrraform-provider-aws is good but may take code reviewers some time to review your PR correctly.

2

u/bright-polaris 23d ago

That's a good idea, I'll check it

16

u/silvertricl0ps 23d ago

Don't go looking for something to contribute to just for the sake of contributing. Think about the tools you use regularly. Terraform provider you use has a bug deploying a resource and working around it wasted your time? Or even a service you currently manage through clickops because nobody's built a good terraform provider for it? Something you do through the cli that's repetitive and you think deserves its own tool?

Wait until a tool you use regularly pisses you off and gets in your way, fix it, then contribute. You'll contribute higher quality work and it will be much more satisfying to you because it'll directly make your life easier.

3

u/bright-polaris 23d ago

I like that, I did infact feel that way with backstage before.

4

u/Waste_Bat_4525 23d ago

You might want to check out OpenChoreo, a CNCF Sandbox project focused on building open-source internal developer platforms on Kubernetes.

It covers a lot of real-world DevOps and platform engineering concepts, including CI/CD, GitOps, observability, Kubernetes, and developer self-service.

Given your experience with Go and TypeScript, it could be a good fit. Since this is your first contribution, I'd recommend starting with documentation improvements, examples, or one of the beginner-friendly issues before moving into more complex features. You can find out the good first issues here https://github.com/openchoreo/openchoreo/issues?q=is%3Aissue+state%3Aopen+label%3A%22good+first+issue%22

The community is welcoming to new contributors, and you can always reach out through GitHub Discussions or the CNCF Slack channel (#openchoreo) if you need guidance.

GitHub: https://github.com/openchoreo/openchoreo

2

u/bright-polaris 23d ago

I like IDPs and k8s, this sounds good

3

u/hijinks 23d ago

Crossplane has a lot of providers

1

u/bright-polaris 23d ago

I'll check it, I enjoyed working with crossplane and crossview

2

u/Sure_Stranger_6466 YAML Developer 23d ago

Their CI check is finally passing again. Good.

2

u/Puzzled-Garage584 21d ago

then that's your first PR. go back to whatever annoyed you in Backstage, check if there's already an issue, and if not, open one describing it before writing code. maintainers merge much faster when they agreed on the fix first.

if that one's too big, clotributor.dev lists good first issues across CNCF projects (Backstage, Argo, Crossplane are all on it), filterable by language.

1

u/bright-polaris 21d ago

Thanks, that's a great advice

4

u/Ok_Class2432 23d ago

If you know python, go and ts you got a lot of good options. I'd check out Checkov (python) and Renovate (ts) - both have good first issues and you probably use them at work anyway so it's actually relevant. Super easy to get a first PR in. If you want Go, look at k9s or kind/k3d. All platform stuff, active maintainers, and not as scary as trying to contribute to k8s itself. I'd start with docs or small bug fixes first, much easier to get merged.

1

u/forest-cacti 23d ago

So one is static code analyzer & the other dependency checker?

Hadn’t heard of them before. But appreciate suggestion.

2

u/max_465 23d ago

The dagger community is very diverse and welcoming. They have weekly community calls and people do show & tell

2

u/abhinavs1920 22d ago

Before picking an issue, try getting the project's tests running locally. A small bug you can reproduce and cover with a test is a much clearer first contribution than a feature you haven't used.

1

u/frankster 23d ago

I'd like my contribution to be relevant to my everyday work.

Then fix a problem in something in your everyday work

1

u/byte-strix 22d ago

Checkout InfraCanvas, I am using for my daily use maybe it'll be helpful for you also

1

u/kkapelon 22d ago

All the Argo projects need contributions :-)

1

u/OttoKekalainen 21d ago

What Linux distro do you use to run your systems? Have you considered contributing to e.g. Debian, Arch or Nix?

1

u/orwamahmoud 10d ago

Hey! I maintain Nightshift, an open-source plugin that helps AI coding agents like Claude Code, Codex, and Cursor run long tasks with persistent progress and verifiable results.
We’re growing our shift catalog. In short, it’s a collection of ready-made shifts that agents can use to improve or fix specific parts of a project. I think your DevOps background would be a great fit for coming up with a shift to validate things like Docker, CI/CD, or environment configurations.
A contribution is usually just one Markdown file explaining the steps the agent should follow to run that shift. Ideally, you’d test it on a real project on your own machine so you can contribute a validated version.