You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The election will follow the project governance. This section summarizes the key parts of the governance and adds specifics for the operation of the election:
"Participants" are those that have contributed to or participated in the SLSA community, such as by attending meetings, engaging in conversations on Slack, or commenting on documents.
The nomination period should last two weeks. After the nomination period, the voting period should begin and last one week. Participants are eligible to vote for Steering Committee members. The Steering Committee Members will then tally the votes and announce the new Steering Committee Members.
In the case of disagreement between this issue and the project governance, the project governance is definitive.
Election Timeline
The dates below are proposed but not finalized. The actual timeline will be relative to the announcement by the current Steering Committee.
Date
Description
April 14th
Election Issue Created
April 20th
Election Issue approved by current Steering Committee
April 20th
Nomination period open, voting registration
May 10th
Last day for nominations and registrations
May 11th
Voting period open
May 17th
Last day for voting
May 20th
Voting results published, new Steering Committee formed
Voting Operations
Nominees will be declared as comments to this issue.
Participants may self-nominate.
Nominations should include Name, Affiliation (e.g. company or organization), Background (be brief), and any supporting text of why the nominee is good for the role.
I would like to self-nominate to run for steering committee membership.
Name: Andrew McNamara
Affiliation: Red Hat
Background: I believe that SLSA has an important role in helping people with usable security. Reasoning about security and trust is hard, especially in the modern supply chain. My interest in this area combined with my involvement in a build platform built on top of SLSA provenance (konflux-ci.dev) and I have talked about this at many conferences. The lines around SDLC are only getting more complex and we are actively exploring how this will change our preconceived notions of security and trust.
I would like to nominate myself for the SLSA steering committee
Name: Tom Bedford
Organisation: Bloomberg
Background: I help my organisation reduce SDLC-related risks. SLSA is quickly becoming a part of that, and I've found myself being able explain the risks and remediations well to a variety of user types - from CISO, CTO, individual engineers and legal/compliance. I am also a maintainer of the Dependency Track, which is in the progress of being drafted for SLSA, after I helped contribute it from the original 'S2C2F' specification.
I would like to self-nominate to run for steering committee membership.
Name: Brandon Lum
Organization: Google
Background: I help teams at Google adopt SLSA, working with builders to achieve higher SLSA levels, and helping teams automate creation of SLSA/BCID policies to demonstrate protection from supply chain threats and regulatory compliance (i.e. EO 14028, EU CRA). I am interested in translating the complexities of the supply chain security to something understood and valued, and am also a maintainer of projects that produce and consume other supply chain data (i.e. SPDX, VEX, GUAC).
I would like to self-nominate for steering committee membership.
Name: Michael Lieberman
Organization: Kusari
Background: I am an early maintainer of SLSA. I built early SLSA tooling including an OpenSSF project called FRSCA. I have been involved heavily for the past several years. I also contribute to various open source projects and tools that work with SLSA or related in some way like GUAC, and Darnit. I bring the perspective both of a small team attempting to leverage SLSA internally as well as the perspective of a SaaS provider who is working with customers so they can both generate trustworthy SLSA attestations and also how to ingest those attestations for better software supply chain security outcomes.
I would like to self-nominate to run for steering committee membership.
Name: Michael Winser
Affiliation: Eclipse Foundation (also Alpha-Omega and XWind.io)
Background: I have been involved in SDLC and supply chain security and open source for years both during my time at Google and more recently with the Eclipse Foundation and Alpha-Omega (which I co-founded). I have been an active and vocal part of the SLSA working group for the past year and helped update our governance docs. During that time I have tried to bring a customer-centric perspective to the group's work.
Activity
michaelwinser commentedon Apr 20, 2026
Approved by the steering committee in the April 20th meeting.
arewm commentedon Apr 20, 2026
I would like to self-nominate to run for steering committee membership.
Name: Andrew McNamara
Affiliation: Red Hat
Background: I believe that SLSA has an important role in helping people with usable security. Reasoning about security and trust is hard, especially in the modern supply chain. My interest in this area combined with my involvement in a build platform built on top of SLSA provenance (konflux-ci.dev) and I have talked about this at many conferences. The lines around SDLC are only getting more complex and we are actively exploring how this will change our preconceived notions of security and trust.
tombedfordgit commentedon Apr 20, 2026
I would like to nominate myself for the SLSA steering committee
Name: Tom Bedford
Organisation: Bloomberg
Background: I help my organisation reduce SDLC-related risks. SLSA is quickly becoming a part of that, and I've found myself being able explain the risks and remediations well to a variety of user types - from CISO, CTO, individual engineers and legal/compliance. I am also a maintainer of the Dependency Track, which is in the progress of being drafted for SLSA, after I helped contribute it from the original 'S2C2F' specification.
lumjjb commentedon Apr 22, 2026
I would like to self-nominate to run for steering committee membership.
Name: Brandon Lum
Organization: Google
Background: I help teams at Google adopt SLSA, working with builders to achieve higher SLSA levels, and helping teams automate creation of SLSA/BCID policies to demonstrate protection from supply chain threats and regulatory compliance (i.e. EO 14028, EU CRA). I am interested in translating the complexities of the supply chain security to something understood and valued, and am also a maintainer of projects that produce and consume other supply chain data (i.e. SPDX, VEX, GUAC).
mlieberman85 commentedon Apr 27, 2026
I would like to self-nominate for steering committee membership.
Name: Michael Lieberman
Organization: Kusari
Background: I am an early maintainer of SLSA. I built early SLSA tooling including an OpenSSF project called FRSCA. I have been involved heavily for the past several years. I also contribute to various open source projects and tools that work with SLSA or related in some way like GUAC, and Darnit. I bring the perspective both of a small team attempting to leverage SLSA internally as well as the perspective of a SaaS provider who is working with customers so they can both generate trustworthy SLSA attestations and also how to ingest those attestations for better software supply chain security outcomes.
michaelwinser commentedon May 4, 2026
I would like to self-nominate to run for steering committee membership.
Name: Michael Winser
Affiliation: Eclipse Foundation (also Alpha-Omega and XWind.io)
Background: I have been involved in SDLC and supply chain security and open source for years both during my time at Google and more recently with the Eclipse Foundation and Alpha-Omega (which I co-founded). I have been an active and vocal part of the SLSA working group for the past year and helped update our governance docs. During that time I have tried to bring a customer-centric perspective to the group's work.
(yes, I copied this from last year)
arewm commentedon May 11, 2026
Yesterday was the last day for nominations. We have 5 seats and 5 nominations, so I think that that means we do not need to run the vote.
arewm commentedon May 11, 2026
@mlieberman85 , can you help to make adjustments to the maintainers/ownership?
Update steering committee for 2026 election