Move K8sYoutubeCollaboration.md to youtube-guidelines.md

4 files changed, 55 insertions, 52 deletions

diff --git a/communication/K8sYoutubeCollaboration.md b/communication/K8sYoutubeCollaboration.md
index eec69b96..f9400682 100644
--- a/communication/K8sYoutubeCollaboration.md
+++ b/communication/K8sYoutubeCollaboration.md
@@ -1,43 +1,3 @@
-## Kubernetes Youtube Channel Collaboration 
+This file has moved to https://git.k8s.io/community/communication/youtube-guidelines.md.
 
-
-### Meeting Playlists
-
-
-The [Kubernetes Youtube Channel](https://www.youtube.com/channel/UCZ2bu0qutTOM0tHYa_jkIwg) has separate playlists for each SIG’s meeting recordings, as well as recordings of other meetings (i.e. Cloud Native, Kubernetes Community meetings). 
-
-To better serve the community, we have set up [collaboration](https://support.google.com/youtube/answer/6109639) on these playlists, so that anyone with the appropriate link to the particular playlist can upload videos *to that particular playlist* (links & playlists are 1:1).
-
-Each SIG playlist’s link will be shared with the SIG’s leadership, and other playlists' links (i.e. Cloud Native) will be shared with the appropriate point(s) of contact. The SIG playlist links will be sent to the official SIG lead Google Groups. 
-
-### Uploading Guidelines for Collaborators
-
-Collaboration should simplify things for everyone, but with privilege comes responsibility :). We assume all playlist collaborators in the community will use things fairly and appropriately, subject to the guidelines below:
-
-1. Once collaboration is setup for each meeting recording playlist, the upload responsibility will fall on the SIG leaders or other appropriate point(s) of contact.  Community managers *will only be escalation for issues with those playlists*
-
-2. Please post only related content (mostly meeting recordings) in the appropriate playlists 
-	- Posting of any exceedingly inappropriate content (i.e. NSFW content) will result in ***immediate*** suspension of privileges 
-
-3. Please ensure all videos have the same naming format, which is:
-	- Kubernetes [Name of Playlist’s Group] YYYYMMDD
-		- i.e. Kubernetes SIG Service Catalog 20161129
-
-4. All playlists need to be organized chronologically for ease of use, which is most easily done by selected “date added, newest” as the “Ordering” option in the playlist settings
-
-5. Please do not remove any already-published content from the playlists without checking with the community managers 
-
-6. For any small issues that arise (i.e. improper naming / ordering), you may be asked by the community managers to attempt to resolve the issue yourselves
- 
-7. Any egregious or habitual violation* of the above rules will result in suspension of collaboration privileges for the particular individual, or for the entire playlist if the individual can’t be identified
-	- If an individual is suspended, the playlist link will be remade and the new link will be shared with the non-offending individuals 
-	- If *playlist* collaboration is suspended, uploading by community managers to the playlist of interest will ***not*** be a priority, and will likely occur on a delayed basis
-	- *Note that "habitual violation" means "more than 3 issues per quarter"
-
-### Permissions for G Suite Accounts
-
-- If you're using a G Suite account you might need to loosen the permissions in your YouTube settings. See [this help article](https://support.google.com/a/answer/6212415) for more information. 
-
-Your community managers are happy to help with any questions that you may have and will do their best to help if anything goes wrong. Please get in touch via [SIG Contributor Experience](https://git.kubernetes.io/community/sig-contributor-experience).
-
-- Check the [centralized list of administrators](./moderators.md) for contact information.
+This file is a placeholder to preserve links. Please remove after 2019-06-12.
diff --git a/communication/moderation.md b/communication/moderation.md
index 0dc4896a..440d94cd 100644
--- a/communication/moderation.md
+++ b/communication/moderation.md
@@ -118,7 +118,7 @@ Moderators _MUST_:
   Kubernetes communication channels.
 - Make yourself generally available during working hours in your time zone for moderation.
   - This can be handled as a group so that there is enough coverage of people to allow for absences/travel.
-  - Ensure you are on #slack-admins during work hours and notifications are set appropriately. 
+  - Ensure you are on #slack-admins during work hours and notifications are set appropriately.
 - Become familiar with the [Kubernetes Community Values].
 - Take care of spam as soon as possible, which may mean taking action by
   removing a member from that resource.
@@ -212,7 +212,7 @@ umbrella.
   are being flagged by the system.
 - We do NOT use YouTube comments during our live streams, these are checked as
   OFF in the settings.
-- [Youtube Guidelines](./K8sYoutubeCollaboration.md)
+- [Youtube Guidelines](./youtube-guidelines.md)
 - [Moderators](./moderators.md#youtube-channel)
 
 ### Zoom
diff --git a/communication/youtube-guidelines.md b/communication/youtube-guidelines.md
new file mode 100644
index 00000000..eec69b96
--- /dev/null
+++ b/communication/youtube-guidelines.md
@@ -0,0 +1,43 @@
+## Kubernetes Youtube Channel Collaboration 
+
+
+### Meeting Playlists
+
+
+The [Kubernetes Youtube Channel](https://www.youtube.com/channel/UCZ2bu0qutTOM0tHYa_jkIwg) has separate playlists for each SIG’s meeting recordings, as well as recordings of other meetings (i.e. Cloud Native, Kubernetes Community meetings). 
+
+To better serve the community, we have set up [collaboration](https://support.google.com/youtube/answer/6109639) on these playlists, so that anyone with the appropriate link to the particular playlist can upload videos *to that particular playlist* (links & playlists are 1:1).
+
+Each SIG playlist’s link will be shared with the SIG’s leadership, and other playlists' links (i.e. Cloud Native) will be shared with the appropriate point(s) of contact. The SIG playlist links will be sent to the official SIG lead Google Groups. 
+
+### Uploading Guidelines for Collaborators
+
+Collaboration should simplify things for everyone, but with privilege comes responsibility :). We assume all playlist collaborators in the community will use things fairly and appropriately, subject to the guidelines below:
+
+1. Once collaboration is setup for each meeting recording playlist, the upload responsibility will fall on the SIG leaders or other appropriate point(s) of contact.  Community managers *will only be escalation for issues with those playlists*
+
+2. Please post only related content (mostly meeting recordings) in the appropriate playlists 
+	- Posting of any exceedingly inappropriate content (i.e. NSFW content) will result in ***immediate*** suspension of privileges 
+
+3. Please ensure all videos have the same naming format, which is:
+	- Kubernetes [Name of Playlist’s Group] YYYYMMDD
+		- i.e. Kubernetes SIG Service Catalog 20161129
+
+4. All playlists need to be organized chronologically for ease of use, which is most easily done by selected “date added, newest” as the “Ordering” option in the playlist settings
+
+5. Please do not remove any already-published content from the playlists without checking with the community managers 
+
+6. For any small issues that arise (i.e. improper naming / ordering), you may be asked by the community managers to attempt to resolve the issue yourselves
+ 
+7. Any egregious or habitual violation* of the above rules will result in suspension of collaboration privileges for the particular individual, or for the entire playlist if the individual can’t be identified
+	- If an individual is suspended, the playlist link will be remade and the new link will be shared with the non-offending individuals 
+	- If *playlist* collaboration is suspended, uploading by community managers to the playlist of interest will ***not*** be a priority, and will likely occur on a delayed basis
+	- *Note that "habitual violation" means "more than 3 issues per quarter"
+
+### Permissions for G Suite Accounts
+
+- If you're using a G Suite account you might need to loosen the permissions in your YouTube settings. See [this help article](https://support.google.com/a/answer/6212415) for more information. 
+
+Your community managers are happy to help with any questions that you may have and will do their best to help if anything goes wrong. Please get in touch via [SIG Contributor Experience](https://git.kubernetes.io/community/sig-contributor-experience).
+
+- Check the [centralized list of administrators](./moderators.md) for contact information.
diff --git a/communication/zoom-guidelines.md b/communication/zoom-guidelines.md
index e92a7aa6..df183344 100644
--- a/communication/zoom-guidelines.md
+++ b/communication/zoom-guidelines.md
@@ -8,7 +8,7 @@ has to moderate a meeting in all senses of the word from starting and stopping
 the meeting, to acting on [code of conduct] issues.
 
 These guidelines are meant as a tool to help Kubernetes members manage their
-Zoom resources. 
+Zoom resources.
 
 Check the main [moderation] page for more information on other tools and general
 moderation guidelines.
@@ -28,7 +28,7 @@ listed in the [centralized list of administrators].
 
 ### Obtaining a Zoom license
 
-Ensure that all SIG/WG leads, chairs, and any other necessary trusted owners 
+Ensure that all SIG/WG leads, chairs, and any other necessary trusted owners
 have access to the `k-sig-<foo>-leads@googlegroups.com` account as described
 in the [sig creation procedure]. Once done, contact one of the [Zoom Admins]
 to obtain a Zoom licence.
@@ -43,9 +43,9 @@ To create a meeting with **moderation** enabled, ensure the following:
 
 - Have the [latest version] of the Zoom client installed.
 - Be logged in as the leads account associated with the meeting **OR** use the
-  [host key] to "claim host". 
+  [host key] to "claim host".
 - Configure a meeting setup through the "Meeting" menu in the leads Zoom account.
-  **NOTE:** Do **NOT** use the "Personal Meeting ID". This will create an 
+  **NOTE:** Do **NOT** use the "Personal Meeting ID". This will create an
   "ad-hoc" meeting that is time-bounded and without moderation capability.
 
 After the meeting has started:
@@ -60,7 +60,7 @@ After the meeting has started:
 
 If you're dealing with a troll or bad actor:
 
-- Put the troll or bad actor on **hold**. The participant will be put into a 
+- Put the troll or bad actor on **hold**. The participant will be put into a
   "waiting room" and will not be able to participate in the call until the host
   removes the hold.
 - Remove the participant. Please be cautious when testing or using this feature,
@@ -76,7 +76,7 @@ options after scrolling over the participants name/information.
 
 Hosts **must** be comfortable with how to use these moderation tools and the
 Zoom settings in general. Make sure whoever is running your meeting is equipped
-with the right knowledge and skills. If you have any questions or concerns, 
+with the right knowledge and skills. If you have any questions or concerns,
 reach out to the [Zoom Admins] and they will be able to provide further guidance
 and training.
 
@@ -84,7 +84,7 @@ and training.
 #### Related moderation documentation
 
 - Zoom has [documentation on how to use their moderation tools].
-- Members of the _kubernetes-sig-leads@_ group have access to an extensive 
+- Members of the _kubernetes-sig-leads@_ group have access to an extensive
   [best practices doc] with screenshots going over the community Zoom best
   practices.
 
@@ -203,7 +203,7 @@ Thanks for making Kubernetes meetings work great!
 [best practices doc]: https://docs.google.com/document/d/1fudC_diqhN2TdclGKnQ4Omu4mwom83kYbZ5uzVRI07w/edit?usp=sharing
 [Kubernetes channel]: https://www.youtube.com/c/kubernetescommunity
 [SIG Contributor Experience]: /sig-contributor-experience
-[Please follow this guideline for more details.]: ./K8sYoutubeCollaboration.md
+[Please follow this guideline for more details.]: ./youtube-guidelines.md
 [centralized list of administrators]: ./moderators.md
 [documentation on how to use their screen sharing feature]: https://support.zoom.us/hc/en-us/articles/201362153-How-Do-I-Share-My-Screen
 [lots of things that can go wrong]: https://www.youtube.com/watch?v=JMOOG7rWTPg