Incentivize maintainership: Weighted maintainer votes in GC elections
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from open-telemetry/community
-
area/github-membership
Difficulty 1/5 Under an hour Newbie friendliness 1/100
open-telemetry/community#3847 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
open-telemetry/community#3846 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
open-telemetry/community#3844 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
open-telemetry/community#3823 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
open-telemetry/community#3821 · 3 comments ·
Maintainers usually reply within 1 day
All issues in open-telemetry/community
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Deltares/numba_celltree#100 · 1 comment ·
-
auto-reported bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
soup airgap-bundle --bundle-size-cap nan, inf or a cap above ~1.67e299 GiB stops with an internal ValueError/OverflowError (exit 1) instead of a usage errorPossibly taken @Keshemir claimed this today. Openbug claimed difficulty:2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MakazhanAlpamys/Soup#3045 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
dagster-io/skills#80 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day