Skip to content

Commit a9be8ff

Browse files
Trottaddaleax
authored andcommitted
doc: minimal documentation for Emeritus status
Include a high-level explanation of how Collaborators are identified for Emeritus status. This is intended to supply the minimum amount of information to being assigning Emeritus status to inactive Collaborators. The documentation may be expanded subsequently. PR-URL: #13421 Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
1 parent 2778256 commit a9be8ff

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

GOVERNANCE.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -67,9 +67,9 @@ Typical activities of a Collaborator include:
6767
* participation in working groups
6868
* merging pull requests
6969

70-
While the above are typical things done by Collaborators, there are no required
71-
activities to retain Collaborator status. There is currently no process by which
72-
inactive Collaborators are removed from the project.
70+
The CTC periodically reviews the Collaborator list to identify inactive
71+
Collaborators. Past Collaborators are typically given _Emeritus_ status. Emeriti
72+
may request that the CTC restore them to active status.
7373

7474
## CTC Membership
7575

0 commit comments

Comments
 (0)