5 min read
Your first open source contribution doesn't need code
Docs, reproduction steps, and tested bug reports are contributions. The barrier you imagine is lower than the one that exists.
← All writing
Open source20 posts
Open source
Contribution over ownership — reading issue trackers, writing mergeable PRs, and the evidence that actually proves your work.
Written by Nzubechukwu Cyprian — Pharmacy student at UNN, full-stack developer and AI builder.
5 min read
Reading the issue tracker: the skill nobody teaches
Issue trackers are where projects tell the truth. Learning to read them well reveals what to contribute and what to avoid.
6 min read
The anatomy of a pull request that gets merged
Small scope, clean description, tests, and the maintainer's style. What separates merged PRs from the ones that die open.
5 min read
Cloning a repo is not a portfolio piece
A local copy of a repository proves you downloaded it. What actually counts as evidence of your work — and how to present it.
5 min read
What maintaining your own small library teaches you
Nobody uses it? Perfect. Publishing and maintaining even a tiny package teaches the responsibilities that side projects never do.
4 min read
The etiquette of saying no in open source
Maintainers say no all the time — politely, clearly, with reasons. Contributors need the same skill: how to accept it and how to do it.
5 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.
5 min read
Writing documentation people actually use
Good docs answer the question the reader has *now*. Task-first, honest about limits, and tested like code.
5 min read
Licensing for people who publish things
MIT, GPL, Apache — what the choice actually decides, and why shipping without a licence is a decision you already made badly.
5 min read
The contribution that taught me to write smaller patches
A 400-line PR taught me more about contributing than ten merged ones — by taking three weeks to die in review.
5 min read
Open source is a reputation ledger, and it's read by humans
Your contributions form a public record of how you work. Issue comments age better than commits — and employers read both.
5 min read
Why I contribute upstream instead of maintaining forks
Forks feel powerful and rot quietly. Upstream contributions are slower and compound forever. The math I use.
4 min read
The bug report checklist that changed my hit rate
Reports that get fixed share a skeleton. Mine: minimal repro, versions, expectation vs reality, and what I already tried.
4 min read
Contributing to documentation of a project you don't fully understand
The best person to document a concept is the person who just struggled with it. Your confusion is the map.
5 min read
The economics of free software work
Nobody pays you to fix bugs at midnight, so the currency must be something else. Skills, reputation, and access — honestly accounted.
4 min read
How to ask a maintainer a question they'll want to answer
Good questions show the work already done. The difference between 'how do I do X?' and a question that gets a thoughtful reply.
5 min read
GrantFox, bounties, and getting paid for open source work
Bounty platforms connect contributors with funded issues. What I learned about their reality: scope, proof, and payment rails.
4 min read
Open source as a student: what to contribute when you have no free time
Between lectures and exams there is no spare time — only small time. The contribution formats that fit in an hour.
5 min read
The difference between contributing and taking
Opening issues for free labour, demanding features, vanishing after the fix — the patterns that make maintainers close their doors.
4 min read
Why I stopped caring about GitHub stars
Stars measure attention, not usefulness. The repositories I'm proudest of have triple-digit stars and daily users; the ones with thousands taught me nothing.