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

* typo
2023-08-16 20:30:41 +00:00
..
OWNERS 2022 TOC Elections framework (#1017) 2022-04-25 17:18:54 +00:00
README.md Fixed links to Elekto (#1029) 2022-04-27 17:02:52 +00:00
candidate-dprotaso.md dprotaso (#1036) 2022-05-11 02:20:33 +00:00
candidate-dsimansk.md Add dsimansk as 2022 TOC candidate (#1054) 2022-05-11 02:17:34 +00:00
candidate-n3wscott.md Fix Scott's candidate profile (#1064) 2022-05-13 00:27:54 +00:00
candidate-psschwei.md add serving approver (#1065) 2022-05-13 00:29:54 +00:00
candidate-salaboy.md Fix name of Mauricio's candidate file so that it (#1059) 2022-05-11 06:45:34 +00:00
candidate-skonto.md Add skonto for TOC 2022 (#1039) 2022-05-11 02:21:33 +00:00
candidate-zroubalik.md rename sandbox to extensions (#1419) 2023-08-16 20:30:41 +00:00
election.yaml Add OWNERS file field to candidates template per discussion with Steering on Slack. (#1030) 2022-04-27 19:08:52 +00:00
election_desc.md Fixed links to Elekto (#1029) 2022-04-27 17:02:52 +00:00
nomination-template.md Add OWNERS file field to candidates template per discussion with Steering on Slack. (#1030) 2022-04-27 19:08:52 +00:00
voters.yaml adding exception to voters.yaml (#1073) 2022-05-25 08:10:03 +00:00

README.md

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

2022 Voters Guide - Knative TOC Election

Purpose

The role of this election is to fill the four (4) 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 26 Announcement of Election
May 10 All candidate nominations are due by 23:59 UTC (4:59pm Pacific)
May 13 Election Begins via Elekto UI
May 24 Voting exception forms are due by 23:59 UTC (4:59pm Pacific)
May 27 Election Closes by 23:59 UTC (4:59pm Pacific)
June 1 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/2022-TOC folder, with the following filename format:

candidate-yourname.md

yourname in the template file should match your Github handle.

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 last TOC election.

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 once again using Elekto, an online voting tool created by CNCF intern Manish Sahani. As a reminder 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 "2022 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 the deadline above 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 the voting deadline above.

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.

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