From: Zev Weiss <zweiss@equinix.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: TOF elections for 2023H2
Date: Tue, 29 Aug 2023 18:24:34 +0000 [thread overview]
Message-ID: <20230829182433.GD19997@packtop> (raw)
In-Reply-To: <ZNvDQ9xTbV-Ynk6T@heinlein.vulture-banana.ts.net>
On Tue, Aug 15, 2023 at 11:26:11AM PDT, Patrick Williams wrote:
>Hello everyone,
>
>Like last half[1], I have also run behind schedule in sending out the
>data for the TOF elections this half.
>
>The schedule will be as follows:
>
> * Aug 15th - Current TOF must publish a list of eligible voting
> members.
> * Sept 1st - Nominations (self or peer) for TOF seats must be sent to
> the mailing list.
> * Sept 1st - Developers disputing membership eligibility must submit
> a pettion request to the current TOF.
> * Sept 7th - Election Begins
> * Sept 15th - Election concludes
> * Sept 22nd - TOF will publish election results.
>
>The current election roll-call is available at:
> https://github.com/openbmc/tof-election/blob/main/2023H2/rollcall.json
>
>For this half, we have 3 seats up for election. Currently those are
>held by Brad, Ed, and Zev.
>
>Nominations for those 3 seats may be sent to the mailing list by
>replying to this email. Only those eligible to vote may be nominated.
>
I'd be happy to have another term, so I'll self-nominate.
Thanks,
Zev
next prev parent reply other threads:[~2023-08-29 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 18:26 TOF elections for 2023H2 Patrick Williams
2023-08-16 14:15 ` Gunnar Mills
2023-08-29 18:24 ` Zev Weiss [this message]
2023-09-06 17:37 ` Ed Tanous
2023-09-15 9:04 ` 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=20230829182433.GD19997@packtop \
--to=zweiss@equinix.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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.