8000 Add CONTRIBUTING.rst and CODE_OF_CONDUCT.rst to develop-4 branch · django-cms/django-cms@be694b7 · GitHub
[go: up one dir, main page]
Skip to content

Commit be694b7

Browse files
fsbraunfsbraun
committed
Add CONTRIBUTING.rst and CODE_OF_CONDUCT.rst to develop-4 branch
1 parent 19c66fe commit be694b7

File tree

2 files changed

+109
-0
lines changed

2 files changed

+109
-0
lines changed

‎CODE_OF_CONDUCT.rst

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
==========================
2+
django CMS Code of Conduct
3+
==========================
4+
5+
django CMS is governed by a `Code of Conduct
6+
<http://docs.django-cms.org/en/latest/contributing/code_of_conduct.html>`_.
7+
All participants in our community and its various forums are expected to abide by it.

‎CONTRIBUTING.rst

Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
============
2+
CONTRIBUTING
3+
============
4+
5+
First, thank you very much, that you would like to contribute to django CMS.
6+
We always welcome contributions, like many other open-source projects. We are
7+
very thankful to the many `present, past and future contributors <https://github.com/django-cms/django-cms/graphs/contributors>`_, to our `community heroes <https://github.com/django-cms/django-cms-mgmt/blob/master/community%20heros/list%20of%20community%20heros.md>`_ and to the `members of the django CMS Association <https://github.com/django-cms/django-cms-mgmt/blob/master/association/members.md>`_.
8+
9+
10+
Code of Conduct
11+
===============
12+
13+
django CMS is governed by a `Code of Conduct
14+
<http://docs.django-cms.org/en/latest/contributing/code_of_conduct.html>`_.
15+
All participants in our community and its various forums are expected to abide by it.
16+
17+
18+
Issues
19+
======
20+
21+
* Please report **any bugs** through `GitHub issues <https://github.com/django-cms/django-cms/issues>`_.
22+
* For *security issues* please see further below.
23+
24+
Contributing Code
25+
================
26+
27+
Here’s what the pull request process looks like in brief:
28+
29+
1. Fork our GitHub repository, https://github.com/django-cms/django-cms
30+
2. Work locally and push your changes to your repository.
31+
3. When you feel your code is good enough for inclusion, send us a pull request.
32+
4. After that, please join the `Slack Channel <https://www.django-cms.org/slack>`_ 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.
33+
5. Get acknowledged by the django CMS community for your contribution :-)
34+
35+
To learn more about basic requirements and standards of code contribution, please familiarize yourself with our comprehensive `documentation <https://docs.django-cms.org/en/latest/contributing/code.html#>`_.
36+
37+
django CMS commits follow the `Conventional Commits Guideline <https://conventionalcommits.org/>`_, please try to follow the Guidelines in your commit messages to ease our review & merge process.
38+
39+
40+
Proposing large feature additions
41+
=================================
42+
43+
In terms of proposing large feature additions, we follow the best practice of `DEPS <https://github.com/django/deps>`_.
44+
45+
To create a proposal...
46+
47+
1. please use this `DEP <https://github.com/django/deps/blob/main/template.rst>`_ template
48+
49+
2. create a discussion in the main `django CMS repository <https://github.com/django-cms/django-cms/discussions>`_
50+
51+
3. join the `Tech Committee <https:/github.com/django-cms/django-cms-mgmt/blob/master/tech-committee/about.md>`_ `Slack Channel <https://www.django-cms.org/slack>`_ (#technical-committee) and ask for a RFC.
52+
53+
4. After RFC is completed, add the proposal to the `agenda <https://hackmd.io/ddhvq_aqS6my9gwhLddyPg>`_ of the TC for approval.
54+
55+
56+
Contribution documentation
57+
==========================
58+
59+
We maintain comprehensive `contribution documentation <http://docs.django-cms.org/en/latest/contributing/>`_.
60+
Please familiarise yourself with it before submitting any issues or pull requests.
61+
62+
63+
Security issues
64+
===============
65+
66+
Please have a look at our security policy for
67+
`how to deal with security issues <http://docs.django-cms.org/en/latest/contributing/development-policies.html#reporting-security-issues>`_.
68+
69+
If you think you have discovered a security issue in our code, please do not raise it in any public
70+
forum until we have had a chance to deal with it.
71+
72+
73+
Community & Association
74+
=======================
75+
76+
You can join us online:
77+
78+
* in our `django CMS Slack channel <https://www.django-cms.org/slack>`_
79+
80+
You can join a work group and work collaboratively on django CMS
81+
82+
* `work groups <https://www.django-cms.org/en/join-work-group/>`_
83+
84+
You can also follow:
85+
86+
* the `@djangocms <https://twitter.com/djangocms>`_ Twitter account for general announcements
87+
88+
You can become a member of the django CMS Association and receive benefits
89+
90+
* `Membership <https://www.django-cms.org/en/memberships/>`_
91+
92+
93+
Receive rewards for submitting pull requests
94+
--------------------------------------------
95+
96+
Sign up for our `Bounty program <https://www.django-cms.org/en/bounty-program/>`_.
97+
98+
99+
Join a work group
100+
=================
101+
102+
As part of the django CMS Association we have formed several `work groups <https://docs.django-cms.org/en/latest/contributing/code.html#>`_ 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.

0 commit comments

Comments
 (0)
0