Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create 2022 election docs #259

Merged
merged 2 commits into from
May 18, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
85 changes: 85 additions & 0 deletions toc/elections/2022/Readme.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,85 @@
# 2022 CFF TOC Election Guide


## Overview


Each year, the CFF technical community holds an election for open seats on the
Technical Oversight Committee (TOC). The rules governing this election are set in the
[CFF's project charter](../../../governing-board/charter.md) (See section 7(b) and 7(e)
for the relevant details).


This guide exists to serve as a guide to this year's election process.


## Schedule


| Date | Event |
| -------------------------- | ------------------------ |
| May 18 | Announcement of Election (at least 4 weeks before results) |
| May 18 through June 2 | Candidate nomination period (at least 2 weeks long and ending 2 weeks before results) |
| June 2 | Election Begins via email ballots (alow 2 work days to prepare election system) |
| June 17 | Election Closes (at least 2 weeks after election begins) |
| *June 22* | Announcement of Results (at least 2 work days after election ends) |


## Candidate Processes


**Nominations**


Every eligible voter can nominate candidates for the TOC, and we encourage you to do so. If you are
eligible to serve on the TOC, you can self nominate! If you want to nominate someone else, do so as
well!


You can nominate someone for the TOC by [submitting an issue using this template](https://github.com/cloudfoundry/community/issues/new?assignees=&labels=election&template=toc-candidate-nomination.md&title=TOC+Candidate+Nomination+for+%5BPerson+Name%5D).


The deadline is June 2nd to be nominated (and for the nominee to indicate acceptance).


It is strongly recommended that you confirm that a nominee is interested and willing
to accept the nomination prior to submitting the nomination issue.


**Confirming Nominee Eligibility**


Once a nomination is received, the CFF staff will contact the nominee to confirm acceptance
of the nomination. If the nominee accepts, they will be added to the list of nominees at the bottom
of this file. The nomination issue will be closed, noting if the nominee accepted or declined the
nomination.


## Voting Process


The election will be conducted using a time-limited [Condorcet](https://civs.cs.cornell.edu/rp.html) ranking
on [CIVS](http://civs.cs.cornell.edu/) using the Schulze method.


Voters will receive an email with a ballot link. Voters will have until the end of the election cycle
to submit their ballot.
Comment on lines +61 to +66
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like us to explore using https://github.com/elekto-io/elekto as the election system for this cycle, which Kubernetes has been using for its Steering Committee elections and which Knative also started using last year. We ran into significant confusion with the email exchanges and the once-a-day syncing cycle from the CIVS service last time.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BTW, I started getting Elekto to build and run on CF on my fork at https://github.com/emalm/elekto/tree/run-with-cf. I've gotten it to stage and to connect to a bound MySQL DB automatically, but I haven't tried configuring the GitHub settings yet.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hah, I kept playing around with this, and it's now running at https://elekto-emalm.apps.dhaka.cf-app.com, with the election config repo at https://github.com/emalm/elekto.meta.test. @christopherclark, I made you both an admin and a voter for the "name the app" election that it's running right now, if you wanted to take a look at it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Switching to Elekto seems like a reasonable move to me. I've signed into the Elekto app but haven't explored more than that. Maybe next week we can run a test election @emalm ?

We can update the voting method details anytime before voting starts - proposed date June 2nd.



## Election Results


The newly elected body will be announced via [email protected] on 22 Jun, 2022.


Following the announcement, the raw voting results and winners will be published.


## Nominees


| Name | Organization/Company | GitHub |
|:----------:|:--------------------:|:--------:|
| Name | Employer | [@githubid](https://github.com/githubid) |