Clarify maintainer role

* Link to approver description for k8s aprovers
* Mention that a maintainer's approval of a pull request means that it
can be merged. Either with our current process (the maintainer clicks
the merge button) or once we finish moving to prow, the end  result is
the same (merge on approval when other checks are successful).
This commit is contained in:
Carolyn Van Slyck 2018-07-13 12:46:01 -05:00
parent b26a55fc96
commit d037dad559
No known key found for this signature in database
GPG Key ID: 1C91EA2338067CBF
1 changed files with 3 additions and 2 deletions

View File

@ -29,8 +29,9 @@ The following, non-exhaustive, items are out of scope:
## Roles
- Maintainers
- Maintainer is equivalent to the standard Kubernetes definition of Approver.
- Responsible for approving, and reviewing, pull requests.
- Maintainer is equivalent to the standard [Kubernetes definition of
Approver](https://github.com/kubernetes/community/blob/master/community-membership.md#approver).
- Responsible for reviewing pull requests, and approving pull requests for merge.
- Responsible for technical planning and stewardship of the project.
- New maintainers may be nominated by a chair, and accepted via lazy
two-thirds resolution amongst the chairs.