Follow up later if we need to (rerecord, do an interview)
No extra work
Producing videos shouldn't be extra work.
You should do what you normally do.
But when a meeting is possibly interesting for more people, make it a livestream.
Or when you start talking about something possibly relevant to more people, hit the record button.
Make private quickly
In case there are any concerns raised about a video everyone has the authority to make it private.
You don't have to wait for any permission, just go to the channel specific YouTube Studio, for example the one for unfiltered and mark the video private.
Please note that there is another tab for live videos.
In case you marked it private while it doesn't need to be it will be easy to undo it by marking the video public.
Why not Google Drive
Always use YouTube and never use Google Drive, even for private videos, because YouTube videos:
The level of visibility should be displayed clearly in the titles of calendar invites.
For example when you do a livesteam to the public channel say: "Private stream" at the start of the invite.
You can skip live in livestream since every stream is live.
Do not say Unfiltered stream since it is ambiguous.
Do not say just livestream since people don't know what the level of access is.
We don't post:
Unlisted videos on any channel, this is too insecure for sensitive materials and not findable enough for public materials.
Private videos on our main channel, all videos here are for a wider audience.
If you get a "Video unavailable This video is private." error on youtube, the error may be caused because the video is private to GitLab Unfiltered and you are accessing the video with your individual Youtube account. In order to see the video, click your photo or icon in the top right of Youtube, then click > Switch Account > GitLab Unfiltered. Once you are on GitLab unfiltered, reload the page and you can view the video.
GitLab Filtered: To request access follow the instructions secret note 'YouTube Access' in the team vault in 1password.
GitLab Unfiltered: Everyone should get access to YouTube unfiltered during onboarding. If you do not see an invitation in your Inbox, please check the Pending Invitations section of your GSuite account.
Remember that when you're signed into YouTube using an official GitLab account that any interaction you may have with other groups or people on the site (e.g. such as in the comments sections of videos) will be perceived as official communication from the company. In almost all cases, unless your job specifically requires you to interact in a community manager role or capacity, it is best to switch to a personal account prior to engaging with a video or user on YouTube.
Our YouTube channels contain a lot of content.
As a result it can often be hard to find videos once they are published.
Make liberal use of tags and playlists to organize video content you publish.
For published recordings of recurring meetings, create a YouTube playlist.
Starting a recorded video that is/is not Livestreamed
The below instructions apply to either livestreams to YouTube or recorded videos which are uploaded to YouTube soon afterwards.
When the meeting or call is about to start (5 seconds or so before the start time), the moderator starts the recording and everyone on the call can hear: "This call is being recorded". This ensures that there is no empty space at the beginning of the call.
If the meeting is to be livestreamed, the moderator asks the host "Can I initiate/start the countdown?" and waits for confirmation. The moderator counts down from three ("I'll start the countdown for this public/private stream in 3, 2, 1"), and nothing else is said by the moderator beyond this point so that so it is not accidentally recorded. Click Live to YouTube and start the livestream.
If the meeting is only to be recorded, the moderator does not complete Step 2 above.
The host should do an introduction stating who they are, what their role is, and what the meeting is about, e.g. "I am Jane Doe, the VP of Widget Production, and today's Group Conversation is about the molding phase of widget production."
We prefer livestreaming over uploading because:
it allows more people to participate in real-time.
You don't have to upload the video to YouTube later on (extra step).
You can't forget about uploading the video.
It is clear to all participants that the content will be public.
But it can happen that you're not in a livestream and something interesting comes up.
In that case, you can upload it to YouTube.
Unless stated or arranged otherwise, our expected behavior is that the meeting organizer is responsible for distributing the video after the meeting.
Log in to the Zoom account of the meeting and go to the menu on the right and choose "My Recordings" (it can take up to 30 minutes before the recording is available to be shared).
Select the meeting and download the recording to your computer (if you can't find the recording because it was a while ago check "Trash" in the menu on the top left and "Recover" the recording).
Go to the YouTube upload page and log into the channel. If you're logged into your personal YouTube account, you may need to first log into your GitLab YouTube account to access the channel. If you're already logged into your GitLab YouTube account and have access to the channel, you need to switch accounts to that channel. To switch accounts, click on the account icon in the top right corner and then click "Switch account".
Drag and drop your recording into the window to upload it. Keep the privacy dropdown on the default 'Public' setting (unless there is confidential material). Use the dropdown menu to set the video to private if it the video contains confidential material.
While it's uploading, edit the title and description. Place "Confidential:" at the beginning of the video's title if the video will be kept private on our YouTube channel.
Be sure to include relevant links (for example a handbook page or presentation) in the description, and add the video to any relevant playlists.
When it is done uploading, press publish, then click on the Embed tab and copy the code, and insert that in the relevant part of the handbook or documentation.
After uploading a video to the GitLab Filtered channel, be sure to add a link to the new video in the #content-updates channel in Slack.
Everyone at the company probably has at least one conversation every week that is relevant to more people, so please share it.
We always list videos publicly instead of having them unlisted, unless there is confidential material. This allows more people to find the content. If the material is confidential, set the video to private.
Don't worry about whether or not it will be interesting to absolutely everyone. Just give it a descriptive title so people know what it is about, and let them decide whether or not they should watch it.
Make sure that all participants are aware that you're recording.
You don't have to be sure it is interesting and OK to share when you start recording; you can make that decision after the fact.
If you record an in-person conversation with your mobile phone please hold your phone in landscape (horizontal) mode.
Depending on your needs, you might want use software to provide overlays and/or reroute audio.
99% of the people at GitLab don't use this, but see below for instructions if you do want to use it.