Merge pull request #3991 from castrojo/start-voter-guide

Add initial guide for 2019 election

3 files changed, 178 insertions, 1 deletions

diff --git a/events/elections/2019/OWNERS b/events/elections/2019/OWNERS
new file mode 100644
index 00000000..acb3b36e
--- /dev/null
+++ b/events/elections/2019/OWNERS
@@ -0,0 +1,12 @@
+# See the OWNERS docs at https://go.k8s.io/owners
+
+reviewers:
+  - castrojo
+  - idvoretskyi
+  - mrbobbytables
+  - bgrant0607
+approvers:
+  - castrojo
+  - idvoretskyi
+  - mrbobbytables
+  - bgrant0607
diff --git a/events/elections/2019/README.md b/events/elections/2019/README.md
new file mode 100644
index 00000000..73d9eaed
--- /dev/null
+++ b/events/elections/2019/README.md
@@ -0,0 +1,164 @@
+# 2019 VOTERS GUIDE - KUBERNETES STEERING COMMITTEE ELECTION
+
+## Purpose
+
+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.
+
+## 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:
+
+* 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
+* Define and evolve project and group governance
+  structures and policies
+* Act as a final non-technical escalation point for any Kubernetes repository
+* Request funds and other support from the CNCF (e.g. marketing, press, etc.)
+* Define and enforce requirements for community groups to be in good standing 
+  such as having an approved charter
+
+For more context, please see the [current steering committee backlog] or a
+previous [governance meeting video] which led to this whole process.
+
+## Eligibility
+
+Please refer to the [Steering Committee Election Charter] for:
+
+- [Eligibility for candidacy]
+- [Eligibility for voting] and [Eligible voters] list (not in charter)
+
+### 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 |
+
+## Candidacy Process
+
+**Nomination**
+
+If you want to stand for election, send an email to kubernetes-dev@googlegroups.com
+with the subject line "Steering Committee Nomination: Your Name (@yourgithub)".
+
+If you want to nominate someone else, you may do so, but PLEASE talk to them
+first.
+
+If you wish to accept a nomination from someone else, reply to the nomination
+email saying something like "I accept the nomination"
+
+**Endorsement**
+
+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".
+
+**Running**
+
+Eligible candidates must 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.
+
+**Campaigning**
+
+Please refer to the [Steering Committee Election Charter] and understand
+that we care deeply about [limiting corporate campaigning]. The election
+officers and members of the steering committee [pledge to recuse] themselves
+from any form of electioneering.
+
+You should be running as a "brand free" individual, based on your contribution
+to the project as a member of this community, outside of whatever corporate
+roles you may hold.
+
+## Voting Process
+
+Kubernetes members in [voters.md] 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 exemption form] 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.
+
+Employer diversity is encouraged, and thus maximal representation will be
+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
+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. 
+
+### 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
+
+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.
+
+Following the meeting, the raw voting results and winners will be published on the
+[Kubernetes Blog]. 
+
+For more information, definitions, and/or detailed election process, please refer to
+the [Steering Committee Election Charter]
+
+## Nominees
+
+Name | Organization/Company | GitHub
+--- | --- | -- |
+| [Example Candidate](example.md) | YourCompany | Link to Github | 
+
+
+[Kubernetes Steering Committee]: https://github.com/kubernetes/steering
+[Steering Committee Charter]: https://github.com/kubernetes/steering/blob/master/charter.md
+[current steering committee backlog]: https://github.com/kubernetes/steering/projects/1
+[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
+[Eligibility for voting]: https://github.com/kubernetes/steering/blob/master/elections.md#elegibility-for-voting
+[Eligibility for candidacy]: https://github.com/kubernetes/steering/blob/master/elections.md#elegibility-for-candidacy
+[limiting corporate campaigning]: https://github.com/kubernetes/steering/blob/master/elections.md#limiting-corporate-campaigning
+[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
+
+[2018 candidate bios]: https://github.com/kubernetes/community/tree/master/events/elections/2018
+[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]: https://github.com/kubernetes/community/blob/master/events/elections/2019/voters.md
+[voter exemption form]: https://www.surveymonkey.com/r/k8s-sc-election-2019
+[voters.md]: ./voters.md
\ No newline at end of file
diff --git a/events/elections/README.md b/events/elections/README.md
index f3ad473a..8905e7c2 100644
--- a/events/elections/README.md
+++ b/events/elections/README.md
@@ -32,6 +32,7 @@ eligibility for voting, eligibility for candidacy, maximal representation, etc.
    - Make github.com/kubernetes/community/elections/$YEAR/README.md, this is the voter’s guide.
      - Copy over the voter’s guide from the previous year. The voter’s guide is the single source of truth for the election that year! All announcements and notices should link to this document.
      - Update with new dates, candidates, and procedures (if necessary).
+   - Make github.com/kubernetes/community/elections/$YEAR/OWNERS with all the election officers for the election year.
    - Make github.com/kubernetes/community/elections/$YEAR/voters.md
      - Initial list is generated via the [eligibilty for voting requirements][eligibile to vote]
      - Officers will update this list as voters submit the voting exemption form.
@@ -79,7 +80,7 @@ eligibility for voting, eligibility for candidacy, maximal representation, etc.
 
 - Must be [eligible to vote][eligible to vote]
 - Cannot be running for office in the current election
-- Cannot be a current member of the steering committee
+- Cannot be a current member of the steering committee that is a candidate in the election or whose term extends beyond the election period
 - [Recuse themselves from public election activities][election-recusal] except those required to run the election
   - May vote
   - May answer questions about general election specifics, ie: