2019 Steering Election retro fixes

[castrojo]

This is a first cut at landing fixes from the retro document: https://docs.google.com/document/d/1La9ZJPdvgLRzVH_RvE3Tmmx7uw_de8x8Ca4HoCkH8R0/edit

We'll need to address more but this will get a bunch of work out of the way for 2020.

/cc @bgrant0607 @mrbobbytables
/cc @kubernetes/steering-committee
/hold

[idvoretskyi]

/cc

[timothysc]

Minor nits otherwise LGTM
/approve

[nikhita]

Just some nits, but this is great! Thank you!

[bgrant0607]

Thanks!

Of the new docs, what was changed compared to 2019?

[mrbobbytables]

@bgrant0607 Looks like for the 2020 README, it's mostly cleaning up some language, changing dates, and adding a note with a link to the doc regarding maximal representation.

diff --git a/README.md b/2020.md
index 6e3f4004..cd635dcb 100644
--- a/README.md
+++ b/2020.md
@@ -1,24 +1,25 @@
-# 2019 VOTERS GUIDE - KUBERNETES STEERING COMMITTEE ELECTION
+# 2020 VOTERS GUIDE - KUBERNETES STEERING COMMITTEE ELECTION

 ## Purpose

-The role of this election is to fill out the four (4) seats due for
+The role of this election is to fill the three (3) seats due for
 reelection this year on the [Kubernetes Steering Committee]. Each elected
 member will serve a two (2) year term.

 ## Background

-This election will shape the future of Kubernetes as a community and project.
-While SIGs and WGs help shape the technical direction of the project, the
-[Steering Committee Charter] covers the health of the project and community
-as a whole. Some direct responsibilities of steering members to consider as you are deciding
-whether to run or who to vote for:
+This election will help shape the future governance policies for the Kubernetes
+community and project. While SIGs and WGs help shape the technical direction of
+the project, the [Steering Committee Charter] covers the health of the project
+and community as a whole. Some direct responsibilities of steering members to
+consider as you are deciding whether to run or who to vote for:

 * Through the chartering review process, delegate ownership of, responsibility
   for and authority over areas of the project to specific entities
 * Define, evolve, and defend the non-technical vision / mission and the values
   of the project
-* Charter and refine policy for defining new community groups and establish transparency and accountability policies for such groups
+* Charter and refine policy for defining new community groups and establish
+  transparency and accountability policies for such groups
 * Define and evolve project and group governance
   structures and policies
 * Act as a final non-technical escalation point for any Kubernetes repository
@@ -36,15 +37,21 @@ Please refer to the [Steering Committee Election Charter] for:
 - [Eligibility for candidacy]
 - [Eligibility for voting] and [Eligible voters] list (not in charter)

