Core committer orientation

Welcome to the Core Committer Team!

This document provides instructions for setting up a local repository for committing to core and is a reference to important documentation for fulfilling your role.

Responsibilities

The governance for Drupal core explains how core committers work together and includes descriptions for all the roles in the team. You can find the expectations for your role there.

There is a difference in what a full core committers can do and a provisional committers. A provisional committer goes through a trial period, where the individual and the team decide together if the role is a good fit for them. Provisional committers have fewer privileges that a full core committer. Find out more about the differences between full and provisional core committers.

Setup for committing

1. Create a separate local clone of the core repository for core commits. It is the safest and best practice to have a separate copy of the repository that is only used for committing to core. This will prevent changes from other issue contributions or testing from being merged accidentally.
   • Local clones for any core contributions other than committing to core should instead be made using the read-only git remote URL: https://git.drupalcode.org/project/drupal.git. (On the Version control instructions tab for the core project, uncheck Maintainer? and click Show.)
2. Follow the instructions at Configuring Git for Drupal to correctly setup for committing to core.
   • This document recommends global git configuration. You may wish to use local configuration in your maintainer repository so that you can maintain different defaults for each project.
3. Install Drupal git hooks, https://github.com/alexpott/d8githooks.
4. Release Managers are also to install https://github.com/xjm/drupal_core_release.
5. Set up commit signing.
6. Create a bookmark for the canonical RTBC queue; https://www.drupal.org/project/issues/search/drupal?project_issue_followers=&status%5B%5D=14&issue_tags_op=%3D

Committing

Before committing an issue, follow the instructions for reviewing and committing Drupal core patches.

References

All the documentation for developing Drupal core can be found in the Core development policies and practices guide.  This includes the Core committer handbook, a useful reference for tasks.

Projects related to the work of a core committer include:

• Drupal Community Governance project
• Drupal core ideas project

Documents related to issue management and committing include:

• Issue procedures and etiquette
  • Issue scope guidelines for Drupal core issues
• Core change policies
  • Allowed changes during core release cycles
  • Core gates
  • Drupal core backend backwards compatibility and internal API policy (Drupal 8 and above)
  • Drupal core frontend backwards compatibility (BC) policy
  • Drupal deprecation policy
  • Experimental modules and themes in Drupal core
  • Frontend Developer tools for Drupal core
• Fields and other parts of an issue
  • Issue Priority field
• Core committer handbook
  • How is credit granted for Drupal core issues
  • Reviewing and committing Drupal core patches.
• Coding standards