All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: Upcoming TOF elections
Date: Fri, 14 Jan 2022 16:16:24 -0600	[thread overview]
Message-ID: <YeH2OHImO/oRgkjN@heinlein> (raw)
In-Reply-To: <YdiCUiwh1iD4ycr8@heinlein>

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

On Fri, Jan 07, 2022 at 12:11:30PM -0600, Patrick Williams wrote:
> * Jan 15th: Current TOF must publish a list of eligible voting members.

The official list of eligible voters for this half has been accepted by the TOF
and is published here:

https://github.com/openbmc/tof-election/blob/b0fcea13c5433a06c6a01b32e27083e7cb74420c/2022H1/rollcall.json

I have included the list of github ids at the end of this email as well.

> * 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

If your name is not on the above list and you believe this in error, you have
until January 30th to open an issue here with your evidence for inclusion:

https://github.com/openbmc/technical-oversight-forum/issues

> * Jan 30th:	Nominations (self or peer) for TOF seats must be sent to the mailing
>             list.

According to this document we have 4 seats up for election this half:
    https://github.com/openbmc/docs/blob/master/tof/membership-and-voting.md

There requirements are:

    - You must be eligible to vote for yourself (ie. you must be in the linked
      rollcall.json).

    - Only 2 members may be from the same company.  This doesn't mean that
      we cannot have multiple nominations from the same company, but only 2
      may be placed from the election results.
     
If you are interested in joining the TOF, or want to nominate someone, please
reply to the mailing list with your interest by Jan 30th.

---

[ Kostr, Krellan, PlotCondor, PriyangaRamasamy, RashmicaG, ZhikuiRen, adathatri,
  amboar, anoo1, anvesh001, bentyner, bjwyman, bradbishop, brandonkimbk,
  derick-montague, dixsie, drakedog2008, edtanous, geissonator, gkeishin,
  gokulsvg, gtmills, jebr224, jmbills, johnwedig, jonathan-doman, jwludzik,
  kazmierczak-lukasz, krzysztof-i, lxwinspur, manojkiraneda, mikecgithub,
  mine260309, msbarth, ojayanth, peterp-ibm, prkatti1, rahulmah, ratagupt,
  sampmisr, sandeepasingh116, santoshpuranik, sbteeks, sdompke, smccarney,
  spinler, sumbhat90, susilsi7, tomjoseph83, tonylee79, vishwabmc, vmauery,
  wak-google, williamspatrick, wltu, wrightjl1, ya-mouse, zane131 ]

-- 
Patrick Williams

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

  parent reply	other threads:[~2022-01-14 22:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 18:11 Upcoming TOF elections Patrick Williams
2022-01-10  1:39 ` Andrew Jeffery
2022-01-10  1:41   ` Andrew Jeffery
2022-01-10 14:25     ` Patrick Williams
2022-01-14 22:16 ` Patrick Williams [this message]
2022-01-14 22:31   ` TOF Nominations Patrick Williams
2022-01-19 23:30     ` Andrew Jeffery
2022-01-24 19:56     ` Ed Tanous
2022-01-26 11:10       ` Lei YU
2022-01-28 21:10         ` Patrick Williams
2022-01-29  0:27     ` Terry Duncan
2022-02-07 17:36       ` Khetan, Sharad
2022-01-15  3:09   ` Upcoming TOF elections Patrick Williams
2022-02-14 23:01 ` 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=YeH2OHImO/oRgkjN@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 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.