You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: contributions.md
+28-5Lines changed: 28 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ cover-img:
8
8
9
9
## Contributions
10
10
11
-
We love seeing community contributions! Before submitting, please make sure you have signed the Contributor License Agreement (CLA). All contributions should follow our governance principles to keep the framework reliable, relevant, and useful for everyone.
11
+
We love seeing community contributions! All contributions should follow our governance principles to keep the framework reliable, relevant, and useful for everyone.
12
12
13
13
-**Continuous Improvement**: Help the framework evolve with new needs, technologies, and cyber threats, while staying true to its core values.
14
14
-**Evidence-Based Evolution**: Back up your contribution with solid evidence—peer-reviewed publications are ideal, but other credible sources are welcome too. Opinions alone are not enough.
@@ -17,10 +17,33 @@ We love seeing community contributions! Before submitting, please make sure you
17
17
18
18
See [Governance](/governance) section for additional information.
19
19
20
-
### Submission Requirements
20
+
Please include a justification report with your contribution. This report should explain how your submission aligns with the principles above and include any supporting evidence. The Steering Committee will review this report before accepting your contribution.
21
21
22
-
Please include a short justification report with your contribution. This report should explain how your submission aligns with the principles above and include any supporting evidence. The Steering Committee will review this report before accepting your contribution.
22
+
See the [Contribution Justification Template](/cjt) you should complete and add to your contribution.
23
23
24
-
Your contributions help the framework grow stronger and more useful for everyone—thank you for helping us improve!
24
+
Finally, before submitting, please make sure you have signed the Contributor License Agreement (CLA). The CLA ensures that your contributions can be legally incorporated into the project. It will appear when necessary but just for you to know this will be the content of the [Contributor License Agreement](/cla)
25
+
26
+
Your contributions help the framework grow stronger and more useful for everyone, thank you for helping us improve!
27
+
28
+
### How to Contribute
29
+
30
+
Contributions should follow the standard open-source workflow:
31
+
32
+
1.**Fork the repository** of the project you want to contribute to.
33
+
Make sure you fork from the branch you want to contribute to (direct contributions to the `master` branch are **not allowed**).
34
+
35
+
2.**Make your changes** in your fork.
36
+
37
+
3. Once your changes are ready, go to the **Create Pull Request** option to submit your contribution to the official project.
38
+
39
+
4. When creating the pull request:
40
+
- Select the branch in your repository where you made the changes as the **source**.
41
+
- Select the branch in the official repository where you want your changes to be merged as the **target**.
42
+
- Provide a **title** for your contribution.
43
+
- In the **description**, write the **Contribution Justification Report**, following the provided template.
44
+
45
+
5.**Sign the CLA**: Before the pull request can be merged, a Contributor License Agreement (CLA) will appear for you to review and sign.
0 commit comments