Drupal Association members fund grants that make connections all over the world.
Last updated October 10, 2016.
Welcome to the Drupal Community! You're on this page (hopefully) because you are interested in contributing your time to the Drupal project and the Drupal community, and you don't know how to get started. We thank you for your interest, and hope you find that:
- Contributing makes you feel good
- Your contributions are valued
- Many of the tasks are fun to do
- The more you contribute, the more you learn
- Contributing makes you a more integrated part of the Drupal community
In this section (as it grows), you will hopefully be able to find specific tasks that interest you and that are quick (about an hour or less) and easy to get started on. You will also find links to how to get more deeply involved.
Adding new tasks
If you know of a task that would be appropriate for a new contributor to do, read the Adding New Tasks page to find out how to add it (there's a template).
If you need help completing your task, see the Getting help completing your task page.
New or Experienced Contributors
Some of these tasks are for any new contributor. Some are for people experienced with one type of contribution, but are new to a new type of task. Some are targeted to more experienced contributors.
New contributor tasks: Anyone
- Add keywords to a Community Documentation page
- Add screenshots for a Drupal issue
- Answer a support forum question
- Provide support in IRC
- Clean up and Triage a Documentation issue report
- Document steps to reproduce a reported issue
- Handle or refer a support request in an issue
- Manually do accessibility testing of a patch for a Drupal issue
- Manually test a patch for a Drupal issue
- Triage: Verify a reported issue
- Identify duplicate issues
- Triage issues tagged as Novice
New contributor tasks: Non-English language speakers
New contributor tasks: Programmers
- Backport a Drupal core patch
- Create a patch for a Drupal core issue
- Determine if an old patch is still relevant
- Improve patch coding standards and documentation
- Manually testing a Twig patch for a Drupal core issue
- Re-roll a Drupal core patch
- Review a Drupal core patch
- Write an automated test for a Drupal core bug
- Write an issue summary for an existing Drupal Core issue
- Write up a change record for a Drupal core issue
- Profiling a Twig patch for a Drupal core issue
- Properly Writing Comments For Modules and Themes
- Evaluate if a Drupal core issue is allowed in beta
- Reporting and verifying bugs
New contributor tasks: Writers
- Respond to a documentation issue report
- Edit a Community Documentation page
- Fix a Community Documentation page title
- Incorporate comments into a Community Documentation page
- Review or fix user interface text in a Core or contrib issue