Incentivize maintainership: Increase say of maintainers in TC selection process
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
- Domain
- developer-experience
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
- 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