Files
my-rook-config/CODE-OWNERS
T
Travis Nielsen f5c394aa3a governance: yugabytedb members are reviewers instead of approvers
There was a typo in the approvers list. The YugabyteDB members
don't yet have push access to the repo as approvers. The intention
was to start with reviewer access.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
2020-05-27 15:09:32 -06:00

37 lines
977 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
reviewers:
- satoru-takeuchi
- Madhu-1
edgefs:
approvers:
- dyusupov
reviewers:
- sabbot
cassandra:
approvers:
- yanniszark
nfs:
reviewers:
- rohan47
yugabytedb:
reviewers:
- Arnav15
- samkulkarni20