Incentivize maintainership: Formalize which teams are maintainers

Open
#3,441 5 comments 0 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
Mostly clear
Activity status
Quiet
Tech stack
github

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 -maintainers teams 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

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.