@@ -40,6 +40,8 @@ OWNERS files are in YAML format and support the following keys:
40
40
Allows the use case where ` a/deep/nested/OWNERS ` file prevents ` a/OWNERS ` file from having any
41
41
effect on ` a/deep/nested/bit/of/code `
42
42
- ` 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.
43
45
44
46
The above keys constitute a * simple OWNERS configuration* .
45
47
@@ -118,17 +120,19 @@ emeritus_approvers:
118
120
# ### Cleanup
119
121
120
122
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.
132
136
- PR comments are less than 10 and Devstats count is less than 10 for a year
133
137
134
138
0 commit comments