Common Prerequisites for Contributors
Last updated on
14 February 2021
Many tasks for contributors to the Drupal project require one or more prerequisites to be in place before starting the task. The table below lists common prerequisites, with links to more information on how to achieve them.
Prerequisite | Description | Needed for | How to achieve |
---|---|---|---|
Log in | Log in to your user account on Drupal.org | Nearly all tasks | Go to drupal.org/user/register and register. If you already have an account, go to drupal.org/user to log in. |
Confirmed account | Your Drupal.org user account must be "confirmed" by a community member | Creating new documentation pages, contacting other users via contact form | See Become a confirmed user |
Chat account | Obtain and log in to an online chat account | Providing chat-based support, online mentoring | See Communication Tools and Platforms for a current list of tools the community uses for online chat (such as Slack and DrupalChat), and instructions for joining |
Zoom client | Software that allows you to connect to Zoom meetings, preferably on a desktop computer (better size for screen sharing during meetings) | Participating in online meetings held in Zoom by some groups within the project | Download a Zoom client. You probably do not need to create a Zoom account to attend a meeting. |
Stack Exchange account | Obtain and log in to an account on Stack Exchange | Answering questions on the Drupal Answers Stack Exchange | Visit the Drupal Answers area on Stack Exchange. Create an account and log in. |
Online testing site | Temporary online site for testing Drupal core and contributed modules and themes (simplytest.me, Tugboat, etc.) | Testing that bug reports are valid, testing that software patches and merge requests fix issues | See the "Using online Drupal testing sites" section of Setting up an environment for testing Drupal patches |
Local development site | Site on your local development computer for testing Drupal core and contributed modules and themes, including Composer | Optional method for testing, which allows you to test patches and merge requests that you are developing, on your local computer, before sharing them with other developers for review | See the "Using a local development environment" section of Setting up an environment for testing Drupal patches |
Git | Git version control system installed on your local computer, and set up to use Drupal (not including Git authentication). | Developing software patches and merge requests for issues | If you already followed the instructions in the "Using a local development environment" section of Setting up an environment for testing Drupal patches, you will have Git installed. To get it installed (if needed) and set up to work with Drupal, see Setting up Git. |
Git clone or update | Use Git to "clone" the project you're working on, or "pull" in the latest changes | Developing software patches and merge requests for issues | See Cloning a Drupal Git repository |
Git authentication | Agree to the Drupal Git user agreement and set up SSH keys | Pushing Git commits to issue forks, merge requests, and project repositories | See Git Authentication for Drupal.org projects |
Help improve this page
Page status: No known problems
You can:
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion