This project collects relatively easy tasks for new developers to get involved. The tasks for this project are all features that we would accept in Blender releases.
Good First Issue
- Tasks perfect for new comers, or even developers interested on trying their hands in different areas.
- A good first issue doesn't mean necessarily that something is quick to solve, but often there are self-contained problems easy to verify, review and implement.
- Experienced developers don't have to leave these tasks unattended waiting for new contributors to help around. If the task is important then it should be fixed as any other issue.
A good first issue doesn't mean necessarily that something is quick to solve, but often there are self-contained problems easy to verify.
How to Start
- Browse First Good Issue to find one.
- When you want to start working on a task, you can comment on the task to ask for more information if needed.
- When you have a patch ready, you may assign the task to yourself and submit the diff to get it reviewed.
Please: Verify that there isn't already a patch for the task by somebody else. If that's the case, it'll usually be mentioned in a comment or the task has a (open) differential revision assigned (those are usually listed in the task details, like in T45230)
You may also want to look at the Todo wiki page.
Good First Issue can be added by developers and module team members for functionality that they would accept in Blender. This is not a wish list to suggest features.
Projects must be...
- Easy enough for an experienced developer to do in a short time (about 30min - 2hrs).
- Real projects (not simply exercises).
- Acceptable to be added into Blenders code-base without discussion on controversial topics.