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 lhttps://github.com/backdrop-contrib/[your_project_name] after joining the Backdrop Contributed Project Group.
New project checklist
All projects must meet these minimum requirements.
- Include a LICENSE.txt file that indicates the code is GPL v2. You can use this copy.
- Include a README.md file that includes license and maintainer information. You can use this example.
- Maintain the Git history from Drupal 7. See this article.
Backdrop Contributed Project Agreement
By joining the Backdrop Contributed Project Group (Backdrop Contrib, for short) you agree to the following:
- You will not push changes to a repository for which you are not a current maintainer (even though joining the Backdrop Contrib group will grant you access to push to any project within).
- 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.
- Any project you create or maintain must include a README.md file containing at the least the following:
- 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)
- A list of the current maintainers for the Backdrop project
- Credits acknowledging past maintainers for the Backdrop or Drupal projects
- You may use this example README.md to get started.
- You will work with the Backdrop Security Team to address any vulnerabilities in any project you create or maintain, if necessary.
- Any project you create or maintain will have the GitHub issue tracker enabled for official communication.
- If any of the above requirements are not met, your access to the Backdrop Contrib group -- including all projects and even those that you may have originally authored -- may be revoked.
- 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.
You may apply to adopt an abandoned project. The procedure is as follows:
- If you haven't already, please join the Backdrop Contrib group by submitting an application (see above).
- File an issue with the current project requesting to help maintain the project.
- If written permission is granted by a current maintainer, create a PR that adds your name to the README.md file in the list of maintainers.
- If a current maintainer does not respond within 2 weeks create an issue in this repository to take over the project. Please include a link to the issue you filed with the abandoned project.
- After confirming the project has been abandoned, a Backdrop Contrib administrator will add your name to the list of maintainers in that project's README.md file.
- You may now maintain the project directly as though given permission by the project maintainers, and likewise now grant permission to others to maintain the project.
- 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.