Skip to content

Commit c14ed65

Browse files
Merge branch 'main' into Add-Shwetha-app-runtime-interfaces-reviewers
2 parents 1854616 + d210218 commit c14ed65

15 files changed

+655
-24
lines changed
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
name: Paketo Buildpacks SC Candidate Nomination
3+
about: Paketo Buildpacks Steering Committee Candidate Nomination for Election Cycle
4+
title: Paketo Buildpacks Steering Committee Candidate Nomination for [Person Name]
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
Candidate Name: [name of person being nominated]
11+
12+
Candidate GitHub Username: [GitHub username of person being nominated]
13+
14+
Affiliation: [employer of candidate]
15+
16+
Nomination Statement: [Describe why this person (or you!) would make a good member of the TSC]
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
name: Request to be elector for Paketo Buildpacks SC election
3+
about: Requests for community members to be added as electors for a Paketo Buildpacks
4+
Steering Committee election cycle.
5+
title: Request to be elector for Paketo Buildpacks Steering Committee election
6+
labels: election
7+
assignees: ''
8+
9+
---
10+
11+
Github Username: [put the username to be added]
12+
13+
Affiliation: [employer of candidate]
14+
15+
Community participation: [describe your community participation over the last year]

.github/ISSUE_TEMPLATE/request-to-be-elector-for-toc-election.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,4 +11,4 @@ Github Username: [put the username to be added]
1111

1212
Affiliation: [employer of candidate]
1313

14-
Community participation: [describe your community participation over the last year]
14+
Community participation: [describe your community participation over the last year]

elections/2023/Paketo-SC/README.md

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
# 2023 Paketo Buildpacks Steering Committee Election Guide
2+
3+
4+
## Overview
5+
6+
The role of this inuagural election is to fill three (3) seats on the Paketo Buildpacks Steering Committee. The two nominees who recieve the most votes will serve two (2) year terms, and the nominee who recieves the third most votes will serve a one (1) year term. In subsequent elections, all terms will be for two (2) years.
7+
8+
This guide exists to serve as a guide to this year's election process. 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+
- **May 18**: Election is announced and candidate nomination period begins
14+
- **June 1, 5:00 pm PDT**: Candidate nomination period ends
15+
- **June 1, 11:59 pm PDT**: Election begins
16+
- **June 16, 11:59 pm PDT**: Election ends
17+
- **June 20**: 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 1st 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 2023 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/2023---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 [email protected] and [email protected] on 20 Jun, 2022.
78+
79+
80+
Following the announcement, the voting results and winners will be published.
Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
name: 2023 Paketo Buildpacks Steering Committee election
2+
organization: Cloud Foundry Foundation
3+
start_datetime: 2023-06-02 06:59:00 # 11:59 pm PDT, 01 Jun 2023
4+
end_datetime: 2023-06-17 06:59:00 # 11:59 pm PDT, 16 Jun 2023
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+
- christopherclark
14+
- emalm
15+
- dmikusa
16+
- sgreenberg
17+
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.
18+
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.
19+
exception_due: 2023-06-14 06:59:00 # 11:59 pm PT, 13 Jun 2023
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 Paketo Buildpacks Steering Committee. The two nominees who recieve the most votes will serve two (2) year terms, and the nominee who recieves the third most votes will serve a one (1) year term. In subsequent elections, all terms will be for two (2) years. 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/2023/Paketo#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/2023---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 13th, 11:59 pm PT.
6+
7+
## Schedule
8+
9+
May 18: Election is announced and candidate nomination period begins
10+
June 1, 5:00 pm PDT: Candidate nomination period ends
11+
June 1, 11:59 pm PDT: Election begins
12+
June 16, 11:59 pm PDT: Election ends
13+
June 20: 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 16th. 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/2023/Paketo-SC/voters.yaml

Lines changed: 95 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
---
2+
eligible_voters:
3+
- AidanDelaney
4+
- ajdergute
5+
- anthonydahanne
6+
- arjun024
7+
- Azbesciak
8+
- BarDweller
9+
- bbegw
10+
- belfo
11+
- bjongbloedt
12+
- blaenk
13+
- brayanhenao
14+
- c0d1ngm0nk3y
15+
- cforce
16+
- ChuckQuinnIV
17+
- conzetti
18+
- cz4rny
19+
- dashaun
20+
- davidmirror-ops
21+
- dmikusa
22+
- dpacheconr
23+
- dvigueras
24+
- eddumelendez
25+
- effulgentsia
26+
- ekcasey
27+
- emrekaratas06
28+
- engine-workflow
29+
- fg-j
30+
- fgrehm
31+
- findajay
32+
- ForestEckhardt
33+
- francescopersico
34+
- gkwan-ibm
35+
- goafabric
36+
- gudatcomputers
37+
- hibell
38+
- hovancik
39+
- imitbn
40+
- jansu76
41+
- jerzykrlkroche
42+
- jghiloni
43+
- johnkors
44+
- johnnyr0x
45+
- joshuatcasey
46+
- jpena-r7
47+
- kevin-ortega
48+
- kingdonb
49+
- kiranpatel11
50+
- kulhadia
51+
- loewenstein
52+
- makeavish
53+
- maliksalman
54+
- matejvasek
55+
- matthewmcnew
56+
- mgorsk1
57+
- mhdawson
58+
- mheath
59+
- modulo11
60+
- mstoodle
61+
- mterrel
62+
- mucsi96
63+
- musaffa
64+
- oceanicpanda
65+
- pacostas
66+
- pbusko
67+
- PerfectSlayer
68+
- peterjkirby
69+
- phil9909
70+
- pivotal-david-osullivan
71+
- pmbanugo
72+
- robdimsdale
73+
- ryanmoran
74+
- samj1912
75+
- SaschaSchwarze0
76+
- SchillingSebastian
77+
- scottfrederick
78+
- sdeleuze
79+
- semmet95
80+
- sgaist
81+
- sophiewigmore
82+
- sovereignstack
83+
- srisek
84+
- thitch97
85+
- ThomasVitale
86+
- TianMing2018
87+
- till
88+
- TisVictress
89+
- TomBeckett
90+
- ttys3
91+
- tuckeremulls
92+
- uqix
93+
- voor
94+
- xuan-nguyen-swe
95+
- zhoufenqin

