Last updated March 10, 2011.
This section explains how to help by finding issues on which to work, creating patches, and then submitting those patches.
Finding issues on which to work
Most issues are solved by developers who are either affected by the issue or are the maintainer of the module with the issue. Some developers also find issues that interest them and submit patches to fix those issues. You can find issues in need of patches at the following links:
Patches are structured files describing code changes needed to solve an existing issue. A more detailed definition is available at What is a patch?. By applying the patch, the code in the patch modifies the code in the module or in Drupal core.
Patches are used to maintain control-ability over the entire Drupal project. While Drupal is distributed via the Git version control system, patches are additional pieces of code that focus on a single change request and therefore are easily tested, reviewed, and documented.
This also means that you do not need a full Git account to submit patches. Rather, as long as you have a Drupal.org account, you can upload a patch to an issue in the issues queue. The tips for contributing code apply to Drupal core as well as to contributed modules.
- Patch contributor guide (for step-by-step instructions that include Git commands)
- Creating patches (for general information about methods of creating patches)
- Applying patches (for instructions about applying patches if you do not have Git)
// TODO: mention dreditor