From 6e63f0760b7ef7b956ad1cde6919f9d72c4aa4cb Mon Sep 17 00:00:00 2001 From: "Jorge O. Castro" Date: Tue, 14 Aug 2018 08:38:02 -0400 Subject: Reset for 2018 --- events/elections/2018/README.md | 65 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 65 insertions(+) create mode 100644 events/elections/2018/README.md diff --git a/events/elections/2018/README.md b/events/elections/2018/README.md new file mode 100644 index 00000000..f34941a1 --- /dev/null +++ b/events/elections/2018/README.md @@ -0,0 +1,65 @@ +# 2018 VOTERS GUIDE - KUBERNETES STEERING COMMITTEE ELECTION + +## Purpose + +The role of this election is to fill out the three(3) seats due for reelection this year on the [Kubernetes Steering Committee](https://github.com/kubernetes/steering). + +## Voting + +This election will shape the future of Kubernetes as a project and community. You will be voting on three (3) seats up for election. +Every elected community member will serve a two year term. + +The candidates you are voting on will be meeting regularly to strategically grow the project with contributors in mind. Most of the technical decisions, architecture planning, and the like come out of SIGs and other working groups. +Some examples of responsibilities to consider as you are voting: +- Define, evolve, and defend the vision, values, mission, and scope of the project - to establish and maintain the soul of Kubernetes. +- Charter and refine policy for defining new community groups (including Special Interest Groups, Working Groups, and Committees), and establish transparency and accountability policies for such groups. +- Define, evolve, and defend a Code of Conduct, which must include a neutral, unbiased process for resolving conflict + +Full scope of responsibilities, goals, and/or future election timelines, see [steering committee charter](https://github.com/kubernetes/steering/blob/master/charter.md). + +For more context, please see the [current issues](https://github.com/kubernetes/steering/blob/master/backlog.md) that need to be resolved or a previous governance [meeting video](https://www.youtube.com/watch?v=ltRKXLl0RaE&list=PL69nYSiGNLP1pkHsbPjzAewvMgGUpkCnJ&index=23) which led to this whole process. + +## Process + +Elections will be held using time-limited [Condorcet](https://en.wikipedia.org/wiki/Condorcet_method) ranking on [CIVS](http://civs.cs.cornell.edu/) using the [Schulze method](https://en.wikipedia.org/wiki/Schulze_method). +The top vote getters, modulo the corporate diversity requirement of no more than 1/3 of the committee from a single company, will be elected to the respective positions. + +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 on September 19, 2018 at 04:00pm UTC and end two weeks after on October 3, 2018 at 01:00am UTC. You will receive an email to the address on file at the start of the election from Jorge Castro (jorge@heptio), Community Manager, please whitelist if necessary. Detailed voting instructions will be addressed in email and the CIVS polling page. + +### Schedule + +August 15 - Announcement of Election +September 14 - All candidate bios / statement of intents due. Voting exemption forms due. +September 19 - Election Begins +October 3 - Election Closes +October 4 - Announcement of Results + +### Eligibility +Members of Standing are defined by the union of: +* SIG Chairs/Leads +* Approvers and reviewers in any Kubernetes owned repositories +* Anyone with write access to a Kubernetes owned repository +* Active [members of our community](https://github.com/kubernetes/community/blob/master/community-membership.md) + +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`. See [last year's submissions](https://github.com/kubernetes/community/tree/master/events/elections/2017) for some examples. + +### Decision +The newly elected body will be announced in the weekly [Kubernetes Community Meeting](https://github.com/kubernetes/community/blob/master/events/community-meeting.md) on October 4, 2018. + +Following the meeting, the raw voting results and winners will be published on the [Kubernetes Blog](http://blog.kubernetes.io/). + +For more information, definitions, and/or detailed election process, see full [steering committee charter](https://github.com/kubernetes/steering/blob/master/charter.md). + +## Nominees + +Name | Organization/Company | GitHub +--- | --- | -- | +[Jane Container](janecontainer.md) | ContainerCo | [@github](link this) | + +Note:The steering committee members and election officers have +recused themselves from any form of electioneering, including +campaigning, nominating, endorsing, or even asking people to run. + +Please direct any questions via email to . \ No newline at end of file -- cgit v1.2.3 From cdbb2b3e19c8e47d252862f4b0d9494a8987b986 Mon Sep 17 00:00:00 2001 From: "Jorge O. Castro" Date: Tue, 14 Aug 2018 11:52:33 -0400 Subject: Add explicit member requirements and note on exemptions --- events/elections/2018/README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/events/elections/2018/README.md b/events/elections/2018/README.md index f34941a1..69c30fca 100644 --- a/events/elections/2018/README.md +++ b/events/elections/2018/README.md @@ -38,10 +38,11 @@ October 4 - Announcement of Results ### Eligibility Members of Standing are defined by the union of: -* SIG Chairs/Leads -* Approvers and reviewers in any Kubernetes owned repositories -* Anyone with write access to a Kubernetes owned repository -* Active [members of our community](https://github.com/kubernetes/community/blob/master/community-membership.md) +- SIG Chairs/Leads +- Approvers and reviewers in any Kubernetes owned repositories +- Anyone with write access to a Kubernetes owned repository +- Active members of our community with at least [50 contributions to core Kubernetes](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) + - People who have non-code contributions can submit a [voting exemption form](URL TBD) to account for contributions not measured by devstats. 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`. See [last year's submissions](https://github.com/kubernetes/community/tree/master/events/elections/2017) for some examples. -- cgit v1.2.3 From 0ae1bf8f347f0b8cfa38a565098236799aa41c35 Mon Sep 17 00:00:00 2001 From: "Jorge O. Castro" Date: Tue, 14 Aug 2018 11:59:17 -0400 Subject: Clarify election office role --- events/elections/README.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/events/elections/README.md b/events/elections/README.md index 14a1ea3f..563fcddf 100644 --- a/events/elections/README.md +++ b/events/elections/README.md @@ -2,13 +2,13 @@ This document will outline how to conduct a Kubernetes Steering Committee Election. See the [Steering Committee Charter](https://git.k8s.io/steering/charter.md) for more information of how the committee decides when to have an election, the method, and the maximal representation. -## Steering Committee chooses Election Deadlines and Officers +## Steering Committee chooses Election Officers - Steering Committee selects the Election Officers - Dates should be in UTC time, use a [world clock service](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Election+Test&iso=20181101T00&p1=%3A&ah=10) in documentation and email announcements so that end users see the correct time and date based on where they live. -### SC Selects the following dates: +### Election Officers select the following dates: - Recommend the month of October to not collide with a release or end of a quarter. - Nomination and Voter Registration period start @@ -20,6 +20,7 @@ This document will outline how to conduct a Kubernetes Steering Committee Electi - Election period stop - CIVS needs to be manually stopped, so an actual person needs to click for the poll to stop, so this needs to be a human friendly time. - Results announcement date +- Draft dates will then be passed to the Steering Committee for final approval ## Process @@ -62,9 +63,8 @@ This document will outline how to conduct a Kubernetes Steering Committee Electi ### Steering Committee -- Select election dates - Select Election Officers -- Select criteria for Kubernetes Members of Standing +- Select criteria for who can vote in the upcoming election - Must refrain from endorsing or otherwise advocating for any candidate - Is allowed to vote in the election - Announces results of the election to the community @@ -72,11 +72,12 @@ This document will outline how to conduct a Kubernetes Steering Committee Electi ### Election Officers +- Recommend election dates to be approved by the Steering Committee - Must be a Kubernetes Member of Standing - 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 - Generates the voter guide -- Tracks candidates +- Tracks candidates - Monitors kubernetes-dev for nominations - Keeps track of nominees in a spreadsheet - Ensures that each nominee has the required nominations from three different employers (as stated in the charter) -- cgit v1.2.3 From 8a6bd2fbae9be104c4cae2771503a8ad182c36f8 Mon Sep 17 00:00:00 2001 From: "Jorge O. Castro" Date: Tue, 14 Aug 2018 12:03:18 -0400 Subject: Add explicit 2 year term --- events/elections/README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/events/elections/README.md b/events/elections/README.md index 563fcddf..083af11a 100644 --- a/events/elections/README.md +++ b/events/elections/README.md @@ -1,14 +1,15 @@ -## Kubernetes Elections +## Kubernetes Elections -This document will outline how to conduct a Kubernetes Steering Committee Election. See the [Steering Committee Charter](https://git.k8s.io/steering/charter.md) for more information of how the committee decides when to have an election, the method, and the maximal representation. +This document will outline how to conduct a Kubernetes Steering Committee Election. See the [Steering Committee Charter](https://git.k8s.io/steering/charter.md) for more information of how the committee decides when to have an election, the method, and the maximal representation. ## Steering Committee chooses Election Officers - Steering Committee selects the Election Officers -- Dates should be in UTC time, use a [world clock service](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Election+Test&iso=20181101T00&p1=%3A&ah=10) in documentation and email announcements so that end users see the correct time and date based on where they live. +- Dates should be in UTC time, use a [world clock service](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Election+Test&iso=20181101T00&p1=%3A&ah=10) in documentation and email announcements so that end users see the correct time and date based on where they live. +- The steering committee was structured in a way so that it does not turn over all at once with staggered terms, therefore all new elections are for two(2) year terms. -### Election Officers select the following dates: +### Election Officers select the following dates - Recommend the month of October to not collide with a release or end of a quarter. - Nomination and Voter Registration period start -- cgit v1.2.3 From 63cf896898dd1b827dff51e3a9132eb12164850e Mon Sep 17 00:00:00 2001 From: "Jorge O. Castro" Date: Tue, 14 Aug 2018 12:41:24 -0400 Subject: Add election officers for 2018 --- events/elections/2018/README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/events/elections/2018/README.md b/events/elections/2018/README.md index 69c30fca..b34d5fb8 100644 --- a/events/elections/2018/README.md +++ b/events/elections/2018/README.md @@ -28,6 +28,13 @@ You will be ranking your choices of the candidates with an option for "no opinio The election will open for voting on September 19, 2018 at 04:00pm UTC and end two weeks after on October 3, 2018 at 01:00am UTC. You will receive an email to the address on file at the start of the election from Jorge Castro (jorge@heptio), Community Manager, please whitelist if necessary. Detailed voting instructions will be addressed in email and the CIVS polling page. +### Officers + +The Steering Committee has selected the following people as [election officers](https://github.com/kubernetes/community/tree/master/events/elections#election-officers): +- Paris Pittman, @parispittman, Google +- Ihor Dvoretskyi, @idvoretskyi, CNCF +- Jorge Castro, @castrojo, Heptio + ### Schedule August 15 - Announcement of Election -- cgit v1.2.3