Create a list of community admin tasks

This list ingests the sysadmin.md in the root and puts under SIG
Contributor Experience, which is generally responsible for these tasks.

2 files changed, 75 insertions, 36 deletions

diff --git a/sig-contributor-experience/community-maintenance.md b/sig-contributor-experience/community-maintenance.md
new file mode 100644
index 00000000..d47b0463
--- /dev/null
+++ b/sig-contributor-experience/community-maintenance.md
@@ -0,0 +1,75 @@
+# Community Maintenance 
+
+This document outlines maintenance tasks that SIG Contributor Experience should be doing on a regular basis.
+Copy this list into a new Github issue, for example "Community Maintenance Tasks for 2Q 2018". 
+Then people can volunteer to audit different parts of the project at once. 
+These tasks should be done at a _minimum of twice a year_, but ideally once a quarter.
+
+If any of these tasks can be automated, then do so, however most of these require a human to make a judgement decision. 
+If you find that any one person is in charge of a resource it is your responsibility to bring this issue to SIG Contributor Experience so that important parts of Kubernetes infrastructure are not assigned to one sole person. 
+
+### Slack
+
+- [ ] Channels - Anything out of place or not following the guidelines? 
+  - [ ] Close unused channels. 
+  - [ ] Check to see if there is a purpose, pinned documents like agendas, and other best practices being used in the channel. These are not required but are useful.
+- [ ] Audit the Integrations and apps
+- [ ] Audit the user tokens
+- [ ] Audit the Emojis
+- [ ] Generate a Slack data report to share with the community (optional)
+
+### GitHub
+
+- [ ] Audit Org admin permissions
+- [ ] Audit Integrations
+- [ ] Check Label usage (education, deprecation, etc)
+- [ ] Is the PR and/or issue message still good/the best?
+- [ ] Check kubernetes/community/.github/PULL_REQUEST_TEMPLATE
+- [ ] Where’s the issue template located? 
+
+### Calendars
+
+- [ ] Check that the calendar works
+  - Go to http://k8s.io/community and follow the flow
+- [ ] Make sure all SIG, WG, and other community meetings are showing - especially check new groups that were created in the last quarter
+- [ ] Make sure that invites have more than one owner, shared with the mailing list distro, and have an agenda attached plus zoom URL and telephone dial information.
+
+### SIGS
+
+- [ ] Ensure everyone in `sigs.yaml` is subscribed to sigs-leads mailing list
+- [ ] Ensure that chairs and leads are accurate in the `sigs.yaml`
+
+### YouTube
+
+- [ ] Check sharing on all the playlists
+  - Should only be shared with leads or people appointed by leads
+  - Either remove other people or regenerate a new collaboration URL
+- [ ] Check admin permissions on the Kubernetes account
+- [ ] Fix any videos accidentally tagged as unlisted 
+- [ ] Generate a YouTube traffic report to share with the community (optional)
+
+### Zoom
+
+- [ ] Ensure leads have access to their upgraded Zoom account
+- [ ] If appropriate change the password if a SIG has changed leadership 
+  - Contact CNCF to adjust upgraded licenses if necessary
+- [ ] Audit kubernetes.io GSuite - this is primarily needed to create associated resources like GoogleGroups and the Google Cloud organization.  Accounts in  this domain cost the CNCF actual money, so are not available for individuals. Three steering committee members will hold the keys to three accounts on the domain, which can be used to create `@kubernetes.io` groups as needed.
+  - Volunteers (Ask for new representatives from the steering committee if election turnover affects this list):
+    - Joe Beda (@jbeda)
+    - Brendan Burns (@brendandburns)
+    - Tim Hockin (@thockin)
+
+### Properties Managed by the CNCF
+
+The CNCF provides support to Kubernetes for the following properties, you do not need to check them, however members of SIG Contributor Experience should have a working relationship with the administrators of the following properties:
+
+- Twitter
+- Blog
+- GCP Organization
+
+### Unknown State
+
+Properties we should learn how to maintain, or at least document:
+
+- Kubernetes.io DNS
+- Kubernetes.io URL redirector
diff --git a/sysadmin.md b/sysadmin.md
deleted file mode 100644
index ba1f6dd1..00000000
--- a/sysadmin.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# Administering Kubernetes Systems
-
-The Kubernetes community is supported by many systems - things like the
-website, groups, test infrastructure, github bots, and so forth.  The
-administration of these resources should be a volunteer effort and should be
-equally available to anyone in our community.
-
-As of July 2017 this effort has just begun.  This document will detail what
-resources are available for community ownership and who is currently
-responsible for them.
-
-## Community managed
-
-* kubernetes.io GSuite - this is primarily needed to create associated
-  resources like GoogleGroups and the Google Cloud organization.  Accounts in
-  this domain cost the CNCF actual money, so are not available for individuals.
-  Three steering committee members will hold the keys to three accounts on the
-  domain, which can be used to create `@kubernetes.io` groups as needed.
-  Volunteers:
-  * Joe Beda (@jbeda)
-  * Brendan Burns (@brendandburns)
-  * Tim Hockin (@thockin)
-
-## Not yet community managed
-
-* Twitter
-* Google+
-* Blog
-* Slack
-* GCP Organization
-* Kubernetes.io DNS
-* Kubernetes.io URL redirector
-* Github bots
-* Test infrastructure
-* reviewable.kubernetes.io
-* ...