简体中文
EnglishWhat Is Up For Grabs?
Updated
Up For Grabs is a directory of open source projects that have set aside tasks specifically for new contributors. If you want to contribute to open source but don't know where to start, it solves the hardest part of that problem: finding a project whose maintainers actually want beginner help and have labeled issues you can pick up. You browse the list, find a project that interests you, and jump to its designated beginner tasks.
How it works
The site is a curated list rather than a code host. Each entry represents a project that has agreed to maintain issues tagged for newcomers. The tags you'll see vary by project — common ones include good first issue, up-for-grabs, help wanted, and up for grabs. The number next to each tag shows how many open tasks currently carry that label.
When you click through, you land on the project's own repository (usually on GitHub), where you can read the issue, comment that you'd like to work on it, and submit a pull request.
What you'll find on the list
The projects span many languages and domains. A sample from the directory:
| Project | Tag shown | Open tasks | What it is |
|---|---|---|---|
| FuseMedML | good first issue | 4 | Python framework for machine learning in the medical field |
| FSharp.Management | up-for-grabs | 6 | Type providers for managing machines, in F#/.NET |
| activist | good first issue | 4 | Open-source nonprofit activism network (Nuxt, Vue) |
| UnityStation | Good First Issue | 56 | A port of SpaceStation 13 into Unity |
| Bitwarden Clients | good first issue | 3 | Client applications for the Bitwarden password manager |
| Clarvia | good first issue | 9 | Multilingual bereavement compliance checklist for Europe |
| notify | up for grabs | 17 | Go library for sending notifications to messaging services |
| CacheManager | up-for-grabs | 7 | Caching abstraction layer in C# |
| FluentTc | up-for-grabs | 12 | Library for consuming the TeamCity REST API |
Tags and counts change as issues are opened and closed, so treat the numbers as a snapshot, not a fixed figure.
Who it's for
- First-time contributors who want a task with a defined scope and a maintainer expecting questions.
- Developers switching stacks who want to make a small change in an unfamiliar language before committing to a bigger project.
- Anyone who wants to help but doesn't have a project in mind — the list does the discovery work for you.
It is less useful if you already know which project you want to contribute to, since you can go straight to that repository's issue labels.
How to use it
- Open the site and scan the list. If JavaScript is disabled, the site falls back to rendering a selection of available projects, so you can still browse a subset.
- Pick a project based on language, domain, or the tag type you're comfortable with.
- Click through to the repository and read the tagged issues. Check the issue description, any linked discussion, and the project's contribution guidelines.
- Comment on the issue to say you'd like to take it, then follow the project's process for submitting changes.
Common snags
- The count is not a promise. A project showing several open tasks may have most of them already claimed in comments. Read the thread before starting.
- "Beginner-friendly" still means reading the docs. Each project sets its own bar for setup, tests, and code style.
- Tags differ by project.
good first issueandup-for-grabsare conventions, not a standard, so the difficulty behind them varies. - Some projects are more active than others. A maintainer who responds quickly makes a first contribution much smoother than one who doesn't, so check recent activity before investing time.
The core value is the same in every case: it shortens the distance between "I want to contribute" and "here is a task someone wants done."