Participate in Godot's development

The engine development is coordinated by teams and discussed on the Godot Contributors Chat. If you are serious about getting involved, you should join us there!

Engine code (mainly C++): If you are a programmer, you can contribute to Godot by working on its source code, or the source code of any other repository.
Documentation: Contribute documentation to improve the Godot Engine with your technical writing skills.
Translations (spoken languages other than English): Are you interested in making the Godot Engine more accessible to non-English speakers? Contribute to our community translations on Weblate.
Test and discuss pull requests: Every change to Godot starts with a pull request, and all pull requests need feedback. Even without knowing how to program, you can help by testing whether pull requests work as intended, by discussing whether new features are useful and appropriate, and giving feedback on how to improve fixes or new features.
Bugsquad & triage: With so many bug reports and pull requests being opened each day, the ◆ Triage team — also called bugsquad — is invaluable to keep things organized. If you'd like to get involved, please visit Introduction to issue triage!

Contribute engine code

You can theoretically propose and implement any kind of change to Godot. The community will discuss whether the change is needed and appropriate, and will make suggestions for how to improve it. Area maintainers consider community demand, priority, and complexity, and make a decision about whether to accept it.

Even if you already have some specific change in mind, in many cases you should report a bug or propose the change first. These are useful for maintainers to understand the change, and proposals especially are used to gauge community interest and challenge your solution idea.

Look for simple, relevant, and uncontroversial changes to contribute, especially at first. Here are some ideas:

Fix bugs. A great place to start is by fixing bugs. Feel free to browse issues on the Godot repository, choose one, and just get started!
- Issues labeled as good first issue are issues that maintainers think should be good for newcomers. However, these issues are claimed pretty quickly, so it's likely you won't find anything actionable here.
Add unit tests. Many engine areas are not covered by unit tests. Feel free to look yourself or browse the unit test tracker. Find a guide to add unit tests in the engine docs.
Contribute to an area. If you are knowledgeable or interested in a specific area, you can browse its bug reports using the associated labels or by looking through trackers. Some teams also maintain a triage project. This can be an especially effective way to make meaningful contributions. Find triage projects linked in Areas and teams.
Contribute improvements or new features. You can find popular open proposals or propose your own. The bar for adding new features is high, so is is usually better to engage with proposal discussions before starting work to implement something. Please note that we do not accept feature PRs from new contributors.
Review pull requests. Godot's development is bottlenecked by reviews. You can find pull requests to review by browsing each team's review requests and triage projects, by browsing pull requests and filtering by label, or by exploring the Godot team reports and PRs by file websites.

Contribute documentation

Start contributing in the areas that you are most familiar with. This ensures that the added description will be based on experience and the necessary know-how, not just the name of a method or a property. We advise not to add low effort descriptions, no matter how appealing it may look. Such descriptions obscure the need for documentation and are hard to identify automatically.