Nzubechukwu.
← All posts
Open source5 min read

How I find projects worth contributing to

The best project to contribute to is one you use, that's healthy, and that needs what you can give. A practical filter.

By Nzubechukwu Cyprian · Pharmacy student at UNN, full-stack developer

Cover image for “How I find projects worth contributing to” — Open source

Choosing an open source project is like choosing a gym: the nearest one you'll actually go to beats the famous one across town. My filter has four gates, and any project that passes them is worth my evenings.

The four gates

I use it. Contributions from real users carry context that drive-by contributions lack. I can tell when the bug matters, and my motivation survives the boring parts.

It's healthy. Signals: commits in the last month, PRs merged recently (not just opened), maintainers responding in the tracker. An alive project multiplies your work; a dead one entombs it.

It needs what I have. Honest matching: a docs-heavy project doesn't need my frontend patch, and a design-starved project doesn't need my docs pass. The "good first issue" queue tells me where the door actually is.

The culture fits. Ten minutes reading maintainer responses. Gruff-but-fast, slow-but-thorough, welcoming, strict — all fine if stated. What doesn't fit: contempt. Life is too short to contribute where courtesy is absent.

What I gave up

Impressive names. Contributing to a famous project for the logo looks good and feels empty if the work is trivial. A smaller project where my patch genuinely matters beats a giant where I renamed a variable.

Found this useful? Send it to someone.

Nzubechukwu Cyprian studies Pharmacy at the University of Nigeria, Nsukka and builds software, products, and AI experiments in between.

One email when a post lands

No schedule, no spam. Just the posts worth reading — new writing on software, AI, products, and the Pharmacy × Tech life.

Prefer a feed reader? Grab the RSS feed.