Skip to content

Commit b3de318

Browse files
christopherclarkchristopherclark
authored
Merge pull request #1175 from cloudfoundry/2025-election
2025 election
2 parents a121224 + 35ae274 commit b3de318

6 files changed

Lines changed: 234 additions & 0 deletions

File tree

‎elections/2025/Paketo-SC/README.md‎

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
# 2025 Paketo Buildpacks Steering Committee Election Guide
2+
3+
4+
## Overview
5+
6+
The role of this inuagural election is to fill two (2) seats on the Paketo Buildpacks Steering Committee. The nominees who receive the most votes will serve two (2) year terms.
7+
8+
For more information on the Paketo Buildpack Steering Committee, [please read this](https://github.com/paketo-buildpacks/community/blob/main/STEERING.md).
9+
10+
11+
## Schedule
12+
13+
- **June 2**: Election is announced and candidate nomination period begins
14+
- **June 12, 5:00 pm PDT**: Candidate nomination period ends
15+
- **June 12, 11:59 pm PDT**: Election begins
16+
- **June 24, 11:59 pm PDT**: Election ends
17+
- **June 26**: Announcement of results
18+
19+
20+
## Candidate Processes
21+
22+
23+
### Nominations
24+
25+
26+
Every eligible voter can nominate candidates for the Steering Committee, and we encourage you to do so. If you are
27+
eligible to serve on the committee, you can self-nominate. If you want to nominate someone else, do so as
28+
well.
29+
30+
31+
You can nominate someone for the Steering Committee by [submitting an issue using this template](https://github.com/cloudfoundry/community/issues/new?assignees=&labels=election&template=paketo-buildpacks-sc-candidate-nomination.md&title=Paketo+Buildpacks+Steering+Committee+Candidate+Nomination+for+%5BPerson+Name%5D).
32+
33+
34+
The deadline is June 12th to be nominated (and for the nominee to indicate acceptance).
35+
36+
37+
It is strongly recommended that you confirm that a nominee is interested and willing
38+
to accept the nomination prior to submitting the nomination issue.
39+
40+
41+
### Confirming Nominee Eligibility
42+
43+
44+
Once a nomination is received, the CFF staff or existing Steering Committee will contact the nominee to confirm acceptance
45+
of the nomination. If the nominee accepts, they will be added to the list of nominees at the bottom
46+
of this file. The nomination issue will be closed, noting if the nominee accepted or declined the
47+
nomination.
48+
49+
50+
## Voting Process
51+
52+
53+
The 2025 Paketo Buildpacks Steering Committee election will be conducted using a [CFF-managed instance](https://elections.cloudfoundry.org) of [Elekto](https://elekto.dev), a CNCF infrastructure project
54+
that implements Condorcet ranked-choice voting using the Schulze method. Elekto relies on GitHub
55+
for user identity and authentication, which better matches how members interact with the Cloud
56+
Foundry community on a day-to-day basis than the email identity that the [Condorcet Internet Voting
57+
Service](https://civs1.civs.us/) requires.
58+
59+
As stated in the Paketo [Steering Committee documentation](https://github.com/paketo-buildpacks/community/blob/main/STEERING.md), any individual who has contributed to Paketo Buildpacks in the twelve months prior to the election is eligible to vote in the Steering Committee election. Contributions include, but are not limited to, opening PRs, reviewing and commenting on PRs, opening and commenting on issues, writing design docs, commenting on design docs, participating in mailing list discussions and participating in working groups.
60+
61+
If Elekto fails to recognize you as eligible to vote in this election even though you believe you
62+
should be, please file a voting exception request [within the Elekto app](https://elections.cloudfoundry.org/app/elections/2025---Paketo-SC/exception) or [via an issue on the
63+
community repository](https://github.com/cloudfoundry/community/issues/new?assignees=&labels=election&template=request-to-be-elector-for-paketo-buildpacks-sc-election.md&title=Request+to+be+an+elector+for+Paketo+Steering+Committee+election).
64+
65+
Once the official election period starts, you will be able to rank the candidates in your preferred
66+
order and submit your ballot. You may set a password on your ballot, which is required to change
67+
your ballot later within the election period. Once the election period ends, all ballots are final.
68+
69+
All ballot data for Elekto is stored on a database managed by the CFF staff, and is not shared with
70+
third parties. Individual ballot data is encrypted, and ballot data can be retrieved only in
71+
aggregate form.
72+
73+
74+
## Election Results
75+
76+
77+
The newly elected body will be announced via cf-dev@lists.cloudfoundry.org and main@lists.paketo.io on 26 Jun, 2025.
78+
79+
80+
Following the announcement, the voting results and winners will be published.

‎elections/2025/Paketo-SC/election.yaml‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
name: 2025 Paketo Buildpacks Steering Committee election
2+
organization: Cloud Foundry Foundation
3+
start_datetime: 2025-06-12 06:59:00 # 11:59 pm PDT, 12 Jun 2025
4+
end_datetime: 2025-06-24 06:59:00 # 11:59 pm PDT, 24 Jun 2025
5+
no_winners: 1
6+
allow_no_opinion: True
7+
delete_after: True
8+
show_candidate_fields:
9+
- employer
10+
- github
11+
- slack
12+
election_officers:
13+
- loewenstein-sap
14+
- christopherclark
15+
- sgreenberg
16+
eligibility: Any individual who has contributed to Paketo Buildpacks in the twelve months prior to the election is eligible to vote in the Steering Committee election. Each election cycle, an initial set of voters will be identified through automated reporting. Any individual who has at least 10 measurable contributions in the last 12 months will be automatically added to the eligible voter list.
17+
exception_description: If you feel you are eligible to vote but are not represented in the list of voters, please request an exception to allow you to vote via the Elekto application.
18+
exception_due: 2025-06-22 06:59:00 # 11:59 pm PT, 22 Jun 2025

‎elections/2025/Paketo-SC/election_desc.md‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
The role of this election is to fill the two (2) seats due for election this year on the Paketo Buildpacks Steering Committee. The nominees who recieves the most votes will serve two (2) year terms. This is a brief summary of the election; for more details, such as how to become a candidate, [see the README](https://github.com/cloudfoundry/community/tree/main/elections/2025/Paketo-SC#readme).
2+
3+
## Eligibility
4+
5+
Any individual who has contributed to Paketo Buildpacks in the twelve months prior to the election is eligible to vote in the Steering Committee election. You will see either ELIGIBLE or NOT ELIGIBLE at the top of this screen. If Elekto fails to recognize you as eligible to vote in this election even though you believe you should be, please file a voting exception request [within the Elekto app](https://elections.cloudfoundry.org/app/elections/2025---Paketo-SC/exception) or [via an issue on the community repository](https://github.com/cloudfoundry/community/issues/new?assignees=&labels=election&template=request-to-be-elector-for-paketo-buildpacks-sc-election.md&title=Request+to+be+an+elector+for+Paketo+Steering+Committee+election). The deadline for filing exceptions is June 22nd, 11:59 pm PT.
6+
7+
## Schedule
8+
9+
June 2: Election is announced and candidate nomination period begins
10+
June 12, 5:00 pm PDT: Candidate nomination period ends
11+
June 12, 11:59 pm PDT: Election begins
12+
June 24, 11:59 pm PDT: Election ends
13+
June 26: Announcement of results
14+
15+
## Changing Your Vote
16+
17+
With Elekto, you may revoke and re-cast your ballot until the election deadline of June 24th. To do so, set a passphrase when you cast your ballot; as long as you have that passphrase, you may re-cast your ballot by returning to the site.

‎elections/2025/TOC/README.md‎

Lines changed: 82 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,82 @@
1+
# 2025 CFF TOC Election Guide
2+
3+
4+
## Overview
5+
6+
7+
Each year, the CFF technical community holds an election for open seats on the
8+
Technical Oversight Committee (TOC). The rules governing this election are set in the
9+
[CFF's project charter](../../../governing-board/charter.md) (See section 7(b) and 7(e)
10+
for the relevant details).
11+
12+
13+
## Schedule
14+
15+
- **June 2**: Election is announced and candidate nomination period begins
16+
- **June 12, 5:00 pm PDT**: Candidate nomination period ends
17+
- **June 12, 11:59 pm PDT**: Election begins
18+
- **June 24, 11:59 pm PDT**: Election ends
19+
- **June 26**: Announcement of results
20+
21+
22+
## Candidate Processes
23+
24+
25+
### Nominations
26+
27+
28+
Every eligible voter can nominate candidates for the TOC, and we encourage you to do so. If you are
29+
eligible to serve on the TOC, you can self nominate! If you want to nominate someone else, do so as
30+
well!
31+
32+
33+
You can nominate someone for the TOC by [submitting an issue using this template](https://github.com/cloudfoundry/community/issues/new?assignees=&labels=election&template=toc-candidate-nomination.md&title=TOC+Candidate+Nomination+for+%5BPerson+Name%5D).
34+
35+
36+
The deadline is June 12th to be nominated (and for the nominee to indicate acceptance).
37+
38+
39+
It is strongly recommended that you confirm that a nominee is interested and willing
40+
to accept the nomination prior to submitting the nomination issue.
41+
42+
43+
### Confirming Nominee Eligibility
44+
45+
46+
Once a nomination is received, the CFF staff will contact the nominee to confirm acceptance
47+
of the nomination. If the nominee accepts, they will be added to the list of nominees at the bottom
48+
of this file. The nomination issue will be closed, noting if the nominee accepted or declined the
49+
nomination.
50+
51+
52+
## Voting Process
53+
54+
55+
The 2025 TOC election will be conducted using a [CFF-managed instance](https://elections.cloudfoundry.org) of [Elekto](https://elekto.dev), a CNCF infrastructure project
56+
that implements Condorcet ranked-choice voting using the Schulze method. Elekto relies on GitHub
57+
for user identity and authentication, which better matches how members interact with the Cloud
58+
Foundry community on a day-to-day basis than the email identity that the [Condorcet Internet Voting
59+
Service](https://civs1.civs.us/) requires.
60+
61+
Any individual who has contributed to CFF projects or technical working groups in the twelve months prior to the election is eligible to vote in the TOC election. Contributions include, but are not limited to, opening PRs, reviewing and commenting on PRs, opening and commenting on issues, writing design docs, commenting on design docs, participating in mailing list discussions and participating in working groups.
62+
63+
If Elekto fails to recognize you as eligible to vote in this election even though you believe you
64+
should be, please file a voting exception request [within the Elekto app](https://elections.cloudfoundry.org/app/elections/2025---TOC/exception) or [via an issue on the
65+
community repository](https://github.com/cloudfoundry/community/issues/new?assignees=&labels=election&template=request-to-be-elector-for-toc-election.md&title=Request+to+be+an+elector+for+TOC+election).
66+
67+
Once the official election period starts, you will be able to rank the candidates in your preferred
68+
order and submit your ballot. You may set a password on your ballot, which is required to change
69+
your ballot later within the election period. Once the election period ends, all ballots are final.
70+
71+
All ballot data for Elekto is stored on a database managed by the CFF staff, and is not shared with
72+
third parties. Individual ballot data is encrypted, and ballot data can be retrieved only in
73+
aggregate form.
74+
75+
76+
## Election Results
77+
78+
79+
The newly elected body will be announced via cf-dev@lists.cloudfoundry.org on 26 Jun, 2024.
80+
81+
82+
Following the announcement, the voting results and winners will be published.

‎elections/2025/TOC/election.yaml‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
name: 2025 CFF Technical Oversight Committee election
2+
organization: Cloud Foundry Foundation
3+
start_datetime: 2025-06-12 06:59:00 # 11:59 pm PDT, 12 Jun 2025
4+
end_datetime: 2025-06-24 06:59:00 # 11:59 pm PDT, 24 Jun 2025
5+
no_winners: 3
6+
allow_no_opinion: True
7+
delete_after: True
8+
show_candidate_fields:
9+
- employer
10+
- github
11+
- slack
12+
election_officers:
13+
- beyhan
14+
- rkoster
15+
- christopherclark
16+
- ramiyengar
17+
- sgreenberg
18+
eligibility: Any individual who has contributed to any Cloud Foundry Foundation project in the twelve months prior to the election is eligible to vote in the TOC election. See [the voter eligibility section](https://github.com/cloudfoundry/community/blob/main/toc/TOC.md#community-eligibility-to-vote-in-toc-elections) for more information.
19+
exception_description: If you feel you are eligible to vote but are not represented in the list of voters, please request an exception to allow you to vote via the Elekto application.
20+
exception_due: 2025-06-22 06:59:00 # 11:59 pm PT, 22 Jun 2025

‎elections/2025/TOC/election_desc.md‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
The role of this election is to fill the three (3) seats due for election this year on the Cloud Foundry Foundation TOC. The elected members will serve two (2) year terms. This is a brief summary of the election; for more details, such as how to become a candidate, [see the README](https://github.com/cloudfoundry/community/tree/main/elections/2025/TOC#readme).
2+
3+
## Eligibility
4+
5+
Anyone who has contributed to a Cloud Foundry Foundation project over the last year is eligible to vote. You will see either ELIGIBLE or NOT ELIGIBLE at the top of this screen. If Elekto fails to recognize you as eligible to vote in this election even though you believe you should be, please file a voting exception request [within the Elekto app](https://elections.cloudfoundry.org/app/elections/2025---TOC/exception) or via an issue on the community repository. The deadline for filing exceptions is June 20th, 11:59 pm PT.
6+
7+
## Schedule
8+
9+
June 2: Election is announced and candidate nomination period begins
10+
June 12, 5:00 pm PDT: Candidate nomination period ends
11+
June 12, 11:59 pm PDT: Election begins
12+
June 24, 11:59 pm PDT: Election ends
13+
June 26: Announcement of results
14+
15+
## Changing Your Vote
16+
17+
With Elekto, you may revoke and re-cast your ballot until the election deadline of June 24th. To do so, set a passphrase when you cast your ballot; as long as you have that passphrase, you may re-cast your ballot by returning to the site.

0 commit comments

Comments
 (0)