Join our growing Backdrop contributor community.

To apply, create a request as an issue in our queue. If you have started writing or porting a project for Backdrop, please include a link to the module, theme, or layout you have written.

If you have posted the code under your own GitHub account you will be able to transfer the entire repository to https://github.com/backdrop-contrib/[your_project_name] after joining the Backdrop Contributed Project Group.

The Application Process

  1. Create an issue in the Backdrop Contrib queue.
  2. A friendly community member will review your application, looking for the following:
    • Did you provide a link to a Backdrop module, theme or layout?
      • If so, does the project meet the three minimum requirements in the New project checklist?
      • Is there anything we might be able to help out with? -- If so we might offer suggestions.
        • NOTE: It is not necessary that you address any code suggestions before joining the group. These suggestions are only meant to be helpful, and will not be a barrier to entry.
    • If not, did you provide at least 2 links to Pull Requests or commits?
      • If so, do these changes represent strong collaboration skills?
    • If not, did you @-mention someone who will provide a recommendation for you?
      • If so, have they responded with the recommendation?
  3. If all checks out, you will be asked to agree to the Backdrop Contributed Project Agreement.
  4. You will agree.
  5. You will be invited to the Backdrop contrib group.

New project checklist

All projects must meet these minimum requirements:

Backdrop Contributed Project Agreement

By joining the Backdrop Contributed Project Group you agree to the following:

  1. You will not push changes to a repository for which you are not a current maintainer.
  2. You will work with the Backdrop Security Team to address any vulnerabilities in any project you create or maintain, if necessary.
  3. Any project you create or maintain will have the GitHub issue tracker enabled for official communication.
  4. You must agree to license your code contributions as GPLv2 or later.
    • Any project you create or maintain must include a copy of the GPL v2 LICENSE.txt file in the root of your repository. The GPLv2 license applies to all code that directly interacts with parts of Backdrop licensed as GPLv2 or later. See for the Backdrop License FAQ for a more detailed explanation.
    • You must confirm that you have the right to distribute any additional code, libraries, images, fonts or other assets written or created by any third party with code licensed as GPLv2 or later.
  5. Any project you create or maintain must include a README.md file containing at the least the following (you may use the example README.md to get started:
    • A list of the current maintainers for the Backdrop project
    • A description of the project
    • Basic documentation
    • License information for the project (GPL v2)
    • License information for any additional assets (SIL OFL fonts, CC-SA images, etc)
    • Credits acknowledging past maintainers for the Backdrop or Drupal project.
  6. If any of the above requirements are not met, your access to the Backdrop Contrib group -- including all projects, even those that you may have originally authored -- may be revoked.
  7. If your project becomes abandoned and you do not respond to requests in the issue tracker within 2 weeks, your project may be modified by a Backdrop Contrib administrator without your explicit consent.

Rejected applications:

  • No rejected application to the Backdrop contrib group is final.
  • In the rare case that your application is rejected, you are welcome to reapply after a waiting period of 1 month.
  • After 1 month has passed, please open a new issue in the queue and try again.
  • Please carefully review the reason for rejection so that history does not repeat itself.