Update language to make emeritus process clearer (#6339)

* update language to make emeritus process clearer

Signed-off-by: Davanum Srinivas <davanum@gmail.com>

* Update contributors/guide/owners.md

Co-authored-by: Bob Killen <killen.bob@gmail.com>

Co-authored-by: Bob Killen <killen.bob@gmail.com>

1 files changed, 15 insertions, 11 deletions

diff --git a/contributors/guide/owners.md b/contributors/guide/owners.md
index af20808a..fcd8887a 100644
--- a/contributors/guide/owners.md
+++ b/contributors/guide/owners.md
@@ -40,6 +40,8 @@ OWNERS files are in YAML format and support the following keys:
     Allows the use case where `a/deep/nested/OWNERS` file prevents `a/OWNERS` file from having any
     effect on `a/deep/nested/bit/of/code`
 - `reviewers`: a list of GitHub usernames or aliases that are good candidates to `/lgtm` a PR
+- `emeritus_approvers` a list of GitHub usernames of folks who were previously in the `approvers` section,
+   but are no longer actively approving code. please see [below](#emeritus) for more details.
 
 The above keys constitute a *simple OWNERS configuration*.
 
@@ -118,17 +120,19 @@ emeritus_approvers:
 #### Cleanup
 
 In addition to the Emeritus process above, from time to time, it is necessary
-to prune inactive members from OWNERS files. A core principle in maintaining a
-healthy community is encouraging active participation. OWNERS have a higher
-activity requirement, as they directly impact the ability of others to contribute.
-If an owner should become inactive, they will be removed but may be added back
-should they become active again.
-
-
-An inactive OWNER is defined as someone with less than 10 Devstats recorded
-contributions within the past year, as shown by this [dashboard]. This is a
-conservative metric but should ensure only the removal of the most inactive
-OWNERS.
+to prune inactive folks from OWNERS files. A core principle in maintaining a
+healthy community is encouraging active participation. Those listed in OWNERS files
+have a higher activity requirement, as they directly impact the ability of others
+to contribute. If anyone listed in OWNERS files should become inactive, here is
+what we will do:
+- if the person is in reviewers section, their GitHub id will be removed from the section
+- if the person is in approvers section, their GitHub id will be moved the `emeritus_approvers` section.
+
+
+An inactive person (listed in an OWNERS file) is defined as someone with less than
+10 Devstats recorded  contributions within the past year, as shown by this [dashboard].
+This is a  conservative metric but should ensure only the removal of the most inactive
+folks from a OWNERS file.
 - PR comments are less than 10 and Devstats count is less than 10 for a year