openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Patrick Williams" <patrick@stwcx.xyz>,
	"OpenBMC List" <openbmc@lists.ozlabs.org>
Subject: Re: TOF Nominations
Date: Thu, 20 Jan 2022 10:00:32 +1030	[thread overview]
Message-ID: <61e076fe-d490-4034-933e-d821d9123001@www.fastmail.com> (raw)
In-Reply-To: <YeH5uCwUQ02RrGok@heinlein>



On Sat, 15 Jan 2022, at 09:01, Patrick Williams wrote:
> On Fri, Jan 14, 2022 at 04:16:24PM -0600, Patrick Williams wrote:
>> On Fri, Jan 07, 2022 at 12:11:30PM -0600, Patrick Williams wrote:
> 
>> > * Jan 30th:	Nominations (self or peer) for TOF seats must be sent to the mailing
>> >             list.
>
> I'll be the first to nominate myself for participating in the TOF as my 
> current term is one of the 4 up for election.

I'm also nominating myself.

>
> I suspect most developers know me already.  I've been around the project since
> the beginning (other than a 2 year break where I didn't work on BMCs) and I'm
> a very active contributor, reviewer, and Discordian.

For the same reasons, sans the 2 year break :)

Andrew

  reply	other threads:[~2022-01-19 23:31 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
2022-01-14 22:31   ` TOF Nominations Patrick Williams
2022-01-19 23:30     ` Andrew Jeffery [this message]
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=61e076fe-d490-4034-933e-d821d9123001@www.fastmail.com \
    --to=andrew@aj.id.au \
    --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 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).