public inbox for openbmc@ozlabs.org
 help / color / mirror / Atom feed
From: Alexander Hansen <alexander.hansen@9elements.com>
To: Patrick Williams <patrick@stwcx.xyz>, openbmc@lists.ozlabs.org
Subject: Re: TOF elections for 2026H1
Date: Thu, 19 Mar 2026 11:21:56 +0100	[thread overview]
Message-ID: <325cc62f-2c65-4ce6-aa22-79d5f23f4672@9elements.com> (raw)
In-Reply-To: <absG_8pQilMHGMnO@heinlein>

[-- 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 --]

  reply	other threads:[~2026-03-19 10:22 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 [this message]
2026-03-20  0:12   ` Andrew Jeffery
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=325cc62f-2c65-4ce6-aa22-79d5f23f4672@9elements.com \
    --to=alexander.hansen@9elements.com \
    --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