When you become a committer

Welcome to being a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.! Here are some things you should know:

  • Make sure you have a strong password: it should be long, random, and stored in the password manager of your choice.
    • Bad: X*7z7XL{kZvky7E(
    • Good: aLy%t;67zvy3VdFwVPKA@VGV?i7oq.63Lj.2aKZ@Tw3].Eu4kVUJJVGyXH7oRL*a
  • Make sure you have two-factor auth enabled for GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., and the email account associated with your w.org account. It’s also a very good idea to enable it for any service you use, since hackers will often leverage access to a low priority account to gain access to a high priority account.
  • Join the #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-committers channel on Slack.  This channel is for onboarding and questions from committers about the act of committing, tips and tricks for SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase., etc. You’re welcome and encouraged to ask here whenever you have a question about committing (e.g., SVN syntax, backports, etc). Anything that is relevant to non-committers (e.g., whether or not a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. is ready for commit, project philosophy, proposals, etc) should still take place in #core to avoid excluding other contributors.
  • Please add svnusername@git.wordpress.org (e.g.pento@git.wordpress.org) to your GitHub account: https://github.com/settings/emails . This will allow the new GitHub mirror (https://github.com/WordPress/wordpress-develop) to correctly attribute your commits. GitHub will try to send a verification email, but it won’t be delivered. There’s no need to verify this email address for commit attribution purposes.
  • Read through this guide on commit messages for a primer on what’s considered best practices.
  • Please ask a relevant committer to peer-review your first few prospective patches and commit messages before you commit them. This serves as a safety check to make sure you know what to look out for before you actually commit. It also gives you a chance to ask any questions you have about process, standards, norms, etc.
  • It can also be a good idea to ask for peer-review from another committer whenever you have any doubts about a patch, especially if you’re committing outside an area that you normally work on.

Tasks to add a committer

  • Ensure the committer has completed the above steps.
  • On a WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Sandbox, add them to the following lists:
    • /home/svn/etc/develop.svn.wordpress.org in DeployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. SVN
    • $committers in .config/capes.php
    • wpTracContributorLabels in the Trac SVN file templates/core/site-specific.html
  • Additionally, add them to the following groups:
  • If the committer will be working on security issues, refer to the Security Team handbook for onboarding tasks.

Last updated: