Maintainers

Godot is governed by the Godot Foundation and developed by an open community. The day-to-day code-review and merge work is done by the Production Team plus area-specialist teams. This page summarizes how ownership is organized in this repo.

CODEOWNERS

.github/CODEOWNERS is the source of truth for review assignment. It maps every directory in the repo to one or more @godotengine/<team> teams; GitHub auto-requests review from the matching teams when a PR is opened.

Top-level teams referenced in CODEOWNERS:

Team	Owns
@godotengine/buildsystem	SConstruct, *.py, top-level files, thirdparty/, register_*_types.cpp glue, misc/
@godotengine/core	core/, main/, scene/main/, miscellaneous core utility modules (regex, zip, noise)
@godotengine/rendering	servers/rendering/, drivers/{vulkan,d3d12,metal,gles3,egl,dummy,spirv-reflect}, render-side modules
@godotengine/shaders	modules/visual_shader/, shader-language-related editor files
@godotengine/2d-nodes	scene/2d/, scene/resources/2d/, 2D-related editors
@godotengine/3d-nodes	scene/3d/, scene/resources/3d/, CSG, GridMap, 3D editors
@godotengine/gui-nodes	scene/gui/, scene/theme/, text servers, themes, fonts
@godotengine/animation	scene/animation/, animation track editor, skeletons
@godotengine/physics	servers/physics_*, modules/godot_physics_*, physics nodes/resources
@godotengine/jolt-physics	modules/jolt_physics/, thirdparty/jolt_physics/
@godotengine/navigation	servers/navigation_*, modules/navigation_*, nav nodes
@godotengine/audio	servers/audio/, audio drivers, audio modules (mp3, ogg, theora, vorbis, interactive_music)
@godotengine/xr	servers/xr/, modules/openxr/, modules/webxr/, modules/camera/, modules/mobile_vr/, platform/visionos/
@godotengine/network	core/crypto/, network modules (enet, mbedtls, multiplayer, upnp, webrtc, websocket)
@godotengine/input	core/input/, drivers/sdl/
@godotengine/asset-pipeline	All image / texture / asset-import modules (gltf, fbx, png, etcpak, …)
@godotengine/gdscript	modules/gdscript/, JSON-RPC for the language server
@godotengine/dotnet	modules/mono/, extension_api_validation/
@godotengine/gdextension	core/extension/, extension_api_validation/
@godotengine/script-editor	The editor's script editor + GDScript/Mono editor plugins
@godotengine/editor	editor/ (general)
@godotengine/debugger	core/debugger/, scene/debugger/, servers/debugger/, modules/objectdb_profiler/
@godotengine/documentation	doc/, all doc_classes/ per module
@godotengine/i18n	editor/translations/, doc/translations/
@godotengine/tests	tests/, all module tests/
@godotengine/android	platform/android/
@godotengine/ios	platform/ios/
@godotengine/macos	platform/macos/, drivers/apple*/
@godotengine/linux-bsd	platform/linuxbsd/, drivers/unix/
@godotengine/windows	platform/windows/, drivers/windows/
@godotengine/web	platform/web/

The validate-codeowners hook checks that every path is owned. New directories must be added to .github/CODEOWNERS before a PR will pass.

Top contributors all-time

Per git shortlog -s -n --no-merges --all against the master branch (numbers in parentheses are commit counts at the time of this snapshot, April 30, 2026):

1. Rémi Verschelde — 5,401 — release manager + build system + maintainer-at-large.
2. Hugo Locurcio — 3,024 — documentation, defaults, polish across the engine.
3. Juan Linietsky (reduz) — 2,809 — co-founder, lead designer; driver behind major architecture changes.
4. Pāvels Nadtočajevs — 2,428 — Linux/BSD platform, X11/Wayland.
5. Tomasz Chabora (KoBeWi) — 2,175 — editor + GUI + 2D nodes.
6. Haoyu Qiu — 1,448 — broad engine work.
7. Fabio Alessandrelli — 1,277 — networking, multiplayer, web.
8. Chaosus — 1,116 — visual shader, shaders.
9. Pedro J. Estébanez — 1,069 — performance, threading, physics.
10. Michael Alexsander — 1,001 — editor + GUI.
11. Aaron Franke — 873 — math, physics, conventions.
12. Clay John — 855 — rendering server, RD path.
13. Ignacio Etcheverry — 782 — Mono / .NET integration.
14. George Marques — 641 — GDScript.
15. Fredia Huya-Kouadio — 613 — Android platform.
16. Bastiaan Olij — 538 — XR / OpenXR.
17. lawnjelly — 535 — performance, rendering.

The list keeps going — over 3,700 unique authors have committed over the project's lifetime. The 90-day window (Jan-Apr 2026) shows 262 distinct authors, which gives a good sense of the active community size.

Production Team and Working Groups

The contributors documentation lists active maintainers, by team. The production team coordinates releases and maintainer onboarding; specialist working groups (Rendering, Mono, GUI, etc.) own their respective subsystems with the autonomy to design and ship features.

The Project Management Committee at the foundation handles legal, financial, and trademark matters, but does not direct technical decisions — those rest with the production team and contributors.

Becoming a maintainer

The path is informal but consistent:

1. Make high-quality contributions in a focused area for a sustained period.
2. Help review other PRs in that area.
3. An existing maintainer of that area will eventually invite you to the corresponding @godotengine/<team> GitHub team. From that point you have triage + review-merge powers in your area.

There is no application process; merit is observed in the open via PR history and chat presence.

Reaching maintainers

• Per-area channels in the Godot Contributors Chat.
• @ tags on a GitHub PR after a reasonable wait if no review has happened.
• Issue triage requests in the #triage channel.

Avoid DMing maintainers about issues unless they explicitly invite it; the open channels are intentional.