| |
@@ -148,3 +148,13 @@
|
| |
|
| |
For the current list of active SIGs, refer to
|
| |
[http://wiki.centos.org/SpecialInterestGroup](http://wiki.centos.org/SpecialInterestGroup)
|
| |
+
|
| |
+ ## Retiring a SIG
|
| |
+
|
| |
+ If a SIG misses two of their quarterly reports in a row: then the community manager should contact the members listed in the account system. More than a single attempt at contact should be made. If the SIG responds they can be correctly categorized. If they do not respond within 45 days, they can be considered inactive.
|
| |
+
|
| |
+ If the SIG (a) fails to respond, (b) responds that the SIG completed the work it intended and no further work is required, or (c) responds that they’ve decided to abandon the effort - the following actions should be performed.
|
| |
+
|
| |
+ (1) An announcement should be sent to CentOS Devel indicating the SIG is reaching end of life. If members believe they can re-energize the SIG, this would be the time to stop the retirement.
|
| |
+ (2) A board ticket should be opened for notification purposes only so the board can track if suddenly a bunch of SIGs drop off.
|
| |
+ (3) A ticket should be opened with Infra to archive the SIG materials. Steps should be taken to account for both the desire to credit past members with their work and those members who wish to be de-listed from the archive.
|
| |
