From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: 2022H2 TOF Elections
Date: Tue, 19 Jul 2022 16:10:24 -0500 [thread overview]
Message-ID: <YtcdwFSsS2vsWVoU@heinlein.stwcx.org.github.beta.tailscale.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]
Hello Developers,
Since we are into July, the 2nd half TOF cycle starts. See this
document for a reminder on the process:
https://github.com/openbmc/docs/blob/master/tof/membership-and-voting.md#terms-and-elections
There are 3 important points:
1. The current TOF publishes a list of eligible developers for the
next TOF election (that is the primary purpose of this email).
2. Nominations are open for TOF members and run through the end of
July.
3. The election, if necessary, is to begin September 1st.
Now for the details...
## Eligible developers.
Contributions made from January through June qualified for this TOF
cycle. We have 82 developers [currently] qualified for voting in this
cycle and they are listed here:
https://github.com/openbmc/tof-election/blob/main/2022H2/rollcall.json
Anyone who feels they made contributions to the project which did not
show up in our metrics may request to be added to this roll-call by
opening an issue by July 31st to the current TOF at:
https://github.com/openbmc/technical-oversight-forum/issues
## Nominations for TOF membership
We currently have 2 TOF members who's term is completed and 1 open seat,
for a total of 3 seats available during this cycle. Nominations, either
self-nominations or of others, should be sent to the mailing list by
July 31st. Remember that only those qualified to vote may be nominated,
but anyone may nominate someone from the roll-call list.
Brad and Ed are the two members who will have their term concluded and
the open seat is due to a resignation. If we have 3 or less developers
nominated for the TOF then the election will not be necessary.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-07-19 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 21:10 Patrick Williams [this message]
2022-07-19 23:11 ` 2022H2 TOF Elections M. D. Truong
2022-07-27 8:27 ` Zev Weiss
2022-07-19 23:13 ` Ed Tanous
2022-07-25 16:24 ` Brad Bishop
2022-07-26 16:09 ` Patrick Williams
2022-09-14 20:21 ` Patrick Williams
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=YtcdwFSsS2vsWVoU@heinlein.stwcx.org.github.beta.tailscale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.