All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bills, Jason M" <jason.m.bills@linux.intel.com>
To: openbmc@lists.ozlabs.org
Subject: Re: TOF elections for 2025H1
Date: Mon, 10 Mar 2025 16:55:21 -0600	[thread overview]
Message-ID: <9759ef8b-d4ef-4642-a4a4-7f800f6aad30@linux.intel.com> (raw)
In-Reply-To: <Z8ec-DOTlSM8FMhC@heinlein>



On 3/4/2025 5:38 PM, Patrick Williams wrote:
> Hello,
> 
> It is time again for TOF elections.  The current roll-call is available
> at:
>      https://github.com/openbmc/tof-election/tree/main/2025H1
> 
> For this half, we have 4 seats up for election.  Currently those are
> held by Andrew J., Jason, Patrick, and William.  Due to slipping from
> the developer membership, Jason is not eligible for re-election.
> 
> Nominations for those 4 seats may be sent to the mailing list by
> replying to this email.  Only those eligible to vote may be nominated.
> 
> Nominations are due by Sunday March 16th, 2024.  The election, if
> required, will be held immediately after with more details to follow.
> 
> As usual, disagreements with the rollcall results can be raised to the
> TOF.
> 

Thank you all for allowing me to serve on the TOF for the last couple of 
years!  I hope that I have helped the community and provided meaningful 
support during my tenure.

If you are eligible, please consider putting your name up for election 
to help support a our OpenBMC community!

Thanks,
-Jason

  parent reply	other threads:[~2025-03-10 22:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05  0:38 TOF elections for 2025H1 Patrick Williams
2025-03-05  0:39 ` Patrick Williams
2025-03-05 23:44 ` Andrew Jeffery
2025-03-06  5:58   ` Jayanth Othayoth
2025-03-10 22:55 ` Bills, Jason M [this message]
2025-03-13  0:15 ` Jagpal Singh Gill
2025-04-01 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=9759ef8b-d4ef-4642-a4a4-7f800f6aad30@linux.intel.com \
    --to=jason.m.bills@linux.intel.com \
    --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.