From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: TOF elections for 2024H1
Date: Fri, 22 Mar 2024 15:23:18 -0500 [thread overview]
Message-ID: <Zf3otl5dVPv8wCcE@heinlein.vulture-banana.ts.net> (raw)
In-Reply-To: <ZeE_tWHOZLdtPXu1@heinlein.vulture-banana.ts.net>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
On Thu, Feb 29, 2024 at 08:38:45PM -0600, Patrick Williams wrote:
> The 5 nominated developers are:
> * amboar - Andrew Jeffery
> * jmbills - Jason Bills
> * pointbazaar - Alexander Hansen
> * wak-google - William Kennington
> * williamspatrick - Patrick Williams
Without any fancy tooling to handle Ranked Choice Voting, it is clear
that the votes would go to Andrew J, Jason, William, and Patrick. They
will continue in their TOF position.
Results can be verified with:
$ cat 2024H1/votes/*.json | grep '"' | sed 's/,//' | sort | uniq -c | sort -n
One thing I noticed as the votes were coming in was that it wasn't clear
if people understood that the order of your votes mattered, as TOF
elections are suppose to be Ranked Choice[1]. I will make sure this is
more clearly communicated next time we have an election. (I saw many
votes in simply alphabetical order.)
I am interested in hearing any other feedback on how voting went. Are
there improvements we should make to the process?
1. https://github.com/openbmc/docs/blob/master/tof/membership-and-voting.md#terms-and-elections
2. https://en.wikipedia.org/wiki/Ranked_voting
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-03-22 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 20:45 TOF elections for 2024H1 Patrick Williams
2024-01-15 20:47 ` Patrick Williams
2024-01-15 22:19 ` Andrew Jeffery
2024-01-17 10:32 ` Alexander Hansen
2024-01-19 1:43 ` Ren, Zhikui
2024-01-30 2:18 ` William Kennington
2024-03-01 2:38 ` Patrick Williams
2024-03-22 20:23 ` Patrick Williams [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zf3otl5dVPv8wCcE@heinlein.vulture-banana.ts.net \
--to=patrick@stwcx.xyz \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).