Skip to content

Commit 120241f

Browse files
committed
Avoid renumbering resolutions
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]>
1 parent b58b14b commit 120241f

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

templates/ballot_template.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -4,22 +4,22 @@ This is a template ballot for HPSF project acceptance.
44

55
## Criteria for Emerging Stage
66

7-
1. That the project has 2 TAC sponsors.
7+
* That the project has 2 TAC sponsors.
88
- [ ] Approve
99
- [ ] Against
1010
- [ ] Abstain
1111

12-
2. That the project aligns with the mission of the HPSF.
12+
* That the project aligns with the mission of the HPSF.
1313
- [ ] Approve
1414
- [ ] Against
1515
- [ ] Abstain
1616

17-
2. That the project has a code of conduct.
17+
* That the project has a code of conduct.
1818
- [ ] Approve
1919
- [ ] Against
2020
- [ ] Abstain
2121

22-
3. That the project has a publicly available governance document.
22+
* That the project has a publicly available governance document.
2323
- [ ] Approve
2424
- [ ] Against
2525
- [ ] Abstain
@@ -28,17 +28,17 @@ This is a template ballot for HPSF project acceptance.
2828

2929
To be considered for Established Stage, the project must meet the Emerging requirements as well as the following:
3030

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.
3232
- [ ] Approve
3333
- [ ] Against
3434
- [ ] Abstain
3535

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.
3737
- [ ] Approve
3838
- [ ] Against
3939
- [ ] Abstain
4040

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.
4242
- [ ] Approve
4343
- [ ] Against
4444
- [ ] Abstain
@@ -47,32 +47,32 @@ To be considered for Established Stage, the project must meet the Emerging requi
4747

4848
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:
4949

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.
5151
- [ ] Approve
5252
- [ ] Against
5353
- [ ] Abstain
5454

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.
5656
- [ ] Approve
5757
- [ ] Against
5858
- [ ] Abstain
5959

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.
6161
- [ ] Approve
6262
- [ ] Against
6363
- [ ] Abstain
6464

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.
6666
- [ ] Approve
6767
- [ ] Against
6868
- [ ] Abstain
6969

70-
11. That the project has explicitly defined governance and committer processes.
70+
* That the project has explicitly defined governance and committer processes.
7171
- [ ] Approve
7272
- [ ] Against
7373
- [ ] Abstain
7474

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.
7676
- [ ] Approve
7777
- [ ] Against
7878
- [ ] Abstain

0 commit comments

Comments
 (0)