Incentivize maintainership: Increase say of maintainers in TC selection process

Open
#3,453 0 comments 4 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet

Research direction

The issue names no files, tests, or implementation entry points. Read the proposal and its dependency on #3441 first; done would require an agreed change to the Technical Committee selection process, not an implementation described here.

Written by the indexing model from the issue text.

Description

Proposal

Give maintainers more of a say in the selection of TC members. This could be accomplished in various ways, including (nonexhaustive list):

  • Making maintainers, or a subset of maintainers, directly vote for new TC members from a list pre-selected by the existing TC and/or the GC
  • Allow maintainers, or a subset of maintainers, to nominate themselves for TC positions
  • Establish a comment or consultation period to get feedback from maintainers or a subset of them about potential candidates.
  • Allow individual SIGs or groups of SIGs from different technical areas to, through their maintainers, nominate, propose or directly elect TC members

All of these could be for the whole TC or a subset of it ("maintainer-appointed seats").

This would depend on #3441.

Rationale

The Technical Committee is the highest technical decision-making body of the project. All SIGs that have to take technical decisions have to eventually interact with it. However, it can be hard for maintainers to understand the selection process of new members and how to get to it, and it can feel difficult to understand how to participate in its decision making,.

Currently, the selection process is done in private by existing TC members, in collaboration with the Governance Committee. To give maintainers more of a say and a clearer path towards the TC, it could be useful to reform this process and include maintainers in the conversation in a more explicit and direct way.

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.