Areas and teams
Godot is organized into areas, most of which has a designated team working on them. This page lists these areas and explains their goals and how they're organized.
For each team or area there is a list of links and resources associated with them:
Communication: links to the RocketChat channels for the team, joining this channel is the best way get involved with a team.
GitHub reviews: opens a GitHub search for PRs that have a review request for the team. Note that this doesn’t show PRs that have already been reviewed by that team, any review comments at all, from any member of a specific team, will remove the request, so this is not always helpful.
GitHub labels: lists any labels relevant to the team, and links to issues and PRs tagged with those tags. For more information about the different GitHub labels, please see the Bug triage guidelines. Note that some GitHub labels aren’t neatly covered by trackers.
Triage project: links to the team triage project for the team. You are welcome to help the team out by implementing or reviewing something from this list.
Maintainers: lists the members of each team. The area maintainers take ownership of the area, and will steer its development by creating and reviewing pull requests and improvement proposals. Maintainers are listed alphabetically. Maintainers written as ⭐ Member (with a star and in bold) are team leads.
You can find information about the teams' current priorities on the Godot website.
How to join a team / become a maintainer
Prospective maintainers are invited by other maintainers. As such, there is no way to apply to become one.
At the same time, the primary goal of any contributor should be to improve Godot. Becoming a maintainer can be an honor, but is primarily a responsibility.
Regardless of whether you work with the goal of becoming a maintainer, or simply want to make effective contributions for the community, we have some advice for you:
Take on maintainer tasks. Many people assume that tasks like reviewing PRs, taking on team tasks, and critically evaluating proposals are reserved to maintainers. This is not true! These kinds of tasks are a major bottleneck for Godot's development, so we appreciate everyone who contributes in this way.
Be aligned with the project direction. Try to work in the best interest of Godot. Many people like implementing exciting new features, but often this is not the best way to contribute. What are other ways to help? Where do you see problems or jobs that nobody else is taking on? What plans or roadblocks do the teams currently have, and can you help? By being well informed and aligning with the teams, you can make effective contributions in the interest of Godot.
Earn trust from other maintainers. Casual contributors come and go, but we take note of those who stay around and communicate well, take on tasks and responsibility in an area, and are proactive when solving problems and fixing regressions.
2D
Communication
GitHub reviews
Maintainers
Gilles Roudière (@groud), Tomasz Chabora (@KoBeWi)
3D
Communication
GitHub reviews
Maintainers
Hugo Locurcio (@Calinou)
Animation
Nodes and features for 2D and 3D animation and IK workflows.
Communication
GitHub reviews
Triage project
Maintainers
Juan Linietsky (@reduz), K. S. Ernest Lee (@fire), @Lyuma, @SaracenOne, Silc 'Tokage' Renew (@TokageItLab)
Asset pipeline
Asset import pipeline for 2D (textures) and 3D (scenes, models, animations, etc.).
Communication
GitHub reviews
Triage project
Maintainers
Aaron Franke (@aaronfranke), @BlueCube3310, Hugo Locurcio (@Calinou), K. S. Ernest Lee (@fire), @Lyuma, Rémi Verschelde (@akien-mga)
Audio
All audio-related features, from low-level AudioServer and drivers to high-level nodes and effects.
Communication
GitHub reviews
Triage project
Maintainers
Adam Scott (@adamscott), Lukas Tenbrink (@Ivorius/@Ivorforce), Juan Linietsky (@reduz)
Core
Low-level Core API: Object, Variant, templates, base nodes like Node, Viewport, etc. (everything under core and scene/main).
Communication
GitHub reviews
Triage project
Maintainers
HP van Braam (@hpvb), Juan Linietsky (@reduz), @lawnjelly, Lukas Tenbrink (@Ivorius/@Ivorforce), Rémi Verschelde (@akien-mga)
Demos
Communication
GitHub reviews
Maintainers
Aaron Franke (@aaronfranke), Gilles Roudière (@groud), Hugo Locurcio (@Calinou), K. S. Ernest Lee (@fire)
Documentation
Documentation for the engine and its systems. You can find documentation for this team in the documentation section.
Note that, while there is a dedicated documentation team, all other teams are expected to contribute to the documentation for their area.
Communication
GitHub reviews
Maintainers
A Thousand Ships (@AThousandShips), Hana - Piralein (@Piralein), Hugo Locurcio (@Calinou), Max Hilbrunner (@mhilbrunner), Matthew (@skyace65), Micky (@Mickeon)
Editor
All things related to the editor.
Communication
GitHub reviews
Triage project
Maintainers
Gilles Roudière (@groud), Hugo Locurcio (@Calinou), Kit Bishop (@kitbdev), Michael Alexsander (@YeldhamDev), Pāvels Nadtočajevs (@bruvzg), Robert Yevdokimov (@ryevdokimov), Tomasz Chabora (@KoBeWi)
Debugger
Communication
GitHub reviews
Triage project
Maintainers
Fabio Alessandrelli (@Faless), George Marques (@vnen)
Script Editor
Communication
GitHub reviews
Triage project
Maintainers
Kit Bishop (@kitbdev), Michael Alexsander (@YeldhamDev), Paul Batty (@Paulb23)
GUI
Everything that inherits Control (everything under scene/gui) and can be used to build Graphical User Interfaces (both game UI and editor tools).
Communication
GitHub reviews
Triage project
Maintainers
Gilles Roudière (@groud), Hendrik Brucker (@Geometror), Kit Bishop (@kitbdev), Michael Alexsander (@YeldhamDev), Paul Batty (@Paulb23), Pāvels Nadtočajevs (@bruvzg), Rémi Verschelde (@akien-mga), Tomasz Chabora (@KoBeWi)
Input
Communication
GitHub reviews
Maintainers
Alexander Hartmann (@Alex2782), Rémi Verschelde (@akien-mga), Gilles Roudière (@groud), @Nintorch
Networking
Networked multiplayer, RPCs and replication, HTTP/TCP/UDP/DNS, WebSockets, ENet, encryption.
Communication
GitHub reviews
Triage project
Maintainers
Fabio Alessandrelli (@Faless), Max Hilbrunner (@mhilbrunner)
Physics
Physics servers and their implementation in 2D and 3D.
Communication
GitHub reviews
Triage project
Maintainers
Jorrit Rouwe (@jrouwe), Juan Linietsky (@reduz), @lawnjelly, Mikael Hermansson (@mihe), Ricardo Buring (@rburing)
Platforms
Platform specific layers that reside in platform, with shared components (Unix, Win32, Apple, etc.) in drivers.
Communication
Triage project
Android
Communication
GitHub reviews
Triage project
Maintainers
Alexander Hartmann (@Alex2782), Anish (@syntaxerror247), Fredia Huya-Kouadio (@m4gr3d)
Apple
Communication
GitHub reviews
GitHub labels
Triage project
Maintainers
Bastiaan Olij (@BastiaanOlij), Pāvels Nadtočajevs (@bruvzg)
Buildsystem
Tools and scripts that we use to compile and maintain Godot, both for development purpose (SCons, CI) and releases (official build containers).
Communication
GitHub reviews
Triage project
Maintainers
Fabio Alessandrelli (@Faless), HP van Braam (@hpvb), Hugo Locurcio (@Calinou), Pāvels Nadtočajevs (@bruvzg), Rémi Verschelde (@akien-mga), Thaddeus Crews (@Repiteo)
Web
Communication
GitHub reviews
Triage project
Maintainers
Adam Scott (@adamscott), Fabio Alessandrelli (@Faless)
Windows
Communication
GitHub reviews
Triage project
Maintainers
Max Hilbrunner (@mhilbrunner), Pāvels Nadtočajevs (@bruvzg)
Linux / BSD
Communication
GitHub reviews
Triage project
Maintainers
Dery Almas (@deralmas), Fabio Alessandrelli (@Faless), HP van Braam (@hpvb), Pāvels Nadtočajevs (@bruvzg), Rémi Verschelde (@akien-mga)
Quality Assurance
All things QA: unit/integration tests, static analysis, benchmarks, code style/quality, builds testing.
Communication
Tests
Tests for the engine and its systems. Note that, while there is a dedicated tests team, every team is expected to contribute to the tests for their area.
Communication
GitHub reviews
Maintainers
Hugo Locurcio (@Calinou), Hendrik Brucker (@Geometror), Thaddeus Crews (@Repiteo)
Bugsquad / Issue triage
You can find documentation for this team in the triage section.
Communication
GitHub reviews
Maintainers
A Thousand Ships (@AThousandShips), K. S. Ernest Lee (@fire), @lawnjelly, Rémi Verschelde (@akien-mga), Ricardo Subtil (@rsubtil), Rudolph Bester (@Rudolph-B), Sébastien Dunne Fulmer (@CreatedBySeb)
Rendering
Rendering server and RenderingDevice implementations (Vulkan, OpenGL), as well as the actual rendering techniques implemented using those graphics APIs.
Communication
GitHub reviews
Triage project
Maintainers
Bastiaan Olij (@BastiaanOlij), @BlueCube3310, Clay John (@clayjohn), Darío Banini (@DarioSamo), Hugo Locurcio (@Calinou), Juan Linietsky (@reduz), @lawnjelly, Skyth (Asilkan) (@blueskythlikesclouds), Stuart Carnie (@stuartcarnie)
Shaders
Communication
GitHub reviews
Triage project
Maintainers
Clay John (@clayjohn), Hendrik Brucker (@Geometror), Ilaria Cislaghi (@QbieShay), Patrick Exner (@paddy-exe), Skyth (Asilkan) (@blueskythlikesclouds), Yuri Rubinsky (@Chaosus)
VFX / Tech Art / Particles
Communication
GitHub reviews
Triage project
Scripting
Umbrella team for all the scripting languages usable with Godot. Encompasses some shared core components (Object, ClassDB, MethodBind, ScriptLanguage, etc.) and language specific implementations in dedicated subteams.
GDExtension
GDExtension and godot-cpp.
Communication
GitHub reviews
Triage project
Maintainers
Bastiaan Olij (@BastiaanOlij), David Snopek (@dsnopek), Fabio Alessandrelli (@Faless), George Marques (@vnen), Jan Haller (@Bromeon), Lukas Tenbrink (@Ivorius/@Ivorforce), Patrick Exner (@paddy-exe), Pāvels Nadtočajevs (@bruvzg)
GDScript
GDScript language implementation.
Communication
GitHub reviews
Triage project
Maintainers
Adam Scott (@adamscott), Danil Alexeev (@dalexeev), George Marques (@vnen), @HolonProduction
C# / .NET / Mono
Communication
GitHub reviews
Triage project
Maintainers
Paul Joannon (@paulloz), Raul Santos (@raulsntos)
Server Infrastructure
Managing the backend for the website and servers, e.g. godotengine.org, asset library, and upcoming asset store.
Communication
GitHub reviews
Maintainers
HP van Braam (@hpvb), Winston (@winston-yallow)
Technical Leadership Committee (TLC)
The Technical Leadership Committee (TLC) drafts and drives the technical roadmap / development direction for the engine, supports and assists the project management and release teams, and provides technical guidance to the Godot Foundation Board. Learn more on the Governance page on the Godot website.
GitHub reviews
Maintainers
Bastiaan Olij (@BastiaanOlij), Clay John (@clayjohn), David Snopek (@dsnopek), Fredia Huya-Kouadio (@m4gr3d), George Marques (@vnen), HP van Braam (@hpvb), Juan Linietsky (@reduz), @lawnjelly, Lukas Tenbrink (@Ivorius/@Ivorforce), Pāvels Nadtočajevs (@bruvzg), Rémi Verschelde (@akien-mga), Tomasz Chabora (@KoBeWi)
Translation / i18n
Internationalization and localization team - building the infrastructure to make it possible to translate Godot and its documentation.
If you work on Godot translations and contributors for your language have a dedicated communication channel for coordination, let us know so we can link it here.
Communication
GitHub reviews
Maintainers
Rémi Verschelde (@akien-mga)
Usability
The usability team represents a user-oriented view of the engine, and plans and reviews functionality, workflows, and accessibility.
Feel free to approach the usability team for guidance and support in planning an engine feature, especially if it involves GUI or user experience (UX).
Communication
GitHub reviews
Triage project
Maintainers
Adriaan de Jongh (@AdriaandeJongh), Gilles Roudière (@groud), Hendrik Brucker (@Geometror), Hugo Locurcio (@Calinou), K. S. Ernest Lee (@fire), Michael Alexsander (@YeldhamDev), Micky (@Mickeon), @passivestar, Paul Batty (@Paulb23), Timothé Bonhoure (@ajreckof)
Website
Creating and curating the website godotengine.org and asset library (and upcoming asset store).
Communication
GitHub reviews
Maintainers
Adam Scott (@adamscott), Emilio Coppola (@coppolaemilio), Hugo Locurcio (@Calinou), Iñigo Allende (@InigoAllende/@i.allende), Winston (@winston-yallow)
XR
Augmented (AR) and virtual reality (VR).
Communication
GitHub reviews
Triage project
Maintainers
Bastiaan Olij (@BastiaanOlij), David Snopek (@dsnopek), Fredia Huya-Kouadio (@m4gr3d), Logan Lang (@devloglogan)