Update community repo for the 2021 elections.

Heavy revisions due to changes brought about by Elekto.

Minor changes per comments.

Signed-off-by: Josh Berkus <josh@agliodbs.com>

7 files changed, 133 insertions, 83 deletions

diff --git a/events/elections/2021/OWNERS b/events/elections/2021/OWNERS
index bcc0f241..397e30b5 100644
--- a/events/elections/2021/OWNERS
+++ b/events/elections/2021/OWNERS
@@ -3,5 +3,9 @@
 # replace with election officers once election starts
 approvers:
   - committee-steering
+  - alisondy
+  - ameukam
+  - jberkus
+  - coderanger
 labels:
   - committee/steering
diff --git a/events/elections/2021/README.md b/events/elections/2021/README.md
index 26b03356..926df029 100644
--- a/events/elections/2021/README.md
+++ b/events/elections/2021/README.md
@@ -6,6 +6,17 @@ The role of this election is to fill out the four (4) seats due for
 reelection this year on the [Kubernetes Steering Committee]. Each elected
 member will serve a two (2) year term.
 
+## Changes
+
+This year is the first year we will be using [Elekto] to conduct the election.
+Elekto is a new application, commissioned as an internship by the CNCF.  As
+well as having a new, shiny web UI, it relies entirely on GitHub Oauth for
+voting, and as such does not use email at all.  Elekto also handles exceptions,
+eligibility checks, and other aspects of the election.
+
+This does mean some changes to the nomination, running, and voter exception
+process, so please read below.
+
 ## Background
 
 This election will shape the future of Kubernetes as a community and project.
