Open source feels intimidating from the outside. Here's the exact process we use to onboard new DevSoc members into their first PR — from choosing an issue to getting merged.
Picking the Right First Project
The worst thing you can do is randomly pick a massive project and try to fix something complex. Start with a project you actually use. When you use it daily, you'll notice rough edges naturally — missing docs, confusing error messages, small UX annoyances. Those are your contribution opportunities.
Look for projects with a `good first issue` or `help wanted` label on GitHub. These are explicitly flagged by maintainers as appropriate entry points. Our own projects — HackPortal, OpenLMS — always have a backlog of labelled issues specifically for new contributors.
Finding an Issue You Can Actually Fix
Read the issue thoroughly. Read the comments. Check if there's already a PR open for it — nothing worse than spending a week on something that's already been solved. If there's no activity for a few days, leave a comment saying you'd like to work on it. Maintainers appreciate the heads up and it prevents duplicate work.
Don't be afraid of issues that seem slightly above your current level. The best way to learn is to attempt the fix, get stuck, and ask a specific question in the issue. 'I tried X, got error Y, here's my code' is always welcome. 'How do I fix this?' is not.
Making Your First PR
Fork the repo, create a branch with a descriptive name (`fix/registration-email-typo`, not `patch-1`), and make the smallest change that solves the problem. Resist the urge to clean up unrelated code — reviewers will ask you to split it out and now you have two PRs to manage.
Write a PR description that explains what the problem was, what your solution is, and how you tested it. Include a screenshot if it's a visual change. Maintainers review dozens of PRs — make theirs easy and they'll prioritise yours.
After the Merge
Congratulations — your code ships to every user of that project. Now do it again. The second contribution is always easier than the first because you understand the codebase and the maintainer knows you write clean PRs. Most of our team's best OSS relationships started with a one-line typo fix.
Add it to your CV immediately. 'Contributed to [project name] — [brief description]' is a genuine differentiator when you're applying for internships. Hiring managers who care about open source will ask about it in interviews, and you'll have a real story to tell.
Final year software engineering student with 50+ merged PRs across 12 open source projects. Runs DevSoc's OSS sprint program.