+Maximal representation as [defined by
+steering](https://github.com/kubernetes/steering/blob/master/elections.md) will
+be applied after the election results are tallied.
+
 ### Schedule

 | Date         | Event                    |
 | ------------ | ------------------------ |
-| August 21    | Announcement of Election |
-| September 11 | All candidate bios and voting exception forms due by 0000 UTC (5pm PST) |
-| September 18 | Election Begins via email ballots |
-| October 2    | Election Closes by 0000 UTC (5pm PST) |
-| October 3    | Announcement of Results at Community Meeting |
+| August XX    | Announcement of Election |
+| August XX    | Steering Committee Meeting with Candidates and Community Q&A |
+| September XX | All candidate bios and voting exception forms due by 0000 UTC (5pm PST) |
+| September XX | ~1w of election prep |
+| September XX | Election Begins via email ballots |
+| October XX   | Election Closes by 0000 UTC (5pm PST) |
+| October XX   | Announcement of Results at Community Meeting |

 ## Candidacy Process

@@ -65,16 +72,17 @@ Once nominated, you must get the endorsement of three (3) different eligible
 voters from three (3) different employers.  If you are eligible to vote
 yourself, you count as one of the three.

-[Eligible voters] may endorse candidates of their choosing by replying to the
-candidate's nomination email saying something like "I endorse this nominee"
-or "+1". Please specify your github ID and state that you are in voters.md.
+Only [eligible voters] may endorse candidates of their choosing by replying to the
+candidate's nomination email saying something like "I endorse this nominee" or
+"+1". Please specify your github ID and state that you are in voters.md. +1's
+and other endorsements from anyone not in voters.md are considered non-binding.

 **Running**

-Eligible candidates must submit a pull request with a biography in this
+Eligible candidates should 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`.
-Please refer to the [2018 candidate bios] for examples.
+Please refer to the [2019 candidate bios] for examples.

 **Campaigning**

@@ -104,28 +112,25 @@ 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 the morning September 28, 2019 via email and
-end two weeks after on October 2, 2019 at 00:00am UTC. You will receive an email
+The election will open for voting the morning September XX, via email and
+end two weeks after on October XX. 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 whitelist if necessary. 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 29.
+the election officials if you do not receive a ballot by September XX.

 ### Officers

 The Steering Committee has selected the following people as [election officers]:
-- Ihor Dvoretskyi, @idvoretskyi, CNCF
-- Jorge Castro, @castrojo, VMware
-- Bob Killen, @mrbobbytables, University of Michigan
-- Brian Grant, @bgrant0607, Google
+- Jane Containerface, @github, affiliation

 Please direct any questions via email to <election@k8s.io>.

 ### Decision

 The newly elected body will be announced in the weekly [Kubernetes Community Meeting]
-on October 3, 2019.
+on XXX.

 Following the meeting, the raw voting results and winners will be published on the
 [Kubernetes Blog].
@@ -137,17 +142,7 @@ the [Steering Committee Election Charter]

 |                    Name                    | Organization/Company |                        GitHub                        |
 |:------------------------------------------:|:--------------------:|:----------------------------------------------------:|
-| [Brendan Burns](./brendanburns.md)         |       Microsoft      | [@brendandburns](https://github.com/brendandburns)   |
-| [Christoph Blecker](./christophblecker.md) |        Red Hat       | [@cblecker](https://github.com/cblecker)             |
-| [Derek Carr](./derekcarr.md)               |        Red Hat       | [@derekwaynecarr](https://github.com/derekwaynecarr) |
-| [Pengfei Ni](./pengfeini.md)               |       Microsoft      | [@feiskyer](https://github.com/feiskyer)             |
-| [Stephen Augustus](./stephenaugustus.md)   |        VMware        | [@justaugustus](https://github.com/justaugustus)     |
-| [Kris Nova](./krisnova.md)                 |        Sysdig        | [@kris-nova](https://github.com/kris-nova)           |
-| [Klaus Ma](./klausma.md)                   |        Huawei        | [@k82cn](https://github.com/k82cn)                   |
-| [Lachlan Evenson](./lachlanevenson.md)     |       Microsoft      | [@lachie83](https://github.com/lachie83)             |
-| [Nikhita Raghunath](./nikhitaraghunath.md) |        Loodse        | [@nikhita](https://github.com/nikhita)               |
-| [Paris Pittman](./parispittman.md)         |        Google        | [@parispittman](https://github.com/parispittman)     |
-| [Vallery Lancey](./vallerylancey.md)       |         Lyft         | [@vllry](https://github.com/vllry)                   |
+| [Candidate Name](./yourname.md)            |       Foocorp        | [@github](https://github.com/yourname)               |

 [Kubernetes Steering Committee]: https://github.com/kubernetes/steering
 [Steering Committee Charter]: https://github.com/kubernetes/steering/blob/master/charter.md
@@ -155,6 +150,7 @@ the [Steering Committee Election Charter]
 [governance meeting video]: https://www.youtube.com/watch?v=ltRKXLl0RaE&list=PL69nYSiGNLP1pkHsbPjzAewvMgGUpkCnJ&index=23

 [Steering Committee Election Charter]: https://git.k8s.io/steering/elections.md
+[defined by steering]: https://git.k8s.io/steering/elections.md#maximal-representation
 [Eligibility for voting]: https://github.com/kubernetes/steering/blob/master/elections.md#eligibility-for-voting
 [Eligibility for candidacy]: https://github.com/kubernetes/steering/blob/master/elections.md#eligibility-for-candidacy
 [limiting corporate campaigning]: https://github.com/kubernetes/steering/blob/master/elections.md#limiting-corporate-campaigning
@@ -164,7 +160,7 @@ the [Steering Committee Election Charter]
 [CIVS]: http://civs.cs.cornell.edu/
 [IRV method]: https://www.daneckam.com/?p=374

-[2018 candidate bios]: https://github.com/kubernetes/community/tree/master/events/elections/2018
+[2019 candidate bios]: https://github.com/kubernetes/community/tree/master/events/elections/2019
 [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/

[mrbobbytables]

Not a blocker, but we should add a release style timeline table. Example: 1.17 Timeline. Essentially a list of tasks or milestones by week 0, week 1.

I created a tracking issue with something similar for this past election: #4118

[bgrant0607]

It took a couple days for all of the ballots to go out. Maybe we should say to estimate 2-3 minutes per voter, if CIVS is used again.

[castrojo]

I left this in as boilerplate, I have an item to talk to the GitHub folks during the contributor summit on figuring out if there's a way we can do an election using github primitives instead of email.

[bgrant0607]

BTW, the diff was very helpful @mrbobbytables. Thanks.

[bgrant0607]

Merge and iterate.
/lgtm
/approve
/hold cancel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bgrant0607, castrojo, timothysc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• events/OWNERS [castrojo,timothysc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[castrojo]

Ok last push to address some concerns, this should be it for 2k19.

[castrojo]

/test pull-community-verify

[mrbobbytables]

/lgtm