Incentivize maintainership: reduce load by promoting part-time maintainership
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
- documentation
Research direction
Start with the parent issue #3437 and the role definitions in guides/contributor/membership.md, especially the approver and maintainer sections linked here. Research how contribution risk, dependency updates, and approval requirements are currently handled. Done means an agreed, documented proposal for manageable maintainer roles and approval rules.
Written by the indexing model from the issue text.
Description
Sub-issue of #3437
There is a very steep gap between the responsibilities between approver and maintainer roles, which tends to force having the following:
- dedicated maintainer roles who spend most (if not all) their time in their maintainer role, which requires significant employer sponsorship and commitment
- approvers who do not have the capacity to be 100% dedicated to such responsibility
While most current proposals revolve around "making maintainer role more attractive", I think we should also aim to make it more manageable and also more accessible for the contributors who can't dedicate 100% of their time.
The main idea here would be to find a way to split the overall maintainer role into more limited and manageable pieces by:
- introduce a way to label contributions in their quality and approval requirements.
- introduce an intermediate "limited maintainer" role that grants the ability to handle basic chores like dependency update PRs
- require multiple maintainer approvals for high impact changes or core elements.
- 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