envoyproxy/gateway

Decision: Mechanisms for adding and removing maintainers

Open

#144 opened on Jul 7, 2022

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (802 forks)auto 404
help wanted

Repository metrics

Stars
 (2,871 stars)
PR merge metrics
 (PR metrics pending)

Description

Once we've resolved #143 and have agreed on a voting mechanism, we need to write down the process for adding (and removing, but adding is more relevant) maintainers.

What are the criteria for becoming a maintainer? What's the process? Under what circumstances should a maintainer be removed? What's the process there?

There are definitely further things to discuss, about maintainer diversity on the company and other levels, how big we want the maintainer pool to get, and so on. Those feel like Steering-level issues though, so once we've agreed on the process here, I'll raise another issue and we can discuss it at Steering, and get recommendations from there.

Contributor guide

Research direction
Investigate the project's current governance model and discuss criteria and process for adding/removing maintainers based on community input and existing discussions.
Tech stack
None
Domain
documentationdeveloper experience
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30