From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Patrick Williams <patrick@stwcx.xyz>,
OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: TOF elections for 2026H1
Date: Fri, 20 Mar 2026 10:42:36 +1030 [thread overview]
Message-ID: <4abc5db08e32525ff923f4e3bf5fe91b3b94e2e3.camel@codeconstruct.com.au> (raw)
In-Reply-To: <absG_8pQilMHGMnO@heinlein>
On Wed, 2026-03-18 at 16:11 -0400, Patrick Williams wrote:
> With this being the most nominated-for election in TOF history, I would
> strongly encourage candidates to reply to this email with a [brief]
> campaign: who are you, what work have you done for the community, why do
> you want to be on the TOF, etc.
Hi,
I'm Andrew, and I've nominated myself for another term on the TOF.
I'm interested in maintaining a seat there to provide input from the
perspective of the bootloader and kernel layers. I maintain the
project's Linux and U-Boot forks. An important portion of that work
boils down to ensuring contributors follow sustainable practices.
Sustainable contribution practices require early work upstream, with
all the technical and social expectations that entails.
In the case of Linux I'm the upstream maintainer of the BMC tree. The
BMC tree looks after BMC-related devicetrees as well as SoC-specific
drivers and build infrastructure. I tend to review a lot of ASPEED-
related patches.
I also maintain some elements of OpenBMC's communication plumbing.
Specifically:
* libpldm, a broadly applicable implementation of the various and
related PLDM specifications from the DMTF, and
* mctpreactor, a nexus daemon sitting between entity-manager and mctpd
for configuring MCTP networks in OpenBMC
I maintain other bits and pieces in the project as well, but those
listed above are the most significant.
I use my experience in these areas to provide input on queries raised
to the TOF. So far I feel I've helped influence decisions in helpful
directions, and I'd like to continue to do so with your vote.
Thanks,
Andrew
next prev parent reply other threads:[~2026-03-20 0:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 14:44 TOF elections for 2026H1 Patrick Williams
2026-01-21 22:22 ` Andrew Jeffery
2026-01-22 2:36 ` Brad Bishop
2026-01-22 3:25 ` Jayanth Othayoth
2026-01-22 9:32 ` Deepak Kodihalli
2026-01-23 5:38 ` Jagpal Singh Gill
2026-02-02 11:19 ` Christopher Meis
2026-02-04 14:05 ` Patrick Williams
2026-03-18 20:11 ` Patrick Williams
2026-03-19 10:21 ` Alexander Hansen
2026-03-20 0:12 ` Andrew Jeffery [this message]
2026-03-20 9:50 ` Jayanth Othayoth
2026-03-23 14:30 ` Brad Bishop
2026-03-23 16:57 ` Deepak Kodihalli
2026-03-26 1:20 ` Jagpal Singh Gill
2026-03-31 14:17 ` Patrick Williams
2026-04-01 12:43 ` 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=4abc5db08e32525ff923f4e3bf5fe91b3b94e2e3.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.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