forked from rook/rook
Travis Nielsen
81ae4b66d3
Add a steering committee to the Rook governance to oversee the project and provide direction. Maintainers will still have push access to the project. The steering committee are the ones with the votes for conflict resolution. Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
34 lines
926 B
Plaintext
34 lines
926 B
Plaintext
# Code ownership file that specifies maintainers and reviewers for all areas of the Rook codebase.
|
|
# all: These members have the given role for all areas of the codebase.
|
|
# Specific storage provider ownership and covers all portions of code that is specific to their project.
|
|
# Maintainers have push access to merge PRs after approved by another maintainer or reviewer.
|
|
# With the intention of using the Prow bot in the future, the term "approver" is used below.
|
|
# An approver is equivalent to a Rook maintainer for all intents and purposes as described in the Rook governance.
|
|
|
|
areas:
|
|
all:
|
|
approvers:
|
|
- travisn
|
|
- galexrt
|
|
- jbw976
|
|
ceph:
|
|
approvers:
|
|
- travisn
|
|
- BlaineEXE
|
|
- leseb
|
|
edgefs:
|
|
approvers:
|
|
- dyusupov
|
|
reviewers:
|
|
- sabbot
|
|
cassandra:
|
|
approvers:
|
|
- yanniszark
|
|
nfs:
|
|
reviewers:
|
|
- rohan47
|
|
yugabytedb:
|
|
approvers:
|
|
- Arnav15
|
|
- samkulkarni20
|