community/elections/2021-TOC
David Hadas 9360770db1
rename sandbox to extensions (#1419)
* renqme sandbox to extensions

* typo
2023-08-16 20:30:41 +00:00
..
README.md Add more information about Elekto for TOC election (#566) 2021-04-13 06:56:00 -07:00
candidate-dprotaso.md dprotaso's candidacy submission 👑♦️ (#576) 2021-04-22 09:43:37 -07:00
candidate-evankanderson.md rename sandbox to extensions (#1419) 2023-08-16 20:30:41 +00:00
candidate-julz.md Add julz TOC candidate profile (#581) 2021-04-22 09:44:37 -07:00
candidate-n3wscott.md Fix formatting in Schott Nichol's profile for Elekto. (#582) 2021-04-23 10:12:38 -07:00
election.yaml Add Elekto requirements for 2021 TOC election. (#562) 2021-04-12 09:46:42 -07:00
election_desc.md Add more information about Elekto for TOC election (#566) 2021-04-13 06:56:00 -07:00
nomination-template.md Remove template as "candidate" in TOC election (#584) 2021-04-23 11:27:39 -07:00
results.md updated Elekto results page with the final results, since we are not having a runoff (#640) 2021-06-04 00:09:45 -07:00
voters.yaml Add two voters per approved exception requests. (#592) 2021-04-29 06:38:54 -07:00

README.md

title linkTitle weight type
Knative TOC Election - 2021 Voters Guide 2021 Voters Guide 30 docs

2021 Voters Guide - Knative TOC Election

Purpose

The role of this election is to fill the two (2) seats due for election this year on the Knative Technical Oversight Committee. The elected members will serve two (2) year terms.

Background

This election will shape the future of Knative as a community and project. While WGs help shape the individual direction of the project, the [TOC Charter] covers the technical direction, health of the project and community as a whole.

Eligibility

Please refer to the TOC Election Charter for:

The list of eligible voters is stored in the community repository, but it is easier to check if you are eligible by logging into Elekto. See Voting Process below for more details.

Schedule

Date Event
April 13 Announcement of Election
April 23 All candidate nominations and voting exception forms due by 0000 UTC (5pm Pacific)
April 27 Election Begins via Elekto UI
May 11 Election Closes by 0000 UTC (5pm Pacific)
May 13 Announcement of Results

Election Officers

In an effort to run a fair and transparent election, the following people have been asked by the Steering Committee to run this election:

You can reach us by emailing elections@knative.team

Candidacy Process

Nomination

If you want to stand for election, open a PR against the knative/community repository to include your candidate profile in the /elections/2021-TOC folder, with the following filename format:

candidate-yourname.md

We have included a template file as an example. This profile should include:

  • Your name
  • Your company affiliation (employer or otherwise)
  • Your contributions to Knative
  • Why you are running

You can find examples from the past SC elections, although the format there was different due to using CIVS for elections rather than Elekto.

Once you have created the PR, you may email knative-dev and/or knative-users once to let people know about your candidacy and encourage endorsements as comments on the PR. Please use something like for your email in order to encourage endorsements in Github and not on the mailing list:

Fellow Knative community members,

My name is {your name} and I am running for TOC.  You can read
my profile here: {link to PR}.  If you support my candidacy, please endorse me
by commenting on that PR.  Please don't reply to endorse me on this list.

After a candidate has met all election requirements, the Election Officers will merge the profile PR.

If you want to nominate someone else, you may do so, but PLEASE talk to them first.

Campaigning

Please refer to the TOC 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

Elections will be held using Elekto, an online voting tool created by CNCF intern Manish Sahani. Elekto has one critical advantage over CIVS, which is that it relies on GitHub Oauth to log you in to vote, instead of relying on email.

Thus, when you go to Elekto you will be prompted to log in your GitHub account. Please do, so, and then click on "Explore Election" to look at the list of elections. From there you can click on the "2021 Knative TOC Election."

The election page will, among other things, tell you if you are eligible to vote, via a button at the top of the screen. Due to limitations in our contributor data, many contributors may have been unfairly missed; if you are one of these, please file a voting exception by May 9th so that we can enfranchise you.

As candidates file their candidate statements in the community repo, they will become visible in the Elekto UI. You may click through to any candidate to see their profile.

Once the vote begins, you will be able to rank the candidates in the order of your preference, and submit your ballot. When you submit, you will be offered a chance to set a password, which is required if you want the ability to return and re-cast your ballot before May 13th.

Employer diversity is encouraged, and thus maximal representation will be enforced as spelled out in the TOC Election Charter.

All data for Elekto is stored on a pair of GCP instances operated by Josh Berkus and Manish Sahani, and is not shared with third parties. Individual ballot data is encrypted, and not retrievable by anyone except in aggregate form.

Decision

Ballots are compiled by Elekto and all candidates are ranked using the Condorcet method, Schultze variant.

The newly elected body will be announced on the Knative Blog on May 13, 2020.

For more information, definitions, and/or detailed election process, please refer to the TOC Election Charter.