Skip to content

Commit 6345d7b

Browse files
authored
Create cjr.md
1 parent f59512e commit 6345d7b

File tree

1 file changed

+49
-0
lines changed

1 file changed

+49
-0
lines changed

cjr.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
layout: page
3+
title: Contribution Justification Report
4+
subtitle: Document Your Contribution with Evidence
5+
cover-img:
6+
- "/assets/img/section-cover.png"
7+
---
8+
9+
This report must accompany every contribution. Its purpose is to demonstrate how the submission aligns with the framework’s governance principles and provide supporting evidence. Contributors should complete all sections to facilitate evaluation by the Steering Committee.
10+
11+
## 1. Contribution Summary
12+
*Description: Provide a brief summary of your contribution. Explain what the change, addition, or improvement is, and its intended impact on the framework.*
13+
14+
**Contribution Title:** [Insert title here]
15+
**Brief Summary:** [Insert text here]
16+
17+
## 2. Alignment with Governance Principles
18+
*Description: Explain how your contribution meets each of the following principles.*
19+
20+
- **Continuous Improvement:** [Insert explanation of how the contribution helps the framework adapt to emerging needs, technologies, or cyber threats while preserving core values]
21+
- **Evidence-Based Evolution:** [Insert supporting evidence. Preferably peer-reviewed publications; if not available, provide other credible sources such as pilot projects, case studies, or white papers. Opinions only are not enough.]
22+
- **Broad Applicability:** [Insert explanation of how the contribution benefits a wide range of organizations and contexts]
23+
- **Public Sector Priority:** [Insert explanation of how the contribution addresses public sector needs; if private sector aspects are included, justify why they do not compromise public requirements]
24+
25+
## 3. Evidence and References
26+
*Description: Include all references that support your contribution. Provide URLs, DOIs, or citations for research papers, case studies, or other credible sources. Clearly link the evidence to the claims made in the previous section.*
27+
28+
**References:**
29+
- [Insert reference 1]
30+
- [Insert reference 2]
31+
- [Insert additional references as needed]
32+
33+
## 4. Implementation/Modification Details (if applicable)
34+
*Description: Provide technical or procedural details about how the contribution should be implemented within the framework. Include any dependencies, requirements, or potential impacts on existing components.*
35+
36+
[Insert implementation/modification details here]
37+
38+
## 5. Expected Impact
39+
*Description: Describe the expected benefits or improvements resulting from the contribution. Highlight measurable outcomes if possible (e.g., improved usability, security, adaptability).*
40+
41+
[Insert expected impact here]
42+
43+
## 6. Additional Notes
44+
*Description: Include any other relevant information that may help the Steering Committee evaluate the contribution, such as limitations, risks, or alternative approaches considered.*
45+
46+
[Insert additional notes here]
47+
48+
**Note to Contributors:**
49+
*Incomplete reports or contributions lacking supporting evidence may be rejected. Please ensure that all sections are fully addressed.*

0 commit comments

Comments
 (0)