Skip to content

Correct ballot template emerging stage resolutions #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jlapolla-cray wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Correct ballot template emerging stage resolutions #52

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b58b14b
Correct ballot template emerging stage resolutions
jlapolla-cray Sep 23, 2025
bd594a3
Update ballot template resolution numbering
jlapolla-cray Sep 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 15 additions & 10 deletions templates/ballot_template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,12 @@ This is a template ballot for HPSF project acceptance.
- [ ] Against
- [ ] Abstain

3. That the project has a publicly available governance document.
3. That the project has a code of conduct.
- [ ] Approve
- [ ] Against
- [ ] Abstain

4. That the project has a publicly available governance document.
- [ ] Approve
- [ ] Against
- [ ] Abstain
Expand All @@ -23,17 +28,17 @@ This is a template ballot for HPSF project acceptance.

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

4. That the project is being used successfully in production by at least three independent end users which of adequate quality and scope.
5. That the project is being used successfully in production by at least three independent end users which of adequate quality and scope.
- [ ] Approve
- [ ] Against
- [ ] Abstain

5. That the project has demonstrated development processes that lower barriers to contribution and ensure software quality necessary for increased adoption.
6. That the project has demonstrated development processes that lower barriers to contribution and ensure software quality necessary for increased adoption.
- [ ] Approve
- [ ] Against
- [ ] Abstain

6. That the project has demonstrated a substantial ongoing flow of commits and merged contributions.
7. That the project has demonstrated a substantial ongoing flow of commits and merged contributions.
- [ ] Approve
- [ ] Against
- [ ] Abstain
Expand All @@ -42,32 +47,32 @@ To be considered for Established Stage, the project must meet the Emerging requi

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:

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.
8. 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.
- [ ] Approve
- [ ] Against
- [ ] Abstain

8. That the project has documented and publicly accessible description of the project's governance, decision-making, and release processes.
9. That the project has documented and publicly accessible description of the project's governance, decision-making, and release processes.
- [ ] Approve
- [ ] Against
- [ ] Abstain

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.
10. 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.
- [ ] Approve
- [ ] Against
- [ ] Abstain

10. That the project has explicitly defined security reporting and incident mitigation processes, as appropriate to the security risks of the project.
11. That the project has explicitly defined security reporting and incident mitigation processes, as appropriate to the security risks of the project.
- [ ] Approve
- [ ] Against
- [ ] Abstain

11. That the project has explicitly defined governance and committer processes.
12. That the project has explicitly defined governance and committer processes.
- [ ] Approve
- [ ] Against
- [ ] Abstain

12. That the project has been widely adopted in the HPC ecosystem or in some important component thereof.
13. That the project has been widely adopted in the HPC ecosystem or in some important component thereof.
- [ ] Approve
- [ ] Against
- [ ] Abstain
Expand Down