Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
72 changes: 72 additions & 0 deletions elections/2026/nomination-template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,72 @@
-------------------------------------------------------------
name: Full Name
ID: GitHubID
info:
employer: Your employer or "Independent"
affiliation: Other organizations you contribute on behalf of (or "None")
-------------------------------------------------------------

<!--
Please copy this template to "candidate-<githubid>.md" in this directory and
fill out each section below.

Reminders, per https://github.com/prometheus/governance/blob/main/GOVERNANCE.md:
- You must be an Organization Member in good standing per ROLES.md to run.
- No more than 2 seats may be held by employees or contractors of the same
organization. Please be accurate about your employer and any other
affiliations that materially direct your Prometheus work — this matters for
how votes resolve under the company-cap rule.
- Terms are 2 years, staggered. There are no term limits.
-->

## Eligibility

- [ ] I have read the
[Governance document](https://github.com/prometheus/governance/blob/main/GOVERNANCE.md)
and the
[Code of Conduct](https://github.com/prometheus/docs/blob/main/code-of-conduct.md),
and agree to uphold them if elected.

## Teams

<!--
List the Prometheus teams and sub-projects you are a member of, and your role
(member, maintainer, team lead). See https://prometheus.io/community/ and the
team files under https://github.com/prometheus/docs.
-->
Comment on lines +32 to +36
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: I think sub-projects and team files mentioned here don't really exist, do they?


-

## What I have done

<!--
A narrative of your contributions to Prometheus and the wider ecosystem. Useful
things to cover:
- How long you have been contributing and in which areas (server, TSDB,
Alertmanager, client libraries, exporters, PromQL, remote-write, docs,
community, releases, security, infrastructure, etc.).
- Notable design proposals, features, or refactors you led or shepherded.
- Cross-project work (OpenMetrics, OpenTelemetry, CNCF, downstream projects).
- Community-facing work: mentoring, conference talks, dev summits, triage,
release management, incident response.

Concrete links beat adjectives.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏽

-->

## What I'll do

<!--
Your platform. What do you see as the most important things for Prometheus
over the next 2 years, and what specifically would you push on as a Steering
Committee member? Steering scope is governance, project health, and
cross-team coordination — not setting technical direction inside teams. Be
specific about what you would actually do.
-->

## Resources about me

- GitHub: [@GitHubID](https://github.com/GitHubID)
- Talks / writing:
-
- Social / contact:
-
202 changes: 202 additions & 0 deletions elections/2026/steering-committee-election.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,202 @@
# Prometheus 2026 Bootstrap Steering Committee election

This document lays out the 2026 Bootstrap Steering Committee election process
per the Prometheus [Governance document](../../GOVERNANCE.md). This is the
**bootstrap election** described in
[Migrating from the old governance](../../GOVERNANCE.md#migrating-from-the-old-governance):
it elects all 7 seats at once, after which the new governance comes into
effect.

The 3 highest-voted candidates will serve **2-year terms**; the next 4 will
serve **1-year terms** to establish the staggered cycle.

Election schedule:

* **14 May 2026** — call for nominations opens; voters list published; this
document announced
* **4 June 2026 23:59 UTC** — final deadline to submit nominations
* **8 June 2026** — official nominees list published; deadline to request a
voter eligibility review
* **11 June 2026 to 25 June 2026** — voting takes place
* **2 July 2026** — results announced; new Steering Committee seated;
governance comes into effect

We highly encourage participation in this election cycle to ensure that the
community is well-represented by the Steering Committee.

# TL;DR

* If you are willing to nominate yourself: read the
[Governance document](../../GOVERNANCE.md) and confirm you are ready for the
commitment. Submit a candidate page based on the
[nomination template](./nomination-template.md) before 4 June 2026 23:59
UTC.
* If you are an active community member: confirm that you are on the
[voters list](./voters-list/write-access.csv), or request a review via
[this form](https://forms.gle/tasSbJ9cQdsfj5GV9) before 8 June 2026 23:59
UTC if you believe you should be eligible but are not listed.
* Vote between 11 June 2026 and 25 June 2026 23:59 UTC using the link the
Election Officers will send to eligible voters.
* Keep being awesome and contributing to the project!

# Vacancies

There is no sitting Steering Committee — the new governance comes into effect
once this bootstrap election concludes. **All 7 seats are up for election in
this cycle.**

Per the
[migration section of the Governance document](../../GOVERNANCE.md#migrating-from-the-old-governance):

* The 3 highest-voted candidates will serve **2-year terms** (until the
regular 2028 election).
* The next 4 highest-voted candidates will serve **1-year terms** (until the
regular 2027 election), establishing the staggered cycle.

# Voting process

Anyone can track the 2026 election process via the election announcements
issue (TBD — to be opened in
[prometheus/governance](https://github.com/prometheus/governance/issues) by
the Election Officers; questions and progress updates will live there).

Per the migration section of the Governance document, the Election Officers
for the bootstrap are picked by the existing Prometheus team members (rather
than by a Steering Committee, since none exists yet). For this election they
are:

* **Arianna Vespri** ([@vesari](https://github.com/vesari))
* **Goutham Veeramachaneni** ([@gouthamve](https://github.com/gouthamve))
* **Joe Adams** ([@sysadmind](https://github.com/sysadmind))

All three are Organization Members in good standing, are eligible to vote,
are not running in this election, and have made a public promise of
impartiality.

We strive for transparency in the election process and hold the community's
interests as our priority. All documents and assets related to the 2026
election process will be public, and notes for any meetings held as part of
this process will be recorded and distributed.

Per the [Governance document](../../GOVERNANCE.md#voting-procedure),
elections are held using a ranked **Condorcet** voting method. For this
election the Election Officers have selected
[CIVS](https://civs1.civs.us/) (Condorcet Internet Voting Service), using
**Condorcet with Instant Runoff Voting (IRV) as the tie-breaker**. CIVS
supports ranked Condorcet ballots and provides standard tie-breaking via IRV;
voting is private (no individual's vote is revealed).

# Nominations

Per [the Governance document](../../GOVERNANCE.md#candidate-eligibility),
Organization Members eligible to vote may stand for election. **Candidates
must self-nominate.** There are no term limits.

To nominate yourself, copy [`nomination-template.md`](./nomination-template.md)
to `candidate-<githubid>.md` in this directory, fill it out, and submit it as
a Pull Request to the
[prometheus/governance](https://github.com/prometheus/governance) repository
before **4 June 2026 23:59 UTC**.

The template asks for:

* Full name and GitHub ID
* Employer and any other affiliations that materially direct your Prometheus
work (this matters for the company-cap rule below)
* An eligibility checkbox confirming you have read the Governance document
and the Code of Conduct
* The Prometheus teams and sub-projects you are a member of
* A narrative of what you have done and what you would push on as a Steering
Committee member
* Links so voters can learn more about you

Nominees should also send a preferred contact email address to the Election
Officers — it will be kept private and used only for candidate communications
as the election process proceeds. Contact via the email addresses listed on
the Election Officers' GitHub profiles, or by tagging all three on the
nomination PR.

# Voter Eligibility

All [Organization Members](../../ROLES.md#member) are eligible to vote. The
voter roll for this election is captured under [`voters-list/`](./voters-list/)
in this directory:

* [`write-access.csv`](./voters-list/write-access.csv) — canonical voter
list, derived from accounts with write access across the
[prometheus](https://github.com/prometheus) and
[prometheus-community](https://github.com/prometheus-community) GitHub
organizations.
* [`write-access-raw.csv`](./voters-list/write-access-raw.csv) — full
per-org / per-repo provenance behind the canonical list.
* [`manifest.json`](./voters-list/manifest.json) — record of every API call
used to assemble the list, with timestamps and counts.
* [`main.go`](./voters-list/main.go) (with `go.mod` / `go.sum`) — the
`collect-write-access` tool used to generate the lists, so anyone can
reproduce the result.

Per the migration section of the Governance document, eligibility for the
bootstrap election may include members and maintainers who are inactive
under the regular activity requirements; that is intentional, and they may
still participate in this vote.

If you believe you should be eligible to vote but are not on the list,
please submit an eligibility review request via this form:
[https://forms.gle/tasSbJ9cQdsfj5GV9](https://forms.gle/tasSbJ9cQdsfj5GV9),
before **8 June 2026 23:59 UTC**. Eligibility review requests are private;
only the Election Officers will have access to this information.

# Vote

Voting will be conducted via [CIVS](https://civs1.civs.us/) using ranked
Condorcet with IRV tie-breaking. Eligible voters listed in
[`write-access.csv`](./voters-list/write-access.csv) will receive a unique
voting link by email at the address associated with their GitHub account (or
the address provided through the eligibility-review process).

Each voter ranks the candidates in order of preference. CIVS computes the
Condorcet winner(s) and uses IRV to break any cycles or ties.

The Election Officers will accept late requests to re-send the voting link.
We encourage pre-registration via the eligibility-review process to minimize
the effort required to run this election.

Voting is private: nobody — including the Election Officers — will know any
individual's vote.

# Results

Voting will close at **25 June 2026 23:59 UTC**. The Election Officers will
publish the full CIVS results, then apply the company-representation cap.

Per the
[Governance document](../../GOVERNANCE.md#limitations-on-company-representation),
no more than 2 seats may be held by employees or contractors of the same
organization (or conglomerate). If the raw ranking would result in more than
2 people from the same organization being seated, the lowest-ranked
candidate(s) from that employer are skipped until representation is at most
2.

Once the 7-seat slate is finalized:

* The **top 3** by Condorcet ranking serve **2-year terms** (through the
regular 2028 election cycle).
* The **next 4** serve **1-year terms** (through the regular 2027 election
cycle).

Results will be announced by **2 July 2026** (within 1 week of voting close).
On that date the new Steering Committee is seated, the
[Committee members](../../GOVERNANCE.md#committee-members) table in
GOVERNANCE.md will be filled in by PR, and the new governance comes into
effect.

# Schedule

| Date | Activity |
|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|
| 14 May 2026 | This document announced; call for nominations opens; voters list published; announced via [prometheus-developers](https://groups.google.com/g/prometheus-developers) and [prometheus-users](https://groups.google.com/g/prometheus-users) |
| 4 June 2026 23:59 UTC | End of call for nominations |
| 8 June 2026 | List of nominees finalized and announced; deadline to request a voter eligibility review |
| 11 June 2026 | Voting period begins (CIVS links sent) |
| 25 June 2026 23:59 UTC | Voting ends |
| 2 July 2026 | Results announced; new Steering Committee seated; governance comes into effect |
8 changes: 8 additions & 0 deletions elections/2026/voters-list/go.mod
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
module collect-write-access

go 1.25

require github.com/google/go-github/v66 v66.0.0

require github.com/google/go-querystring v1.1.0 // indirect

9 changes: 9 additions & 0 deletions elections/2026/voters-list/go.sum
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
github.com/google/go-cmp v0.5.2/go.mod h1:v8dTdLbMG2kIc/vJvl+f65V22dbkXbowE6jgT/gNBxE=
github.com/google/go-cmp v0.6.0 h1:ofyhxvXcZhMsU5ulbFiLKl/XBFqE1GSq7atu8tAmTRI=
github.com/google/go-cmp v0.6.0/go.mod h1:17dUlkBOakJ0+DkrSSNjCkIjxS6bF9zb3elmeNGIjoY=
github.com/google/go-github/v66 v66.0.0 h1:ADJsaXj9UotwdgK8/iFZtv7MLc8E8WBl62WLd/D/9+M=
github.com/google/go-github/v66 v66.0.0/go.mod h1:+4SO9Zkuyf8ytMj0csN1NR/5OTR+MfqPp8P8dVlcvY4=
github.com/google/go-querystring v1.1.0 h1:AnCroh3fv4ZBgVIf1Iwtovgjaw/GiKJo8M8yD/fhyJ8=
github.com/google/go-querystring v1.1.0/go.mod h1:Kcdr2DB4koayq7X8pmAG4sNG59So17icRSOU623lUBU=
golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=

Loading