@@ -37,7 +48,7 @@ Please refer to the [Steering Committee Election Charter] for [Eligibility for c
 Eligibility for voting in 2021 is defined as:
 
 * People who had at least 50 contributions to the Kubernetes project over
-  the past year, according to a snapshot taken 2021-MM-DD of the data driving
+  the past year, according to a snapshot taken 2021-09-15 of the data driving
   the [devstats developer activity counts dashboard][devstats-dashboard],
   who are also [Org Members].
   Contributions include GitHub events like creating issues, creating PRs,
@@ -90,18 +101,17 @@ Examples of contributions that would NOT be considered:
 
 | Date         | Event                    |
 | ------------ | ------------------------ |
-| July 1       | Steering Committee selects Election Committee |
-| August XX    | Announcement of Election and publication of voters.md |
-| August XX    | Steering Committee Meeting with Q+A with the candidates and community |
-| September XX | All candidate bios due by 0000 UTC (5pm PST) |
-| ~1 week      | Election prep week (voters.md validation and CIVS setup and testing)
-| September XX | Election Begins via email ballots |
-| October XX   | Deadline to submit voter exception forms and request a replacement ballot |
-| October XX   | Election Closes by 0000 UTC (5pm PST) |
-| October XX   | Private announcement of Results to SC members not up for election |
-| October XX   | Private announcement of Results to all candidates |
-| October XX   | Public announcement of Results at Public Steering Committee Meeting |
-| October XX   | Election Retro |
+| August 19    | Steering Committee selects Election Committee |
+| September 21 | Announcement of Election and publication of voters.md |
+| September XX | Steering Committee Meeting with Q+A with the candidates and community |
+| October 6    | All candidate bios due by 0000 UTC (5pm PST) |
+| October 8    | Election Begins via email ballots |
+| October 24   | Deadline to submit voter exception forms and request a replacement ballot |
+| October 27   | Election Closes by 0000 UTC (5pm PST) |
+| October 28   | Private announcement of Results to SC members not up for election |
+| October 30   | Private announcement of Results to all candidates |
+| November 1   | Public announcement of Results at Public Steering Committee Meeting |
+| November 4?   | Election Retro |
 
 ## Candidacy Process
 
@@ -127,8 +137,12 @@ nomination on GitHub, as +1s via email will not count. Here's an example email:
 **issue** saying something like "I accept the nomination".
 
 4. Finally, the candidate closes the **issue** (`#NNN`) by opening a Pull Request
-to add their bio. The PR body must contain the text `Fixes #NNN` to automatically
-close the issue once the PR is merged.
+to add their bio (see below). The PR body must contain the text `Fixes #NNN` to 
+automatically close the issue once the PR is merged.
+
+5. Create the PR for your bio by copying the `nomination-template.md` file in
+this directory, and creating a new file titled `candidate-YourName.md`.  Fill 
+out all the fields in the template, but avoid making and format changes.
 
 **Endorsement**
 
@@ -152,14 +166,19 @@ Election Officers will announce that on the GitHub issue.
 **Running**
 
 Eligible candidates can submit a pull request with a biography in this
-directory with their platform and intent to run. This statement is
-**limited to 300 words** and must follow the format of `firstnamelastname.md`.
-The word limit applies to the source markdown file and the [`hack/verify-steering-election.sh`]
-script can be used to check the word count.
+directory with their platform and intent to run. This PR will copy `nomination-template.md`
+to a file named `candidate-YourName.md`.  It will fill out the fields in
+that template.
+
+All biographical statements should be brief and to the point, with a guideline of around 
+**300 words** total for all text. If your statement is excessively long, you 
+will be asked to abbreviate it before it is merged.
 
-Please refer to the [2020 candidate bios] for examples. Biography statements are optional.
+Please refer to the [2020 candidate bios] for examples of content, although
+the formatting should support the new templates. Biography statements are optional.
 
-Missed deadlines by the candidates will be addressed by steering on a per case basis to determine eligibility.
+Missed deadlines by the candidates will be addressed by the election committee
+on a per case basis to determine eligibility.
 
 **Campaigning**
 
@@ -174,14 +193,16 @@ roles you may hold.
 
 ## Voting Process
 
-Eligible voters will receive a ballot via email. If you are
-not on that list and feel you have worked on Kubernetes in a way that is NOT
-reflected in GitHub contributions, you can use the [voter exception form] to ask
-to participate in the election.
+Contributors may check their voter eligibility at any time once the election
+process starts, by going to the [election app], logging in, navigating to
+the 2021 election, and seeing if the screen there says that they are eligible.
+
+If the app does not say that you are eligible, because you have worked on 
+Kubernetes in a way that is NOT reflected in GitHub contributions, you can use 
+the exception form built into the same app to ask to participate in the election.
 
-Elections will be held using time-limited [Condorcet] ranking on [CIVS]
-using the [IRV method]. The top vote getters will be elected to the open
-seats.
+Elections will be held using time-limited [Condorcet] ranking on [Elekto]. 
+The most preferred candidates will be elected to the open seats.
 
 Employer diversity is encouraged, and thus maximal representation will be
 enforced as spelled out in the [Steering Committee Election Charter].
@@ -189,21 +210,19 @@ enforced as spelled out in the [Steering Committee Election Charter].
 You will be ranking your choices of the candidates with an option for
 "no opinion". In the event of a tie, a coin will be flipped.
 
-The election will open for voting starting September XX via email and
-end three weeks after on October XX, 2021 at 00:00am UTC. You will receive
-an email to the address on file at the start of the election from "Kubernetes
-(CIVS Poll Supervisor) `<civs@cs.cornell.edu>`, please add to the list of addresses
-you don't spam filter. Detailed voting instructions will be addressed in email
-and the CIVS polling page. Please note that email ballots might be unreliable,
-so you are encouraged to contact the election officials if you do not receive a
-ballot by September XX.
-
-If you do not receive your ballot, request a new one via the [Ballot Replacement Form].
+The election will open for voting starting on the dates specified on the calendar
+at the top of this document. You will be reminded that voting has opened by an
+email to kubernetes-dev, but no email is required for you to vote.
 
 ### Officers
 
 The Steering Committee has selected the following people as [election officers]:
-- Name, GitHub handle, Affiliation
+
+- Alison Dowdney, @alisondy
+- Josh Berkus, @jberkus
+- Noah Kantrowitz, @coderanger
+
+In addition, Arnaud M is serving as our Infra Team liaison for this election.
 
 Please direct any questions via email to <election@k8s.io>.
 
@@ -212,8 +231,8 @@ Please direct any questions via email to <election@k8s.io>.
 - First, the results are privately announced to the incumbent Steering Committee
 members (who are not up for election) and all the candidates.
 
-- The newly elected body will be publicly announced in the monthly
-[public Steering Committee Meeting] on October XX, 2021.
+- The newly elected body will be publicly announced in the scheduled monthly
+[public Steering Committee Meeting].
 
 - Following the meeting, the raw voting results and winners will be published on the
 [Kubernetes Blog].
@@ -223,13 +242,7 @@ the [Steering Committee Election Charter]
 
 ## Nominees
 
-The nominee list is filled in by the Election Officers after all bios have been
-submitted. Please do not edit the following table.
-
-
-|                    Name                    | Organization/Company |                        GitHub                        |
-|:------------------------------------------:|:--------------------:|:----------------------------------------------------:|
-| [Jane Containerface](./biotemplate.md)     |      ExampleCo       | [@github](https://github.com)                        |
+Nominees may be found in the [election app].
 
 [Kubernetes Steering Committee]: https://github.com/kubernetes/steering
 [Steering Committee Charter]: https://github.com/kubernetes/steering/blob/master/charter.md
@@ -243,19 +256,13 @@ submitted. Please do not edit the following table.
 [pledge to recuse]: https://github.com/kubernetes/steering/blob/master/elections.md#steering-committee-and-election-officer-recusal
 
 [Condorcet]: https://en.wikipedia.org/wiki/Condorcet_method
-[CIVS]: http://civs.cs.cornell.edu/
-[IRV method]: https://www.daneckam.com/?p=374
-
-[`hack/verify-steering-election.sh`]: https://git.k8s.io/community/hack/verify-steering-election.sh
 [2020 candidate bios]: https://github.com/kubernetes/community/tree/master/events/elections/2020
 [election officers]: https://github.com/kubernetes/community/tree/master/events/elections#election-officers
 [Kubernetes Community Meeting]: https://github.com/kubernetes/community/blob/master/events/community-meeting.md
 [Kubernetes Blog]: https://kubernetes.io/blog/
-[eligible voters]: ./voters.md
-[voter exception form]: https://www.surveymonkey.com/r/k8s-sc-election-2021
-[voters.md]: ./voters.md
 
 [devstats-sql]: https://github.com/cncf/devstats/blob/master/metrics/shared/project_developer_stats.sql
 [devstats-dashboard]: https://k8s.devstats.cncf.io/d/13/developer-activity-counts-by-repository-group?orgId=1&var-period_name=Last%20year&var-metric=contributions&var-repogroup_name=All
 [Org Members]: https://github.com/kubernetes/community/blob/master/community-membership.md
-[Ballot Replacement Form]: https://www.surveymonkey.com/r/kubernetes-sc-2021-ballot
+[Elekto]: https://elekto.dev
+[election app]: https://election.k8s.io
diff --git a/events/elections/2021/biotemplate.md b/events/elections/2021/biotemplate.md
deleted file mode 100644
index ac734856..00000000
--- a/events/elections/2021/biotemplate.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# Your Name
-
-- GitHub: https://github.com/
-- Affiliation: Where you work or independent
-- Slack: @you
-- Twitter/Other: Add lines as appropriate
-
-## SIGS
-
-- SIGS/WG/UGs you're a member of
-
-## What I have done
-
-## What I'll do
-
-## Resources About Me
-
-- Links to KubeCon or other conference talks or other related material 
diff --git a/events/elections/2021/election.yaml b/events/elections/2021/election.yaml
new file mode 100644
index 00000000..36e79b58
--- /dev/null
+++ b/events/elections/2021/election.yaml
@@ -0,0 +1,17 @@
+name: 2021 Steering Committee Election
+organization: Kubernetes
+start_datetime: 2021-10-07 00:00:01
+end_datetime: 2021-10-28 23:59:00
+no_winners: 4
+allow_no_opinion: True
+delete_after: True
+show_candidate_fields:
+  - employer
+  - slack
+election_officers:
+  - jberkus
+  - alisondy
+  - coderanger
+eligibility: Kubernetes Org members with 50 or more contributions in the last year can vote.  See [the election guide](https://github.com/kubernetes/community/tree/master/events/elections/2021)
+exception_description: Not all contributions are measured by DevStats.  If you have contributions that are not so measured, then please request an exception to allow you to vote via the Elekto application.
+exception_due: 2021-10-24 10:00:00
diff --git a/events/elections/2021/election_desc.md b/events/elections/2021/election_desc.md
new file mode 100644
index 00000000..14eadf6c
--- /dev/null
+++ b/events/elections/2021/election_desc.md
@@ -0,0 +1,13 @@
+# Vote for the 2021-2022 Steering Committee
+
+As is now customary, this fall is [Steering Committee](https://github.com/kubernetes/steering) election season for Kubernetes. Three(3) elected members (bobkillen, dims, liggitt) will stay on for the remaining year of their terms, and there will be four(4) positions open for election. Every election term will be 2 years. More complete information on the election may be found [in the voter's guide](https://github.com/kubernetes/community/tree/master/events/elections/2021).
+
+If you’d like to vote or run for a seat, all details and next steps are outlined in the [election process doc](https://git.k8s.io/steering/elections.md) and this application. The application will be the single source of truth of information for this cycle. It will be updated live as new bios of candidates get committed. Please pay attention to the scheduled dates:
+
+| Start Date | End Date | Activity |
+| ---------- | -------- | -----------------|
+| 2021-09-21 | 2021-10-07 | Nominate Candidates |
+| 2021-09-21 | 2021-10-24 | Request voter exceptions |
+| 2021-10-09 | 2021-10-27 | Vote |
+
+As mentioned in the process doc, eligibility for voting will be determined by 50 contributions to a Kubernetes project over the past year and [Kubernetes Org membership](https://github.com/kubernetes/community/blob/master/community-membership.md).  Eligible voters will be shown as such by this site when logged in.  If you should be eligible, but are not, you may also file for an exception on this site.
diff --git a/events/elections/2021/nomination-template.md b/events/elections/2021/nomination-template.md
new file mode 100644
index 00000000..e3de4cf7
--- /dev/null
+++ b/events/elections/2021/nomination-template.md
@@ -0,0 +1,23 @@
+-------------------------------------------------------------
+name: 
+ID: @GitHubID
+info:
+  - employer: Your Employer or "Independent"
+  - slack: slack handle
+-------------------------------------------------------------
+
+<!-- Please make a copy of this template as "candidate-yourname.md" and save it to
+the election directory -->
+
+## SIGS
+
+- SIGS/WG/UGs you're a member of
+
+## What I have done
+
+## What I'll do
+
+## Resources About Me
+
+- Links to KubeCon or other conference talks or other related material 
+- Links to social media
diff --git a/events/elections/2021/templates/election-templates.md b/events/elections/2021/templates/election-templates.md
index 67a642ac..9e4f33ca 100644
--- a/events/elections/2021/templates/election-templates.md
+++ b/events/elections/2021/templates/election-templates.md
@@ -4,31 +4,35 @@ Adjust this template as necessary:
 
 It’s that time of year again!
 
-As is now customary, this fall is election season for Kubernetes. Three(3) elected members (bobkillen, dims, liggitt) will stay on for the remaining year of their terms, and there will be four(4) positions open for election. Every election term will be 2 years. We will be posting regular updates to kubernetes-dev with deadlines and instructions as well as providing quick updates during the regular Thursday community meetings until completion of the election.
+It's also new!  This is the first year we will be using Elekto[0] for the Kubernetes Steering elections.  Elekto was commissioned as an internship project for us by the CNCF.  You'll find it has a much more modern UI, and does not rely on email at all to enable voting.
 
-If you’d like to vote or run for a seat, all details and next steps are outlined in the election process doc[3] and voters guide.[4] The voters guide will be the single source of truth of information for this cycle. It will be updated live as new bios of candidates flow through over the next four weeks. Please pay attention to the scheduled dates:
+As is now customary, this fall is election season for Kubernetes. Three(3) elected members (bobkillen, dims, liggitt) will stay on for the remaining year of their terms, and there will be four(4) positions open for election. Every election term will be 2 years. We will be posting regular updates to kubernetes-dev with deadlines and instructions as well as providing quick updates during the regular Thursday community meetings until completion of the election.
 
-| schedule here |
+If you’d like to vote or run for a seat, all details and next steps are outlined in the election process doc[3] and the Elekto application[7]. The application will be the single source of truth of information for this cycle. It will be updated live as new bios of candidates flow through. Please pay attention to the scheduled dates:
 
-As mentioned in the process doc, eligibility for voting will be determined by 50 contributions to a Kubernetes project over the past year and Kubernetes Org membership[5], which will result in you getting a ballot emailed to you when the election starts. All contributors who will receive a ballot are listed in voters.md[6]; if your name is not there, you will need an exception to vote.
+| Start Date | End Date | Activity |
+| ---------- | -------- | -----------------|
+| 2021-09-21 | 2021-10-07 | Nominate Candidates |
+| 2021-09-21 | 2021-10-24 | Request voter exceptions |
+| 2021-10-09 | 2021-10-28 | Vote |
 
-For those of you doing work within the Kubernetes project/community that is NOT measured in GitHub, or if you have 50 contributions but not Org Membership, you can apply for participation via the voter exception form[7]. This is to ensure that non-code contributors can participate, so please don’t hesitate to use the form.
+As mentioned in the process doc, eligibility for voting will be determined by 50 contributions to a Kubernetes project over the past year and Kubernetes Org membership[5].  Eligible voters will be shown as such when by the Elekto application[7].  If you should be eligible, but are not, you may also file for an exception through the same application. For those of you doing work within the Kubernetes project/community that is NOT measured in GitHub, or if you have 50 contributions but not Org Membership, you can apply for participation via the voter exception form[7] in the Elekto app. This is to ensure that non-code contributors can participate, so please don’t hesitate to use the form.
 
 Resources:
 
 
+[0] Elekto: https://elekto.dev
 [1] Steering Committee:  https://github.com/kubernetes/steering - who sits on the committee and terms, their projects and meeting info
 [2] Steering Committee Charter: https://github.com/kubernetes/steering/blob/master/charter.md  - this is a great read if you’re interested in running (or assessing for the best candidates!)
 [3] Election Process: https://git.k8s.io/steering/elections.md 
-[4] Voters Guide: https://github.com/kubernetes/community/tree/master/events/elections/2021 - Updated on a rolling basis. This guide will always have the latest information throughout the election cycle. The complete schedule of events and candidate bios will be housed here.
+[4] Voters Guide: https://elections.k8s.io - Updated on a rolling basis. This guide will always have the latest information throughout the election cycle. The complete schedule of events and candidate bios will be housed here.
 [5] Contributor Ladder: https://github.com/kubernetes/community/blob/master/community-membership.md -  explains Org Membership as well as all of the higher levels
-[6] Voters.md: https://github.com/kubernetes/community/blob/master/events/elections/2021/voters.md -  list of contributors who will automatically receive a ballot
-[7] exception Form: https://www.surveymonkey.com/r/k8s-sc-election-2021
+[7] Elekto Application: https://elections.k8s.io
 
 
 On behalf of the election officers,
 
-Name (github), Name (github), etc
+Alison Dowdney (@alisondy), Josh Berkus (@jberkus), Noah Kantrowitz (@coderanger)
 
 If you have questions, please feel free to ask on the list; otherwise, you can reach the Election Officials at election@kubernetes.io.