Skip to content

Add section on not sharing secrets in public YouTube videos

Greg Myers requested to merge keep-gitlab-unfiltered-safe into master

Summary

This merge request adds a new section to the YouTube guidelines on the GitLab Unfiltered Handbook page. The new section emphasizes the importance of not sharing secrets or personal data in public YouTube videos.

Changes

  • Added a section titled "Don't share secrets" to the YouTube guidelines in the Marketing Operations Handbook.
  • The new section advises against sharing secrets such as access tokens, private keys, passwords, and credentials to systems running on GitLab infrastructure.
  • It also advises against sharing GitLab team member personal data like phone numbers and home addresses.
  • The section clarifies that any video that exposes secrets or team member personal data should not be shared as a public YouTube recording.

Why is this change being made?

This change is important for maintaining the security and privacy of GitLab's infrastructure and team members. It provides clear guidelines to prevent accidental sharing of sensitive information in public YouTube videos.

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports