TOF elections for 2026H1

TOF elections for 2026H1

[Patrick Williams]

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

Hello,

It is time again for TOF elections.  The current roll-call is available
at:
    https://github.com/openbmc/tof-election/tree/main/2026H1/rollcall.json

For this half, we have 4 seats up for election.  Currently those are
held by Andrew Jeffery, Patrick Williams, Jagpal Gill and Jayanth Othayoth.
All 4 are eligible for re-nomination / 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 nominate or be
nominated.

Nominations are due by Sunday Feb 15, 2026.  The election, if
required, will be held beginning March 1st with more details to follow.

As usual, disagreements with the rollcall results can be raised to the
TOF.

-- 
Patrick Williams

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

Re: TOF elections for 2026H1

[Andrew Jeffery]

On Wed, 2026-01-21 at 09:44 -0500, 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/2026H1/rollcall.json
> 
> For this half, we have 4 seats up for election.  Currently those are
> held by Andrew Jeffery, Patrick Williams, Jagpal Gill and Jayanth Othayoth.
> All 4 are eligible for re-nomination / 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 nominate or be
> nominated.

I re-nominate myself.

Andrew

Re: TOF elections for 2026H1

[Brad Bishop]

Hi Patrick

I’ll nominate myself.

Thanks,
Brad

> On Jan 21, 2026, at 9:44 AM, Patrick Williams <patrick@stwcx.xyz> wrote:
> 
> Hello,
> 
> It is time again for TOF elections.  The current roll-call is available
> at:
>    https://github.com/openbmc/tof-election/tree/main/2026H1/rollcall.json
> 
> For this half, we have 4 seats up for election.  Currently those are
> held by Andrew Jeffery, Patrick Williams, Jagpal Gill and Jayanth Othayoth.
> All 4 are eligible for re-nomination / 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 nominate or be
> nominated.
> 
> Nominations are due by Sunday Feb 15, 2026.  The election, if
> required, will be held beginning March 1st with more details to follow.
> 
> As usual, disagreements with the rollcall results can be raised to the
> TOF.
> 
> --
> Patrick Williams
> <signature.asc>

Re: TOF elections for 2026H1

[Jayanth Othayoth]

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

I re-nominate myself.

On Wed, Jan 21, 2026 at 8:14 PM Patrick Williams <patrick@stwcx.xyz> wrote:

> Hello,
>
> It is time again for TOF elections.  The current roll-call is available
> at:
>     https://github.com/openbmc/tof-election/tree/main/2026H1/rollcall.json
>
> For this half, we have 4 seats up for election.  Currently those are
> held by Andrew Jeffery, Patrick Williams, Jagpal Gill and Jayanth Othayoth.
> All 4 are eligible for re-nomination / 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 nominate or be
> nominated.
>
> Nominations are due by Sunday Feb 15, 2026.  The election, if
> required, will be held beginning March 1st with more details to follow.
>
> As usual, disagreements with the rollcall results can be raised to the
> TOF.
>
> --
> Patrick Williams
>

[-- Attachment #2: Type: text/html, Size: 1375 bytes --]

Re: TOF elections for 2026H1

[Deepak Kodihalli]

On Wed, Jan 21, 2026 at 8:14 PM Patrick Williams <patrick@stwcx.xyz> wrote:
>
> Hello,
>
> It is time again for TOF elections.  The current roll-call is available
> at:
>     https://github.com/openbmc/tof-election/tree/main/2026H1/rollcall.json
>
> For this half, we have 4 seats up for election.  Currently those are
> held by Andrew Jeffery, Patrick Williams, Jagpal Gill and Jayanth Othayoth.
> All 4 are eligible for re-nomination / 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 nominate or be
> nominated.

I nominate myself.

Thanks,
Deepak

Re: TOF elections for 2026H1

[Jagpal Singh Gill]

I re-nominate myself.

Regards
Jagpal S Gill

> On Jan 21, 2026, at 8:14 PM, Patrick Williams <patrick@stwcx.xyz> wrote:
> 
> Hello,
> 
> It is time again for TOF elections.  The current roll-call is available
> at:
>    https://github.com/openbmc/tof-election/tree/main/2026H1/rollcall.json
> 
> For this half, we have 4 seats up for election.  Currently those are
> held by Andrew Jeffery, Patrick Williams, Jagpal Gill and Jayanth Othayoth.
> All 4 are eligible for re-nomination / 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 nominate or be
> nominated.
> 
> Nominations are due by Sunday Feb 15, 2026.  The election, if
> required, will be held beginning March 1st with more details to follow.
> 
> As usual, disagreements with the rollcall results can be raised to the
> TOF.
> 
> -- 
> Patrick Williams

Re: TOF elections for 2026H1

[Christopher Meis]

Am 21.01.26 um 15:44 schrieb Patrick Williams:
> Hello,
> 
> It is time again for TOF elections.  The current roll-call is available
> at:
>      https://github.com/openbmc/tof-election/tree/main/2026H1/rollcall.json
> 
> For this half, we have 4 seats up for election.  Currently those are
> held by Andrew Jeffery, Patrick Williams, Jagpal Gill and Jayanth Othayoth.
> All 4 are eligible for re-nomination / 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 nominate or be
> nominated.
> 
> Nominations are due by Sunday Feb 15, 2026.  The election, if
> required, will be held beginning March 1st with more details to follow.
> 
> As usual, disagreements with the rollcall results can be raised to the
> TOF.
> 

I nominate Alexander Hansen (pointbazaar)

Re: TOF elections for 2026H1

[Patrick Williams]

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

On Wed, Jan 21, 2026 at 09:44:27AM -0500, Patrick Williams wrote:

> Nominations for those 4 seats may be sent to the mailing list by
> replying to this email.  Only those eligible to vote may nominate or be
> nominated.
> 
> Nominations are due by Sunday Feb 15, 2026.  The election, if
> required, will be held beginning March 1st with more details to follow.

I will also self-nominate for re-election.

-- 
Patrick Williams

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

Re: TOF elections for 2026H1

[Patrick Williams]

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

Greetings,

For the TOF elections for this half, we had 7 qualified individuals
nominated and there are 4 seats expiring.  Therefore, we are going to
have to hold an election for the half. 

The 7 nominated developers[1] are (alphabetical by Github IDs):
    * Andrew Jeffery
    * Brad Bishop
    * Deepak Kodihalli
    * Jagpal Gill
    * Jayanth Othayoth
    * Alexander Hansen
    * Patrick Williams

A few key points about the election:
    - Voting is by Ranked Choice Voting.  The order you give as your
      preference matters [2,3].

    - TOF members represent the development community and not their
      companies.

    - Since there are 4 seats up for election, you may submit a vote
      with up to 4 candidates.

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.

Votes will be accepted until April 1st, 2026 at 12:00 GMT from qualified
votes[4].

As with the last election, we have a tool to facilitate voting[5].  You are
expected to fork the Github repository, run the tool, commit the
resulting JSON file, and create a Pull-Request to submit your vote.

If you have the `gh` tool this would be as follows:
```
gh repo fork --clone openbmc/tof-election
cd tof-election
./vote --user <github-id>
# make your selections with 'vote N', 'save', 'quit'
git add 2026H1/votes/<github-id>.json
git commit -s -m "2026H1: <github-id>: add vote"
git push origin
gh pr create
```

[1]: https://github.com/openbmc/tof-election/blob/main/2026H1/candidates.json
[2]: https://github.com/openbmc/docs/blob/master/tof/membership-and-voting.md#terms-and-elections
[3]: https://en.wikipedia.org/wiki/Instant-runoff_voting
[4]: https://github.com/openbmc/tof-election/blob/main/2026H1/rollcall.json
[5]: https://github.com/openbmc/tof-election

-- 
Patrick Williams

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

Re: TOF elections for 2026H1

[Alexander Hansen]

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

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

my name is Alexander Hansen (GitHub: pointbazaar), firmware engineer at 
9elements working on OpenBMC.

I have contributed to sdbusplus, bmcweb, entity-manager, dbus-sensors, 
and libpldm, working on D-Bus modeling,
Redfish multi-host support, and platform support (e.g. Tyan s5549/s8030 
platforms).

Some concrete examples of my work:

- bmcweb: binary size optimization with busybox approach (one binary for 
both the daemon and cli utilitiy)
- dbus-sensors: modernize debug logging with lg2
- phosphor-bmc-code-mgmt: parts of the common code implementation 
underpinning many device specific code updaters
- entity-manager: design and implementation for reworked physical 
topology  (Type: "Port" configuration records)
- sdbusplus: discussions and patches around |object_path| behavior and 
API design (default values, usability, and correctness)
- libpldm:  libpldm++ library implementation
- phosphor-led-manager:  removal of the yaml config mechanism in favor 
of json based configuration ('one way' to do things)
- removal of preprocessor based conditional compilation in favor of `if 
constexpr` in various repos

 > why doyou want to be on the TOF I believe OpenBMC could benefit from 
some controversial ideas like - deletion of unused features. (unused 
code should not block upstream development, i do not count private 
downstream forks) - consistency of implementation across repositories 
(contributors should not have to adopt an entirely new style for every 
repo) - reducing the amount of code duplication
- 'one way' to do things instead of various (possibly incompatible) 
alternatives - progress on the upstream community code over stability 
for downstream forks If you like these ideas then i can represent them 
for you as part of ToF :)

On 3/18/26 21:11, Patrick Williams wrote:
> Greetings,
>
> For the TOF elections for this half, we had 7 qualified individuals
> nominated and there are 4 seats expiring.  Therefore, we are going to
> have to hold an election for the half.
>
> The 7 nominated developers[1] are (alphabetical by Github IDs):
>      * Andrew Jeffery
>      * Brad Bishop
>      * Deepak Kodihalli
>      * Jagpal Gill
>      * Jayanth Othayoth
>      * Alexander Hansen
>      * Patrick Williams
>
> A few key points about the election:
>      - Voting is by Ranked Choice Voting.  The order you give as your
>        preference matters [2,3].
>
>      - TOF members represent the development community and not their
>        companies.
>
>      - Since there are 4 seats up for election, you may submit a vote
>        with up to 4 candidates.
>
> 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.
>
> Votes will be accepted until April 1st, 2026 at 12:00 GMT from qualified
> votes[4].
>
> As with the last election, we have a tool to facilitate voting[5].  You are
> expected to fork the Github repository, run the tool, commit the
> resulting JSON file, and create a Pull-Request to submit your vote.
>
> If you have the `gh` tool this would be as follows:
> ```
> gh repo fork --clone openbmc/tof-election
> cd tof-election
> ./vote --user <github-id>
> # make your selections with 'vote N', 'save', 'quit'
> git add 2026H1/votes/<github-id>.json
> git commit -s -m "2026H1: <github-id>: add vote"
> git push origin
> gh pr create
> ```
>
> [1]:https://github.com/openbmc/tof-election/blob/main/2026H1/candidates.json
> [2]:https://github.com/openbmc/docs/blob/master/tof/membership-and-voting.md#terms-and-elections
> [3]:https://en.wikipedia.org/wiki/Instant-runoff_voting
> [4]:https://github.com/openbmc/tof-election/blob/main/2026H1/rollcall.json
> [5]:https://github.com/openbmc/tof-election
>

[-- Attachment #2: Type: text/html, Size: 5690 bytes --]

Re: TOF elections for 2026H1

[Andrew Jeffery]

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

Re: TOF elections for 2026H1

[Jayanth Othayoth]

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

On Thu, Mar 19, 2026 at 1:48 AM Patrick Williams <patrick@stwcx.xyz> 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.
>


I’m Jayanth (ojayanth), TOF member, long‑time contributor, and maintainer
of phosphor‑debug‑collector and phosphor‑certificate‑manager.
Along with my regular contributions across the project, I recently
contributed significantly to the ongoing *clang‑tidy enablement effort*,
helping bring many repositories closer to consistent clang‑compliance.

If you’ve found my work helpful, I’d appreciate your support in the 2026
TOF.

[-- Attachment #2: Type: text/html, Size: 1287 bytes --]

Re: TOF elections for 2026H1

[Brad Bishop]

Hi Everyone

I'm Brad Bishop (radsquirrel) and this is my TOF election campaign note.  I've been hacking away on OpenBMC since 2015, sometimes furiously, although for the last few years not so much (although I'm ramping back up).  I implemented phosphor-objmgr, phosphor-inventory-manager, phosphor-hwmon, phosphor-rest-server, phosphor-dbus-monitor, and probably some other things.  This was all long ago - I'm happy to report that most of these components have lost favor for other code or have been re-written, all by people much smarter than me.

For awhile I was the sole OpenBMC maintainer and then I was the TSC chair from 2018-2022.  I was the architect behind the creation of this TOF working group that I am now seeking a seat on, and after it was established I held a seat for a couple of years.  In all these roles I was an advocate for shared ownership and fairness, a consequence of which is the diverse developer community OpenBMC has today.

Quite simply I want to be on the TOF because a significant part of my career has been invested in OpenBMC and its community and I am connected to the code and the people.  Some ideas/things I stand for:

- copying what works from other successful open source communities
- sharing ownership
- removing barriers
- upstream first
- a monorepo
- adopting rust

but ultimately I just want to participate and help the community be the best it can.

Thank you for your support.
-Brad

Re: TOF elections for 2026H1

[Deepak Kodihalli]

> 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 Deepak Kodihalli. I work as a BMC engineer at Nvidia, focused on OpenBMC.
I've been associated with the OpenBMC project for 8+ years (hiatus during
2022-2024), and have a broad range of contributions to the project [1]. I
implemented the initial PLDM stack. I co-maintain pldm, phosphor-logging and
phosphor-settingsd. I'm a contributing author for some of the standard
PLDM specs.

My recent contributions are in the areas of phosphor-dbus-interfaces,
pldm reviews
and the Nvidia GPU dbus-sensors app. I'm also working on getting MCTP over USB
patches merged across a few repos.

I would like to be on the TOF to provide input on/contribute to the areas of:
- Anything related to PLDM
- DBus Interfaces guidelines
- Ideas to improve rework/review times
- Improving code coverage

[1] https://gerrit.openbmc.org/q/owner:deepak.kodihalli.83@gmail.com

Thanks,
Deepak

Re: TOF elections for 2026H1

[Jagpal Singh Gill]

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

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 everyone,

I'm Jagpal Singh Gill (GitHub-Id: jagpalgill) working at Meta Inc, and I'm running for a TOF seat in this election.

My contributions to OpenBMC:

I've been an active upstream contributor since 2023 and I currently serve as owner/maintainer for the following repos/features:


  *   phosphor-health-monitor -- Led a full rewrite: health metrics framework, hysteresis, threshold configuration, storage/tmpfs monitoring.
  *   phosphor-bmc-code-mgmt -- Major rework of the firmware update stack: new async D-Bus update interface, led the effort to develop a common layer used by different update service daemons.
  *   phosphor-modbus -- Implemented sensor, inventory, firmware data collection over serial.
  *   entity-manager -- Owner for Meta platform configurations.
  *   dbus-sensors -- Maintainer for LeakDetector and CableMonitor.

Beyond these, I've contributed to bmcweb (Redfish update service, multipart form handling, Manager Diagnostic Data), phosphor-dbus-interfaces (new interfaces for health metrics, leak detection, firmware update, valves, pumps, cables), and sdbusplus (async fd sender/receiver, async mutex). I actively review contributions from engineers across the OpenBMC community across multiple repos.

What I'd focus on:


  *   Ensuring new designs are reviewed thoroughly and are architecturally consistent.
  *   Helping the community navigate the growing complexity of liquid cooling, modular chassis, and next-gen platform requirements.
  *   Making the design proposal and review process more accessible to new and existing contributors.

Thanks for your consideration.

Regards
Jagpal Singh Gill



[-- Attachment #2: Type: text/html, Size: 3274 bytes --]

Re: TOF elections for 2026H1

[Patrick Williams]

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

On Wed, Mar 18, 2026 at 04:11:43PM -0400, Patrick Williams wrote:
> Votes will be accepted until April 1st, 2026 at 12:00 GMT from qualified
> votes[4].

Reminder that there are a little less than 22 hours left to vote.

-- 
Patrick Williams

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

Re: TOF elections for 2026H1

[Patrick Williams]

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

On Wed, Mar 18, 2026 at 04:11:43PM -0400, Patrick Williams wrote:

Hello,

> The 7 nominated developers[1] are (alphabetical by Github IDs):
>     * Andrew Jeffery
>     * Brad Bishop
>     * Deepak Kodihalli
>     * Jagpal Gill
>     * Jayanth Othayoth
>     * Alexander Hansen
>     * Patrick Williams

The results of the election are:
    * Patrick Williams
    * Andrew Jeffery
    * Brad Bishop
    * Jagpal Gill

Those members will be added to the TOF effective immediately.

Full results of the election can be obtained by running
`./tally --election 2026H1` in the tof-election repository.

```
Election for Seat 1
Round 1
Votes this round: {'amboar': 12, 'bradbishop': 1, 'dkodihal': 10, 'jagpalgill': 7, 'ojayanth': 1, 'pointbazaar': 1, 'williamspatrick': 33}
Elected williamspatrick
Election for Seat 2
Round 1
Votes this round: {'amboar': 34, 'bradbishop': 3, 'dkodihal': 10, 'jagpalgill': 10, 'ojayanth': 1, 'pointbazaar': 7}
Elected amboar
Election for Seat 3
Round 1
Votes this round: {'bradbishop': 16, 'dkodihal': 10, 'jagpalgill': 24, 'ojayanth': 5, 'pointbazaar': 10}
Rejected ojayanth from the next round.
Round 2
Votes this round: {'bradbishop': 21, 'dkodihal': 10, 'jagpalgill': 24, 'pointbazaar': 10}
Rejected pointbazaar from the next round.
Round 3
Votes this round: {'bradbishop': 24, 'dkodihal': 10, 'jagpalgill': 31}
Rejected dkodihal from the next round.
Round 4
Votes this round: {'bradbishop': 34, 'jagpalgill': 31}
Elected bradbishop
Election for Seat 4
Round 1
Votes this round: {'dkodihal': 17, 'jagpalgill': 30, 'ojayanth': 6, 'pointbazaar': 12}
Rejected ojayanth from the next round.
Round 2
Votes this round: {'dkodihal': 17, 'jagpalgill': 31, 'pointbazaar': 12}
Elected jagpalgill
Final election: ['williamspatrick', 'amboar', 'bradbishop', 'jagpalgill']
```

-- 
Patrick Williams

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