YouTube serves as the primary means of distribution for recorded Kubernetes community content including Zoom recordings, official project workshops and Contributor Summit sessions.
Kubernetes adheres to the Kubernetes Code of Conduct throughout the project, and includes all communications such as YouTube.
@youtube-admins
in the
#sig-contribex
Slack channel.The Kubernetes YouTube Channel has separate playlists for each SIG, WG, UG meeting recordings, as well as recordings of other recurring events such as the Kubernetes community meeting, Office Hours, Meet our Contributors and others.
Subprojects, in addition to SIGs, WGs, UGs may request their own playlists to better target their contributors and increase general discoverability.
To better serve the community, collaboration has been enabled to share the management of the playlists. Anyone with the appropriate link to the particular playlist can upload videos to that particular playlist (links & playlists are one-to-one).
Each group’s playlist link will be shared with the group’s leadership via Slack and the group leadership Google Group. Other playlists links, for example Office Hours, will be shared with the appropriate point(s) of contact.
NOTE: If you’re using a Google Workspace account (formerly known as G Suite) you may need to update the permissions in your YouTube settings. If you have any questions, reach out to the YouTube admins or SIG Contributor Experience. You may need to reach out to someone at your organization if you do not have access to Google Workspace Admin permissions.
NOTE: Both public and private steering meeting recordings should be made public.
With collaboration comes great responsibility. Playlist collaborators in the community must use it responsibly and are subject to the following guidelines:
Group leaders or other appropriate point(s) of contact are the primary managers for the playlist, once collaboration is configured. YouTube admins should only be contacted if the issue cannot be resolved by one of the playlist owners.
Upload responsibilities belong to the group leaders or other appropriate contacts. YouTube admins should only be contacted if the issue cannot be resolved by the playlist owners.
Please post only related content, for example meeting recordings, in the appropriate playlists.
All posted videos should use the naming convention: <Name of Playlist’s Group> YYYYMMDD
Playlists should be organized chronologically for ease of use. This can be done by updating the default ordering of the Playlist:
Please do not remove any already-published content from the playlists without checking with the YouTube admins.
For any small issues that arise, for example improper naming or ordering, you may be asked by the YouTube admins to attempt to resolve the issue yourself.
Any egregious or habitual violations (3 or more per quarter) 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.
The role of the Youtube Admins is to help maintain a robust YouTube channel that is valuable to contributors and upholds our transparency goals as laid out by our governance documents.
Moderators should adhere to the general Kubernetes project moderation guidelines.
Moderation responsibilities for YouTube admins is minimal and is centered around checking and removing any potential comments that would violate the Code of Conduct. Any potential violations should be sent to conduct@kubernetes.io.
YouTube admins are asked to help trim and edit recordings that come into the video queue.
Certain events such as the Contributor Summits are not uploaded directly to YouTube and require editing.
A Zoom recording may have significant dead-space leading the meeting itself and also at the end as we end the stream.
A SIG Meeting needs to be edited to make sure it’s clear (ie “Kubernetes Special Interest Group ContribEx 20220131 Meeting”).
Make sure to save a copy of the video first before making adjustments as this can delete the original if not careful. When in doubt, ask.
Note: There is always room for improvement! As such, the community is open to trying various integration features or other productivity tools that might improve the job of admins and help make things more streamlined. Please, reach out if you can help or have any ideas.
One feature used by several SIGs is splain.io. This tool creates a pipeline between Zoom and youtube for easier workflows. To use splain.io please follow the steps outlined below.
Items needed to use splain.io:
Steps:
The following SIGs and groups are currently running splain.io:
Each video that comes into the queue needs to be added to a playlist, set to public, and have contextual information added to the description.
Example description:
Kubernetes Contributor Experience Special Interest Group Weekly Meeting. Check here (link to sig list) for a complete list of SIGs and when they meet. Join us!
Please note the following items:
Below is an example:
Data Protection WG Bi-Weekly Meeting for 2/26/2020
Data Protection WG Bi-Weekly Meeting for 20200226
A short video tutorial of the editing of descriptions and playlists can be found here:
There have been ongoing conversations about how to create and manage better thumbnails for videos using some kind of standard. If you’re interested in helping with thumbnails, please reach out to the YouTube Admins. They would love to hear from you.
YouTube admins with a system capable of streaming may be asked to stream public Kubernetes Community events such as the weekly Community Meeting, Office Hours, Meet our Contributors, or other publicly streamed events. For detailed information about streaming, see our Streaming Config.
In certain cases, such as archiving an inactive SIG or Working Group, it might be useful to grab content from other channels. It is currently NOT POSSIBLE to move content from one YouTube channel to another, so the content must be downloaded and then reuploaded to the Kubernetes channel.
youtube-dl <url>
Was this page helpful?