openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: TOF elections for 2023H1
Date: Mon, 30 Jan 2023 17:47:21 -0600	[thread overview]
Message-ID: <Y9hXCcmij+TRDXJ0@heinlein.taila677.ts.net> (raw)

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

Hello everyone,

I'm behind at getting this email out.

Per https://github.com/openbmc/docs/blob/master/tof/membership-and-voting.md,
the schedule for TOF elections is suppose to be as follows:

  * Jan 1st	- Developer contributions close for OpenBMC Development Community
              membership eligibility (See “Metrics”).
  * Jan 15th - Current TOF must publish a list of eligible voting members.
  * Jan 30th - Nominations (self or peer) for TOF seats must be sent to the
               mailing list.
  * Jan 30th - Developers disputing membership eligibility must submit a
               petition request to the current TOF.
  * Feb 15th - Current TOF must publish a final list of eligible voting members
               and upcoming candidates for TOF seats.
  * March 1st - Election begins.
  * March 7th - Election concludes.

Since today is January 30th (in my part of the world) we are ~15 days
behind.  The following will be the schedule for this half:

  * Jan 30th - Current TOF must publish a list of eligible voting members.
  * Feb 15th - Nominations (self or peer) for TOF seats must be sent to the
               mailing list.
  * Feb 15th - Developers disputing membership eligibility must submit a
               petition request to the current TOF.
  * Feb 22st - Current TOF must publish a final list of eligible voting members
               and upcoming candidates for TOF seats.
  * March 1st - Election begins.
  * March 7th - Election concludes.

The only real change here is that we will extend TOF membership petitions and
TOF nominiations until Feb 15th.

With that said...

A. The current election roll-call is available at:
        https://github.com/openbmc/tof-election/blob/main/2023H1/rollcall.json

B. We have 4 members who's 1 year term has ended, which means there are 4
   positions up for election.  These members have an ending term and may
   be renominated:
        * Andrew Jeffery
        * Jason Bills
        * Patrick Williams
        * William Kennington

C. Nominations for (B) may be sent to the mailing list by replying to
   this email.  Only those eligible to vote may be nominated.

D. Disagreements with (A) may be petitioned for inclusion at:
        https://github.com/openbmc/technical-oversight-forum/issues

-- 
Patrick Williams

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

             reply	other threads:[~2023-01-30 23:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 23:47 Patrick Williams [this message]
2023-01-31  0:03 ` TOF elections for 2023H1 Patrick Williams
2023-01-31 15:39   ` Bills, Jason M
2023-02-01  1:23     ` William Kennington
2023-01-31 11:05 ` Andrew Jeffery
2023-04-03 11:46 ` 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=Y9hXCcmij+TRDXJ0@heinlein.taila677.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 NNTP newsgroup(s).