elections/2023/TOC/README.md

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
# 2023 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+
This guide exists to serve as a guide to this year's election process.
14+
15+
16+
## Schedule
17+
18+
- **May 18**: Election is announced and candidate nomination period begins
19+
- **June 1, 5:00 pm PDT**: Candidate nomination period ends
20+
- **June 1, 11:59 pm PDT**: Election begins
21+
- **June 16, 11:59 pm PDT**: Election ends
22+
- **June 20**: Announcement of results
23+
24+
25+
## Candidate Processes
26+
27+
28+
### Nominations
29+
30+
31+
Every eligible voter can nominate candidates for the TOC, and we encourage you to do so. If you are
32+
eligible to serve on the TOC, you can self nominate! If you want to nominate someone else, do so as
33+
well!
34+
35+
36+
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).
37+
38+
39+
The deadline is June 1nd to be nominated (and for the nominee to indicate acceptance).
40+
41+
42+
It is strongly recommended that you confirm that a nominee is interested and willing
43+
to accept the nomination prior to submitting the nomination issue.
44+
45+
46+
### Confirming Nominee Eligibility
47+
48+
49+
Once a nomination is received, the CFF staff will contact the nominee to confirm acceptance
50+
of the nomination. If the nominee accepts, they will be added to the list of nominees at the bottom
51+
of this file. The nomination issue will be closed, noting if the nominee accepted or declined the
52+
nomination.
53+
54+
55+
## Voting Process
56+
57+
58+
The 2023 TOC election will be conducted using a [CFF-managed instance](https://elections.cloudfoundry.org) of [Elekto](https://elekto.dev), a CNCF infrastructure project
59+
that implements Condorcet ranked-choice voting using the Schulze method. Elekto relies on GitHub
60+
for user identity and authentication, which better matches how members interact with the Cloud
61+
Foundry community on a day-to-day basis than the email identity that the [Condorcet Internet Voting
62+
Service](https://civs1.civs.us/) requires.
63+
64+
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.
65+
66+
If Elekto fails to recognize you as eligible to vote in this election even though you believe you
67+
should be, please file a voting exception request [within the Elekto app](https://elections.cloudfoundry.org/app/elections/2023---TOC/exception) or [via an issue on the
68+
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).
69+
70+
Once the official election period starts, you will be able to rank the candidates in your preferred
71+
order and submit your ballot. You may set a password on your ballot, which is required to change
72+
your ballot later within the election period. Once the election period ends, all ballots are final.
73+
74+
All ballot data for Elekto is stored on a database managed by the CFF staff, and is not shared with
75+
third parties. Individual ballot data is encrypted, and ballot data can be retrieved only in
76+
aggregate form.
77+
78+
79+
## Election Results
80+
81+
82+
The newly elected body will be announced via [email protected] on 20 Jun, 2022.
83+
84+
85+
Following the announcement, the voting results and winners will be published.

elections/2023/TOC/election.yaml

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
name: 2023 CFF Technical Oversight Committee election
2+
organization: Cloud Foundry Foundation
3+
start_datetime: 2023-06-02 06:59:00 # 11:59 pm PDT, 01 Jun 2023
4+
end_datetime: 2023-06-17 06:59:00 # 11:59 pm PDT, 16 Jun 2023
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+
- christopherclark
14+
- ramiyengar
15+
- sgreenberg
16+
- AP-Hunt
17+
- beyhan
18+
- emalm
19+
- rkoster
20+
- stephanme
21+
eligibility: Members of the Cloud Foundry organization with 25 or more contributions in the last year may vote. 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.
22+
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.
23+
exception_due: 2023-06-14 06:59:00 # 11:59 pm PT, 13 Jun 2023

elections/2023/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/2023/TOC#readme).
2+
3+
## Eligibility
4+
5+
All contributors with 25 or more contributions to any Cloud Foundry Foundation project over the last year are 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/2023---TOC/exception) or via an issue on the community repository. The deadline for filing exceptions is June 13th, 11:59 pm PT.
6+
7+
## Schedule
8+
9+
May 18: Election is announced and candidate nomination period begins
10+
June 1, 5:00 pm PDT: Candidate nomination period ends
11+
June 1, 11:59 pm PDT: Election begins
12+
June 16, 11:59 pm PDT: Election ends
13+
June 20: 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 16th. 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)