Adding a new Drupal core committer

Last updated on
18 March 2026

Potential core committers (like any other type of core maintainer) can nominate themselves publicly, at any time, via the standard procedure (see the Drupal core governance documentation).

In practice, though, it is common for the existing team of committers to recruit people privately:

  1. If you think a new core committer is needed, talk to a member of the Core Leadership team. It's best to suggest names of specific people, if you can.
  2. The Core Leadership team may choose to advertise the position more widely, such as via a post on the Drupal core group (example).
  3. Once someone is selected and accepts, this is also announced on the Drupal core group (example).

Once a new core committer has been found and is ready to start, the following changes should be made:

  1. The new committer needs to be granted appropriate access at https://www.drupal.org/node/3060/maintainers based on their role. This is usually done by a member of the Core Leadership team.
  2. The new committer's name should be added to MAINTAINERS.txt in the core codebase. Traditionally the new committer does this themselves - file an issue with a patch, ask someone else to mark it RTBC, and then commit it as their very first (or one of their first) core commits :)
  3. Refer the new committer to the orientation documentation for their next steps.
  4. Add the core committer to the Core Leadership Team google group.

Help improve this page

Page status: No known problems

You can: