Incentivize maintainership: Weighted maintainer votes in GC elections

Open
#3,440 8 comments 5 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Domain
documentation

Research direction

Start with the parent issue and governance-charter.md, then review the current Governance Committee election rules. Resolve the open question about the weighting structure and define how maintainer eligibility and weighted ballots would work. Done means the proposal has a decided, documented scope rather than unresolved alternatives.

Written by the indexing model from the issue text.

Description

Parent issue: Incentivize maintainership for long-term project health

Proposal

Give maintainer votes additional weight in Governance Committee elections. For example, maintainer votes could count as 2, while all other eligible voters get 1.

Rationale

Today, GC elections use a straight democratic model where every Member of Standing gets one vote. The eligibility bar for Member of Standing is 20 contributions in the prior year. This puts casual contributors on equal footing with the people who are load-bearing: doing releases, triaging issues, reviewing PRs, handling security advisories, mentoring new contributors, and all the other unglamorous continuous work that keeps the project running.

All contributions matter, but not equally so. A maintainer who has committed to the sustained, high-trust work of keeping a SIG healthy has a deeper stake in project governance than someone who has made 20 comments. Weighting their votes accordingly recognizes that difference and creates a tangible incentive to take on the maintainer role.

Scope

This proposal applies to GC elections only — not to GC internal decision-making, TC selection, or other votes.

Open questions

  • What's the right weight structure? 2x is one option, but there are other approaches worth considering.
Dominant language
Python
Stars
1.2k
Forks
326
Avg merge
1d 12h
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-telemetry/community

All issues in open-telemetry/community

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.