First, thank you very much, that you would like to contribute to django CMS. We always welcome contributions, like many other open-source projects. We are very thankful to the many present, past and future contributors, to our community heroes and to the members of the django CMS Association.
django CMS is governed by a Code of Conduct. All participants in our community and its various forums are expected to abide by it.
- Please report any bugs through GitHub issues.
- For security issues please see further below.
Here’s what the pull request process looks like in brief:
- Fork our GitHub repository, https://github.com/django-cms/django-cms
- Work locally and push your changes to your repository.
- When you feel your code is good enough for inclusion, send us a pull request.
- After that, please join the Slack Channel of our Pull Request Review work group (#workgroup-pr-review). This group of friendly community members is dedicated to reviewing pull requests. Report your PR and find a “pr review buddy” who is going to review your pull request.
- Get acknowledged by the django CMS community for your contribution :-)
To learn more about basic requirements and standards of code contribution, please familiarize yourself with our comprehensive documentation.
django CMS commits follow the Conventional Commits Guideline, please try to follow the Guidelines in your commit messages to ease our review & merge process.
In terms of proposing large feature additions, we follow the best practice of DEPS.
To create a proposal...
- please use this DEP template
- create a discussion in the main django CMS repository
- join the Tech Committee Slack Channel (#technical-committee) and ask for a RFC.
- After RFC is completed, add the proposal to the agenda of the TC for approval.
We maintain comprehensive contribution documentation. Please familiarise yourself with it before submitting any issues or pull requests.
Please have a look at our security policy for how to deal with security issues.
If you think you have discovered a security issue in our code, please do not raise it in any public forum until we have had a chance to deal with it.
You can join us online:
- in our django CMS Slack channel
You can join a work group and work collaboratively on django CMS
You can also follow:
- the @djangocms Twitter account for general announcements
You can become a member of the django CMS Association and receive benefits
Sign up for our Bounty program.
As part of the django CMS Association we have formed several work groups to work together on different django CMS development topics. If you want to become part of contributor team, feel free to join one of our groups. You will meet friendly people and improve your programming skills and make a real difference in the django CMS open source project.