@@ -128,19 +128,19 @@ Examples of contributions that would NOT be considered:
128
128
public announcement is a weekend.
129
129
-->
130
130
131
- | Date | Event |
132
- | :--------| :----------------------------------------------------------------------|
133
- | July 22 | Steering Committee selects Election Committee |
134
- | | Announcement of Election and publication of voters.md |
135
- | | Steering Committee Meeting with Q+A with the candidates and community |
136
- | | All candidate bios due by 0000 UTC (5pm PST) |
137
- | | Election Begins via email ballots |
138
- | | Deadline to submit voter exception requests |
139
- | | Election Closes by 0000 UTC (5pm PST) |
140
- | | Private announcement of Results to SC members not up for election |
141
- | | Private announcement of Results to all candidates |
142
- | | Public announcement of Results at Public Steering Committee Meeting |
143
- | | Election Retro |
131
+ | Date | Event |
132
+ | :------------------------ | :----------------------------------------------------------------------|
133
+ | Friday, July 22 | Steering Committee selects Election Committee |
134
+ | Monday, August 15 | Announcement of Election and publication of voters.md |
135
+ | ???, August ?? | Steering Committee Meeting with Q+A with the candidates and community |
136
+ | Friday, September 2 | All candidate bios due by 0000 UTC (5pm PST) |
137
+ | Tuesday, September 6 | Election Begins via email ballots |
138
+ | Friday, September 16 | Deadline to submit voter exception requests |
139
+ | Sunday, September 25 | Election Closes by 0000 UTC (5pm PST) |
140
+ | Monday, September 26 | Private announcement of Results to SC members not up for election |
141
+ | Wednesday, September 28 | Private announcement of Results to all candidates |
142
+ | Thursday, September 29 | Public announcement of Results at Public Steering Committee Meeting |
143
+ | Tuesday, October 4 ??? | Election Retro |
144
144
145
145
## Candidacy Process
146
146
@@ -166,11 +166,11 @@ nomination on GitHub, as +1s via email will not count. Here's an example email:
166
166
** issue** saying something like "I accept the nomination".
167
167
168
168
4 . Finally, the candidate closes the ** issue** (` #NNN ` ) by opening a Pull Request
169
- to add their bio (see below). The PR body must contain the text ` Fixes #NNN ` to
169
+ to add their bio (see below). The PR body must contain the text ` Fixes #NNN ` to
170
170
automatically close the issue once the PR is merged.
171
171
172
172
5 . Create the PR for your bio by copying the ` nomination-template.md ` file in
173
- this directory, and creating a new file titled ` candidate-githubid.md ` . Fill
173
+ this directory, and creating a new file titled ` candidate-githubid.md ` . Fill
174
174
out all the fields in the template, but avoid making and format changes.
175
175
176
176
** Endorsement**
@@ -199,8 +199,8 @@ directory with their platform and intent to run. This PR will copy `nomination-t
199
199
to a file named ` candidate-YourName.md ` . It will fill out the fields in
200
200
that template.
201
201
202
- All biographical statements should be brief and to the point, with a guideline of around
203
- ** 300 words** total for all text. If your statement is excessively long, you
202
+ All biographical statements should be brief and to the point, with a guideline of around
203
+ ** 300 words** total for all text. If your statement is excessively long, you
204
204
will be asked to abbreviate it before it is merged.
205
205
206
206
Please refer to the [ 2021 candidate bios] for examples of content.
@@ -227,11 +227,11 @@ process starts, by going to the [election app], logging in, navigating to
227
227
the 2022 election, and seeing if the screen there says that they are eligible.
228
228
That screen takes its data from the [ voters.yaml] file.
229
229
230
- If the app does not say that you are eligible, because you have worked on
231
- Kubernetes in a way that is NOT reflected in GitHub contributions, you can use
230
+ If the app does not say that you are eligible, because you have worked on
231
+ Kubernetes in a way that is NOT reflected in GitHub contributions, you can use
232
232
the exception form built into the same app to ask to participate in the election.
233
233
234
- Elections will be held using time-limited [ Condorcet] ranking on [ Elekto] .
234
+ Elections will be held using time-limited [ Condorcet] ranking on [ Elekto] .
235
235
The most preferred candidates will be elected to the open seats.
236
236
237
237
Employer diversity is encouraged, and thus maximal representation will be
0 commit comments