Open Source
Finding Your First Project
Every day, thousands of developers open GitHub thinking «I want to contribute». Most close the tab an hour later - not knowing where to start. The right question isn't «where should I contribute» but «what problem do I already know how to solve».
- Sindre Sorhus started with small utilities - now maintains 1,000+ npm packages
- Evan You's first Vue.js commit was... fixing a typo in the README
- goodfirstissue.dev has helped thousands find their first project
- Microsoft's first-timers-only label deliberately reserves simple tasks for newcomers
Where to Look
The most common beginner mistake: trying to contribute to a project for the sake of contributing, without genuine interest. The best choice is **a project you already use**. Found a bug? Missing something? That's your entry point.
**Start with documentation.** Most beginners want to write code immediately. But fixing a typo in README or adding an example to docs is a real contribution. Maintainers notice it and remember your name - often more than a complex code PR.
You're new to OSS. Which approach to choosing your first project is most effective?
Evaluating Project Health
Not every project deserves your time. Before investing hours, spend 5 minutes analyzing. There's nothing worse than writing a great PR for an abandoned project.
**Look for projects in the 100-5,000 star range.** Too small - might be abandoned. Too big (React, Vue) - high barrier to entry. The sweet spot: an active project where maintainers know their contributors by name.
A project: 3,000 stars, last commit 8 months ago, 150 open PRs without responses, but has a CONTRIBUTING.md. Is it worth contributing?
Key Ideas
- Best project = one you already use: you know the context and have genuine motivation
- goodfirstissue.dev, up-for-grabs.net, codetriage.com - aggregators for discovery
- 100-5,000 star range: active enough but not overwhelmed
- Healthy project signals: commits < 30 days, PRs get responses, welcoming maintainers
- Start with documentation - it's a real contribution that gets remembered
Related Topics
Found a project - next step is mastering the Git workflow for sending your first PR.
- Next Lesson — Logical continuation
Вопросы для размышления
- Go to goodfirstissue.dev right now. Choose a language you know. Find 3 projects. What does a health check reveal about each?
- Why is documentation an underrated entry point? What do maintainers specifically value in docs PRs?