Skip to content

Commit 09bdced

Browse files
dimsmrbobbytables
andauthored
Update language to make emeritus process clearer (#6339)
* update language to make emeritus process clearer Signed-off-by: Davanum Srinivas <[email protected]> * Update contributors/guide/owners.md Co-authored-by: Bob Killen <[email protected]> Co-authored-by: Bob Killen <[email protected]>
1 parent 0e01b12 commit 09bdced

File tree

1 file changed

+15
-11
lines changed

1 file changed

+15
-11
lines changed

contributors/guide/owners.md

Lines changed: 15 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,8 @@ OWNERS files are in YAML format and support the following keys:
4040
Allows the use case where `a/deep/nested/OWNERS` file prevents `a/OWNERS` file from having any
4141
effect on `a/deep/nested/bit/of/code`
4242
- `reviewers`: a list of GitHub usernames or aliases that are good candidates to `/lgtm` a PR
43+
- `emeritus_approvers` a list of GitHub usernames of folks who were previously in the `approvers` section,
44+
but are no longer actively approving code. please see [below](#emeritus) for more details.
4345

4446
The above keys constitute a *simple OWNERS configuration*.
4547

@@ -118,17 +120,19 @@ emeritus_approvers:
118120
#### Cleanup
119121

120122
In addition to the Emeritus process above, from time to time, it is necessary
121-
to prune inactive members from OWNERS files. A core principle in maintaining a
122-
healthy community is encouraging active participation. OWNERS have a higher
123-
activity requirement, as they directly impact the ability of others to contribute.
124-
If an owner should become inactive, they will be removed but may be added back
125-
should they become active again.
126-
127-
128-
An inactive OWNER is defined as someone with less than 10 Devstats recorded
129-
contributions within the past year, as shown by this [dashboard]. This is a
130-
conservative metric but should ensure only the removal of the most inactive
131-
OWNERS.
123+
to prune inactive folks from OWNERS files. A core principle in maintaining a
124+
healthy community is encouraging active participation. Those listed in OWNERS files
125+
have a higher activity requirement, as they directly impact the ability of others
126+
to contribute. If anyone listed in OWNERS files should become inactive, here is
127+
what we will do:
128+
- if the person is in reviewers section, their GitHub id will be removed from the section
129+
- if the person is in approvers section, their GitHub id will be moved the `emeritus_approvers` section.
130+
131+
132+
An inactive person (listed in an OWNERS file) is defined as someone with less than
133+
10 Devstats recorded contributions within the past year, as shown by this [dashboard].
134+
This is a conservative metric but should ensure only the removal of the most inactive
135+
folks from a OWNERS file.
132136
- PR comments are less than 10 and Devstats count is less than 10 for a year
133137

134138

0 commit comments

Comments
 (0)