@@ -48,12 +48,16 @@ permissions for /lgtm as well as /approve.
4848
4949### Implementation Details/Notes/Constraints
5050
51- In order to make the change, we need to review the OWNERS file(s) in
52- each repository and update them to include a list of reviewers. We
53- have [ a process for approval permission] ( ../maintainers ) but that does
54- not apply to reviewers. We should give reviewer permission more easily
55- than approver permission, as a way to grow our teams without friction,
56- so we're going to want to have a separate process for that.
51+ In order to make the change, we need to review the ` OWNERS_ALIASES `
52+ file(s) in each repository and update them to include the appropriate
53+ list of reviewers. The ` OWNERS ` files in each repository will
54+ reference these aliases, which contain the actual usernames for
55+ reviewers and approvers. We have
56+ [ a process for approval permission] ( https://github.com/metal3-io/community/blob/main/maintainers/README.md ) ,
57+ but that does not apply to reviewers. We should give reviewer
58+ permission more easily than approver permission, as a way to grow our
59+ teams without friction, so we're going to want to have a separate
60+ process for that.
5761
5862If we focus on the transition for now, we can define that process
5963separately later. So, I propose that we take the contributors with 10
0 commit comments