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
Use bullets instead of numbers so we don't have to renumber resolutions
when resolutions are added to or removed from the ballot template.
Signed-off-by: Justin LaPolla <[email protected]>
Copy file name to clipboardExpand all lines: templates/ballot_template.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,22 +4,22 @@ This is a template ballot for HPSF project acceptance.
4
4
5
5
## Criteria for Emerging Stage
6
6
7
-
1. That the project has 2 TAC sponsors.
7
+
* That the project has 2 TAC sponsors.
8
8
-[ ] Approve
9
9
-[ ] Against
10
10
-[ ] Abstain
11
11
12
-
2. That the project aligns with the mission of the HPSF.
12
+
* That the project aligns with the mission of the HPSF.
13
13
-[ ] Approve
14
14
-[ ] Against
15
15
-[ ] Abstain
16
16
17
-
2. That the project has a code of conduct.
17
+
* That the project has a code of conduct.
18
18
-[ ] Approve
19
19
-[ ] Against
20
20
-[ ] Abstain
21
21
22
-
3. That the project has a publicly available governance document.
22
+
* That the project has a publicly available governance document.
23
23
-[ ] Approve
24
24
-[ ] Against
25
25
-[ ] Abstain
@@ -28,17 +28,17 @@ This is a template ballot for HPSF project acceptance.
28
28
29
29
To be considered for Established Stage, the project must meet the Emerging requirements as well as the following:
30
30
31
-
4. That the project is being used successfully in production by at least three independent end users which of adequate quality and scope.
31
+
* That the project is being used successfully in production by at least three independent end users which of adequate quality and scope.
32
32
-[ ] Approve
33
33
-[ ] Against
34
34
-[ ] Abstain
35
35
36
-
5. That the project has demonstrated development processes that lower barriers to contribution and ensure software quality necessary for increased adoption.
36
+
* That the project has demonstrated development processes that lower barriers to contribution and ensure software quality necessary for increased adoption.
37
37
-[ ] Approve
38
38
-[ ] Against
39
39
-[ ] Abstain
40
40
41
-
6. That the project has demonstrated a substantial ongoing flow of commits and merged contributions.
41
+
* That the project has demonstrated a substantial ongoing flow of commits and merged contributions.
42
42
-[ ] Approve
43
43
-[ ] Against
44
44
-[ ] Abstain
@@ -47,32 +47,32 @@ To be considered for Established Stage, the project must meet the Emerging requi
47
47
48
48
To graduate from Emerging or Established status, or for a new project to join as a Core project, a project must meet the Established stage criteria plus:
49
49
50
-
7. That the project has a defined governing body of at least 4 or more members (owners and core maintainers), of whom no more than 1/2 are affiliated with the same employer.
50
+
* That the project has a defined governing body of at least 4 or more members (owners and core maintainers), of whom no more than 1/2 are affiliated with the same employer.
51
51
-[ ] Approve
52
52
-[ ] Against
53
53
-[ ] Abstain
54
54
55
-
8. That the project has documented and publicly accessible description of the project's governance, decision-making, and release processes.
55
+
* That the project has documented and publicly accessible description of the project's governance, decision-making, and release processes.
56
56
-[ ] Approve
57
57
-[ ] Against
58
58
-[ ] Abstain
59
59
60
-
9. That the project has a healthy number of committers from at least two organizations, where a committer is defined as someone accept contributions to some or all of the project.
60
+
* That the project has a healthy number of committers from at least two organizations, where a committer is defined as someone accept contributions to some or all of the project.
61
61
-[ ] Approve
62
62
-[ ] Against
63
63
-[ ] Abstain
64
64
65
-
10. That the project has explicitly defined security reporting and incident mitigation processes, as appropriate to the security risks of the project.
65
+
* That the project has explicitly defined security reporting and incident mitigation processes, as appropriate to the security risks of the project.
66
66
-[ ] Approve
67
67
-[ ] Against
68
68
-[ ] Abstain
69
69
70
-
11. That the project has explicitly defined governance and committer processes.
70
+
* That the project has explicitly defined governance and committer processes.
71
71
-[ ] Approve
72
72
-[ ] Against
73
73
-[ ] Abstain
74
74
75
-
12. That the project has been widely adopted in the HPC ecosystem or in some important component thereof.
75
+
* That the project has been widely adopted in the HPC ecosystem or in some important component thereof.
0 commit comments