public inbox for openbmc@ozlabs.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: TOF elections for 2025H2
Date: Tue, 2 Sep 2025 22:15:55 -0400	[thread overview]
Message-ID: <aLek2wDSYDGMLPH6@heinlein> (raw)
In-Reply-To: <aKOKlY97pOtfuaEv@heinlein>

[-- Attachment #1: Type: text/plain, Size: 2141 bytes --]

Greetings,

For the TOF elections this half, we had 4 qualified individuals
nominated and there are 3 seats expiring.  Therefore, we are going to
have to hold an election for the half.

Per the TOF election rules[1] (with minor date adjustments):
    - The election will begin on Sept 3rd, 2025.
    - The election will conclude on Sept 10th, 2025 (*).
    - The election will be by Ranked Choice Voting of qualified OpenBMC
      developers.

For refreshment, you are considered "qualified" if your Github user ID
is found at the rollcall[2].

The 4 nominated developers are (alphabetical by Github IDs):
    * dkodihal:         Deepak Kodihalli
    * edtanous:         Ed Tanous
    * geissonator:      Andrew Geissler
    * manojkiraneda:    ManojKiran Eda

I'll again say this is a Ranked Choice Voting.  That means you should
ideally vote for at least 3 individuals, in the order of your
preference[3].

As with the last election, we have a tool to facilitate voting[4].  You are
expected to fork the Github repository, run the tool, commit the
resulting JSON file, and create a Pull-Request to submit your vote.

If you have the `gh` tool this would be as follows:
```
gh repo fork --clone openbmc/tof-election
cd tof-election
./vote --user <github-id>
# make your selections with 'vote N', 'save', 'quit'
git add 2025H2/votes/<github-id>.json
git commit -s -m "2025H2: <github-id>: add vote"
git push origin
gh pr create
```

If you don't use the `gh` tool hopefully you know the equivalent
git-commands / github webui operations.

Please reach out either by email or in #tsc-and-tof in Discord if you
have trouble voting.

(*) - Since the election rules do not specify a timezone for the
      election, please submit your vote/PR by 23:59:59 Samoa Standard
      Time (SST).

[1]: https://github.com/openbmc/docs/blob/master/tof/membership-and-voting.md#terms-and-elections
[2]: https://github.com/openbmc/tof-election/blob/main/2025H2/rollcall.json
[3]: https://en.wikipedia.org/wiki/Instant-runoff_voting
[4]: https://github.com/openbmc/tof-election

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2025-09-03  2:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 20:18 TOF elections for 2025H2 Patrick Williams
2025-08-18 20:25 ` Ed Tanous
2025-08-18 21:12 ` Andrew Geissler
2025-08-19  7:02 ` Manojkiran Eda
2025-08-19 20:39 ` Patrick Williams
2025-08-20  5:21   ` Deepak Kodihalli
2025-08-21  5:33   ` Marri Devender Rao
2025-08-21  6:52     ` dhruvaraj S
2025-08-21  6:54       ` Rohit Pai
2025-08-21  7:07       ` dhruvaraj S
2025-08-21 17:43         ` Tom Joseph
2025-08-22 11:00 ` Patrick Williams
2025-09-03  2:15 ` Patrick Williams [this message]
2025-09-03  6:34   ` Sridevi Ramesh
2025-09-03 13:03     ` Gunnar M
2025-09-20 23:17   ` Patrick Williams
  -- strict thread matches above, loose matches on Subject: below --
2025-08-19  7:04 Rohit Pai

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=aLek2wDSYDGMLPH6@heinlein \
    --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