How GitLab protects IP (Aug 5)

Proposal

This post aims to describe the complex network of access and change permission the different layers GitLab have. In a way, it's an update of this video from 2016 (linked in the article too) with new features that have enhanced the client's capabilities to protect and track changes to their IP. It is also a new way of framing this conversation (we usually talk about code and not IP) which speaks to a certain audience we have spoken to in the past. And finally, it is a way to give visibility to a use case that one of hour best clients showcased in GitLab Brooklyn 2019.

Find the DRAFT here

Checklist

• If you have a specific publish date in mind (please allow 3 weeks' lead time)
  • Include it in the issue title
  • Give the issue a due date of a minimum of 2 working days prior
  • If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
• If time sensitive
  • Add ~"Blog: Priority" label and supplied rationale in description
  • Mention @rebecca to give her a heads up ASAP
• If wide-spread customer impacting or sensitive
  • Add sensitive label
  • Mention @nwoods to give her a heads up ASAP
• If the post is about one of GitLab's Technology Partners, including integration partners, mention @TinaS, apply the Partner Marketing label, and see the blog handbook for more on third-party posts
• Indicate if supporting an event or campaign
• Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)