17 lines
703 B
Markdown
17 lines
703 B
Markdown
|
|
||
|
|
This document describes basic expectations for maintainers. To become a maintainer, start taking on these responsibilities. Consistent contributors then discuss with existing maintainers to become the official [MAINTAINERS](./MAINTAINERS).
|
||
|
|
|
||
|
|
### Top-level maintainer
|
||
|
|
|
||
|
|
- Running the etcd release processes
|
||
|
|
- Ownership of test and debug infrastructure
|
||
|
|
- Resolve or redirect issues to keep the issue count low (goal: under 100)
|
||
|
|
- Regularly review pull requests across all pkgs
|
||
|
|
- Providing cross pkg design review
|
||
|
|
|
||
|
|
### Package/feature maintainer
|
||
|
|
|
||
|
|
- Ownership of test and debug failures in a pkg/feature
|
||
|
|
- Resolution of bugs triaged to a package/feature
|
||
|
|
- Regularly review pull requests to the pkg subsystem
|