// css // javascript
navigation

Drupal Contribution Guideline (DCG)

This contribution guideline is designed to help all developers, from interns to tech leads, contribute to Drupal, the open-source content management system. Drupal welcomes contributions of all kinds, and we want to ensure that everyone can participate in the development process.

Onboarding steps

  1. Go through the Official Contribution Guidelines links given below.
  2. Join the drupal slack. https://drupal.slack.com/ and join #contribute, #support channel. There are few more public channels for specific topics.
    1. The advantage of joining the drupal slack channel is that you can get help with any issue related to Drupal and you can find maintainers of most of the modules on the drupal slack channel.
  3. Go through the DO’s and DON’Ts section given below.
  4. Do not pick any novice or beginners issues if you are already familiar with drupal contribution. Do not waste your time fixing low value issue and try to harvest credit.
  5. Always ask yourself what value you are bringing with your contribution. Is this issue truly worth your time?
  6. Always pick issue with Drupal core or contributed modules with higher uses. You can see uses stats of a module on module page. Module uses

Official Contribution Guidelines

  1. Contributor guide
  2. Contribute to Drupal core
  3. Issue etiquette - MUST READ for all contributors DO’s and DON’Ts

Finding Issues to Contribute

Before contributing to Drupal, you should first find an issue that you would like to work on. Drupal has a large community of contributors and users, and there are many ways to find issues that need to be addressed. Here are a few resources that you can use:

  • Drupal.org issue queue: The Drupal.org issue queue is the primary location for tracking issues related to Drupal core and contributed modules. You can filter the issue queue to find issues that are suitable for your skill level or interests.

  • Drupal Slack: The Drupal Slack community is a great place to connect with other Drupal contributors and ask for help finding issues or getting started with a contribution.

DO’S AND DON’TS

Types of Issues to Pick

Drupal welcomes contributions of all kinds, from code to documentation to testing. Here are some types of issues that are suitable for different skill levels:

  • Interns/Junior Developers: If you’re new to Drupal or development in general, start by picking up some easy issues that have been identified as “Novice” or “Beginner” level issues. These might involve fixing typos, improving documentation, or adding simple features to a module.

  • Senior Developers: If you have more experience with Drupal and development in general, consider picking up issues that are classified as “Intermediate” or “Advanced.” These might involve more complex changes to Drupal core or contributed modules.

  • Tech Leads: As a tech lead, you can contribute to Drupal by reviewing and testing patches submitted by other contributors. This is an important role in the Drupal community, as it helps ensure that patches are of high quality and meet the community’s coding standards.

Types of Issues to Avoid

There are some types of issues that you should avoid when contributing to Drupal. These include:

  • Coding standard fixes: While fixing coding standards is important, these types of issues should not be the sole focus of a contribution. If you come across a coding standard issue while working on another issue, feel free to fix it, but do not create a new issue just to fix coding standards.

  • Re-rolling patches: If a patch needs to be updated to work with a new version of Drupal or a contributed module, it is important to re-roll the patch. However, simply re-rolling a patch without making any other changes is not a meaningful contribution.

  • Fixing typo or case sensitivity issues: Typo or case sensitivity issues can be a common problem when working on Drupal. If you come across a typo or case sensitivity issue while working on another issue, You can ignore it or You can create the issue and tag it with novice or beginner and leave those issues for beginners who are new to Drupal. DON’T SPEND TIME FIXING TYPO OR CASE SENSITIVITY ISSUES.

Contributing to Drupal

Here are the steps to contribute to Drupal:

  1. Choose an issue to work on.
  2. Comment on the issue to let others know that you’re working on it.
  3. Fork the project.
  4. Create a new branch for your changes.
  5. Make your changes to the code or documentation.
  6. Write tests to ensure that your changes are working correctly.
  7. Commit your changes and push them to your fork.
  8. Create a pull request with a descriptive title and detailed description of your changes.

Conclusion

Contributing to Drupal is a great way to improve your skills, learn from other developers, and give back to the community. By following these guidelines, you can ensure that your contributions are of high quality and meet the needs of the community. If you have any questions or need help with your contribution, don’t hesitate to ask