Incentivize maintainership: Formalize which teams are maintainers
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
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github
- Domain
- developer-experience
Research direction
Start with workstreams.yml and review its SIG entries, then reconcile them against the 73 GitHub teams whose names end in -maintainers. Define the authoritative maintainer team for each relevant SIG, identify stale or redundant teams, and update the mapping so governance scope and repository ownership are auditable.
Written by the indexing model from the issue text.
Description
Parent issue: Incentivize maintainership for long-term project health
Proposal
Establish a formal definition of which GitHub teams represent maintainers, codified in workstreams.yml.
Today, there are 73 GitHub teams with names ending in -maintainers, but there is no authoritative mapping between these teams and the SIGs defined in workstreams.yml. Some teams were created for projects that never materialized, some are redundant due to parent-child relationships, and other various quirks.
If we're going to tie governance rights to maintainer status — voting weight, project proposal roles, roadmap participation — we need a clear, auditable answer to "who is a maintainer?"
Why workstreams.yml
workstreams.yml is already the source of truth for how the project organizes its work. Each SIG entry includes its people (GC liaison, TC sponsors), meetings, Slack channels, and repositories. It's the natural place to also declare which GitHub team represents maintainers for each SIG.
This would extend each SIG entry with something like:
- id: java-sdk-instrumentation
kind: sig
...
people:
- gcLiaison: trask
- tcSponsor:
username: jack-berg
level: leading
- maintainerTeam: java-maintainers # <-- new
resources:
- repository: open-telemetry/opentelemetry-java
...
What this enables
- Clear governance scope. When a process says "maintainers vote on X," we know exactly which teams and people that includes.
- Auditable membership. workstreams.yml is version-controlled and reviewed via PR, unlike ad hoc GitHub team creation.
- Repository ownership. Formalizing the relationship between SIGs, their maintainer teams, and their repositories in one place.
- Cleanup opportunity. Forces us to reconcile the 73 existing
-maintainersteams against the actual SIG structure and identify teams that are stale, redundant, or misclassified.
- 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
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
docling-project/docling-pipelines#669 ·
Maintainers usually reply within 1 day
-
blocked kind/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opendatahub-io/agent-eval-harness#329 · 2 comments · 1 reaction ·
-
cc_wrapper crashes with ValueError on Windows when a path is on another drivePossibly taken @TrapsterDK claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
tweag/rules_haskell#2492 ·
Maintainers usually reply within 1 day