Merge branch 'master' into 'patch-19826111318'

# Conflicts:
#   source/handbook/sales/territories/index.html.md

.gitlab/CODEOWNERS

@@ -9,7 +9,7 @@
 /source/handbook/business-ops/ @wzabaglio
 /source/handbook/business-ops/data-quality-process/ @kathleentam @tayloramurphy @jjstark
 /source/handbook/business-ops/data-team/ @wzabaglio @kathleentam @jjstark @tayloramurphy @eli_kastelein @mpeychet @iweeks @derekatwood
-/source/handbook/business-ops/data-team/metrics/ @kathleentam @derekatwood 
+/source/handbook/business-ops/data-team/kpi-index/ @kathleentam @derekatwood 
 /source/handbook/business-ops/data-team/data-infrastructure/ @jjstark @tayloramurphy
 /source/handbook/business-ops/data-team/python-style-guide/ @jjstark @tayloramurphy

.gitlab/merge_request_templates/Applications.md

@@ -10,5 +10,5 @@ Checklist:
 1. [ ] Application's data added to [`data/applications.yml`](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/applications.yml) (to the end of the category)
 1. [ ] Application's logo added to [`source/images/applications/apps/`](https://gitlab.com/gitlab-com/www-gitlab-com/tree/master/source/images/applications/apps) (optional, but recommended)
 1. [ ] Label the MR with ~"Partners (== Applications)" ~"Community Contribution"  and assign the current milestone
-1. [ ] Mayank Tahilramani's review - cc/ @mayanktahil
+1. [ ] Amy Brandenburg's review - cc/ @abrandenburg
 1. [ ] Tech writer's review

data/categories.yml

@@ -70,7 +70,7 @@ users:
     - user profile
   alt_link: https://docs.gitlab.com/ee/user/profile/
   documentation: https://docs.gitlab.com/ee/user/profile/
-  strategy: /direction/manage/access/users/
+  strategy: /direction/manage/users/
   description: "Managing who's using your instance and what they can do with user management tools, permissions, and user profiles."
   roi: false
   marketing: false # not "available" as a capability for customers
@@ -84,7 +84,7 @@ groups:
     - subgroups
   alt_link: https://docs.gitlab.com/ee/user/group/#groups
   documentation: https://docs.gitlab.com/ee/user/group/#groups
-  strategy: /direction/manage/access/groups/
+  strategy: /direction/manage/groups/
   description: "Organize your projects and restrict access to controlled resources."
   roi: false
   marketing: false # not "available" as a capability for customers
@@ -140,6 +140,7 @@ importers:
     - project export
     - project import
   description: "Import existing work into GitLab from a wide variety of sources."
+  strategy: https://about.gitlab.com/direction/manage/importers
   marketing: false
   roi: false
   acquisition_appetite: low
@@ -148,6 +149,7 @@ templates:
   name: "Templates"
   stage: manage
   documentation: https://docs.gitlab.com/ee/user/group/custom_project_templates
+  strategy: https://about.gitlab.com/direction/manage/templates
   description: "Get new projects hitting the ground running with extensible, reusable templates."
   marketing: false
   roi: false
@@ -809,7 +811,7 @@ system_testing:
   strategy: https://about.gitlab.com/direction/verify/system_testing
   description: "Modern software is often delivered as a collection of (micro)services to multiple clouds, rather than a single monolith to your own data center. Validating complex interactions to ensure reliability of the system as a whole is more important than ever."
   roi: false
-  available: 2021-01-22
+  available: 2020-04-22
   viable:
   complete:
   lovable: 2023-11-18
@@ -1163,9 +1165,9 @@ release_orchestration:
   description: "Management and orchestration of releases-as-code that supports intelligent notifications, scheduling of delivery and shared resources, blackout periods, relationships, parallelization, and sequencing, as well as support for integrating manual processes and interventions."
   roi: false
   available: 2017-01-01
-  viable: 2019-11-22
-  complete: 2020-06-22
-  lovable: 2020-11-22
+  viable: 2020-03-22
+  complete: 2021-03-22
+  lovable: 2023-11-22
   maturity: minimal
   marketing: true
   acquisition_appetite: medium
@@ -1243,10 +1245,10 @@ release_governance:
   strategy: /direction/release/release_governance/
   description: "Release Governance includes features such as deploy-time security controls to ensure only trusted container images are deployed on Kubernetes Engine, and more broadly includes all the assurances and evidence collection that are necessary for you to trust the changes you're delivering."
   roi: false
-  available: 2019-11-22
-  viable: 2020-02-22
-  complete: 2020-9-22
-  lovable: 2021-3-22
+  available: 2020-01-22
+  viable: 2020-07-22
+  complete: 2020-12-22
+  lovable: 2022-05-22
   maturity: planned
   marketing: true
   acquisition_appetite: low
@@ -1258,10 +1260,10 @@ secrets_management:
   strategy: /direction/release/secrets_management/
   description: "Use Vault embedded in GitLab for managing your secrets both inside and outside of GitLab."
   roi: false
-  available: 2019-11-22
-  viable: 2020-03-22
-  complete: 2020-05-22
-  lovable: 2020-10-22
+  available: 2019-12-22
+  viable: 2020-05-22
+  complete: 2020-10-22
+  lovable: 2023-03-22
   maturity: planned
   marketing: true
   acquisition_appetite: medium
@@ -1550,9 +1552,9 @@ status_page:
 web_firewall:
   name: "WAF"
   stage: defend
-  alt_link: https://docs.gitlab.com/ee/user/clusters/applications.html#modsecurity-application-firewall
+  alt_link: https://docs.gitlab.com/ee/user/clusters/applications.html#web-application-firewall-modsecurity
   strategy: /direction/defend/web_application_firewall/
-  documentation: https://docs.gitlab.com/ee/user/clusters/applications.html#modsecurity-application-firewall
+  documentation: https://docs.gitlab.com/ee/user/clusters/applications.html#web-application-firewall-modsecurity
   description: "A Web Application Firewall (WAF) is able to examine traffic being sent to an application and can block malicious traffic before they reach your application."
   roi: false
   available: 2019-09-22

data/events.yml

+- topic: Enterprise Kubernetes Summit Dallas
+  type: Conference
+  date: December 11, 2019
+  date_ends: December 11, 2019
+  description: |
+             With the explosive growth of Kubernetes, many organizations are searching for ways to harness the power of container adoption and deliver strategic value to production. GitLab,Rancher, Datadog, and Aqua have partnered together to deliver a free, full stack container workshop that will help your technical teams deliver Kubernetes as a strategic service for your business.
+  location: Plano, Texas
+  region: AMER
+  event_url: https://k8sdallas.splashthat.com/?utm_campaign=Enterprise%20Kubernetes%20Summit%3A%202019-12-11%3A%20Dallas&utm_source=gitlab
+
+- topic: Enterprise Kubernetes Summit Austin
+  type: Conference
+  date: December 10, 2019
+  date_ends: December 10, 2019
+  description: |
+             With the explosive growth of Kubernetes, many organizations are searching for ways to harness the power of container adoption and deliver strategic value to production. GitLab,Rancher, Datadog, and Aqua have partnered together to deliver a free, full stack container workshop that will help your technical teams deliver Kubernetes as a strategic service for your business.
+  location: Austin, Texas
+  region: AMER
+  event_url: https://k8saustin.splashthat.com/?utm_campaign=Enterprise%20Kubernetes%20Summit%3A%202019-12-10%3A%20Austin&utm_source=gitlab
+
 - topic: Geekfest@Bell
   type: Conference
   date: February 18-19, 2020
@@ -1673,6 +1693,26 @@ There is a lot of curiosity and confusion around serverless computing. What is i
   social_tags: #GitLabMeetup
   event_url: https://www.meetup.com/Mexico-City-GitLab-Meetup/events/266371707/
+- topic: GitLab Lunch & Learn Wellington
+  type: MeetUp
+  date: December 10, 2019
+  date_ends: December 10, 2019
+  description: Join this Lunch and Learn Lab Session where we will break out into small groups and develop your understanding and skills through hands-on practical use of GitLab. 
+  location: Wellington, NZ
+  region: APAC
+  social_tags: #GitLabMeetup
+  event_url: https://www.meetup.com/GitLabANZ/events/266416769/
+
+- topic: GitLab MSP User Group
+  type: MeetUp
+  date: December 12, 2019
+  date_ends: December 12, 2019
+  description: Hear from two customers on how GitLab enabled their DevOps journeys. 
+  location: Minneappolis, MN
+  region: AMER
+  social_tags: #GitLabMeetup
+  event_url: https://www.meetup.com/GitLab-MSP-Meetup/events/266644322/
+
 - topic: GitLab São Paulo
   type: MeetUp
   date: December 12, 2019
@@ -1693,6 +1733,16 @@ There is a lot of curiosity and confusion around serverless computing. What is i
   social_tags: #GitLabMeetup
   event_url: https://www.meetup.com/GitLab-Chicago-User-Community/events/266580345/
+- topic: GitLab Nigeria Community
+  type: MeetUp
+  date: December 21, 2019
+  date_ends: December 21, 2019
+  description: One of Warri's young startups will share how they code, collaborate, and contribute with GitLab.
+  location: Warri, Nigeria
+  region: EMEA
+  social_tags: #GitLabMeetup
+  event_url: https://www.meetup.com/GitLab-Nigeria-Community/events/266715018/
+
 - topic: JsConf Armenia
   type: Conference
   date: November 30, 2019

data/heroes.yml

@@ -455,3 +455,13 @@
   gitlab: wiget
   picture: arturfrysiak.jpg
+- type: person
+  name: Matteo Codogno
+  locality: Lugano
+  country: Switzerland
+  role: GitLab Hero
+  twitter: teo1690
+  bio: Tech Lead | Full stack tinkerer | Love to experiment with new technologies
+  gitlab: papasmurf17
+  picture: matteocodogno.jpg
+

data/pets.yml

@@ -1293,7 +1293,13 @@
   picture: idekerfinn.jpg
   human: Timm Ideker
   story: |
-         Finn is an English Cream Golden Retirever who was born in North Carolina.  He now loves Minnesota - snow, seasons, and 10,000 lakes to explore.  He can usually be found under Timm's chair in the office, curled up like a furry croissant.  
+         Finn is an English Cream Golden Retirever who was born in North Carolina.  He now loves Minnesota - snow, seasons, and 10,000 lakes to explore.  He can usually be found under Timm's chair in the office, curled up like a furry croissant.
+
+- name: Iris and Raidho
+  picture: iris-raidho.png
+  human: Dominic Couture
+  story: |
+         Iris and Raidho are Australian Shepherds with boundless energy. They love to run with their human while he runs, bikes and skis in the forests and mountains located around home. When playtime is over, they enjoy cuddling and sleeping in all sorts of funny positions.
          
 - name: Katie
   picture: katieRose.png

data/projects.yml

@@ -478,14 +478,14 @@ meltano:
     
     Meltano stands for the steps of the data science life-cycle: Model, Extract, Load, Transform, Analyze, Notebook, and Orchestrate.
-peopleops-bot:
-  name: PeopleOps Automation Bot
-  path: gitlab-com/people-ops/employment
-  link: https://gitlab.com/gitlab-com/people-ops/employment
-  description: |
-    Bot to automate common PeopleOps operations like onboarding issue
-    creation, anniversary and new hire announcements, general issue
-    housekeeping, etc.
+peopleops-employment-automation:
+  name: PeopleOps Employment Automation
+  path: gitlab-people-engineering/employment-automation
+  link: https://gitlab.com/gitlab-people-engineering/employment-automation
+  description: |
+    Automation related to various employment activities at GitLab, like
+    onboarding issue creation, anniversary and new hire announcements,
+    GreenHouse to BambooHR sync, general issue housekeeping, etc.
 snowflake_spend:
   name: Snowflake Spend dbt Package

data/redirects.yml

@@ -745,15 +745,25 @@
   - /events/multicloudcon
   target: https://multicloudcon.io/
   comp_op: '='
-- sources: 
+- sources:
   - /handbook/sponsoredtravel/
   - /handbook/sponsoredtravel
   - /handbook/travel-sponsored/
   - /handbook/travel-sponsored
   target: /handbook/travel/sponsored/
   comp_op: '='
-- sources: 
+- sources:
   - /product/agile-portfolio-management
   - /product/agile-portfolio-management/
   target: /solutions/portfolio-management/
+  comp_op: '='
+- sources:
+  - /handbook/creator/fellow_of_initial_delight
+  - /handbook/creator/fellow_of_initial_delight/
+  target: /job-families/fellow-of-initial-delight/
+  comp_op: '='
+- sources: 
+  - /handbook/business-ops/data-team/metrics
+  - /handbook/business-ops/data-team/metrics/
+  target: /handbook/business-ops/data-team/kpi-index/
   comp_op: '='
\ No newline at end of file

data/release_post_managers.yml

@@ -8,30 +8,30 @@ releases:
 - version: "12.9"
   date: "2020-03-22"
   manager: ljlane
-  structural_check: --
+  structural_check: rdickenson
   messaging: traci
-  messaging-shadow: williamchia 
+  messaging-shadow: williamchia
   social: --
 - version: "12.8"
   date: "2020-02-22"
   manager: cdybenko
-  structural_check: --
+  structural_check: msedlakjakubowski
   messaging: williamchia
-  messaging-shadow: traci 
+  messaging-shadow: traci
   social: --
 - version: "12.7"
   date: "2020-01-22"
   manager: jramsay
-  structural_check: --
+  structural_check: marcia
   messaging: brianglanz
-  messaging-shadow: cblake # with Jordi 
+  messaging-shadow: cblake # with Jordi
   social: --
 - version: "12.6"
   date: "2019-12-22"
   manager: gweaver
-  structural_check: --
+  structural_check: axil
   messaging: johnjeremiah
-  messaging-shadow: brianglanz # with Saumya 
+  messaging-shadow: brianglanz # with Saumya
   social: --
 - version: "12.5"
   date: "2019-11-22"
@@ -197,7 +197,7 @@ releases:
 managers:
 - handle: axil
   name: "Axil"
-  team_page: "_axil"
+  team_page: "axil"
 - handle: erica
   name: "Erica"
   team_page: "EricaLindberg_"
@@ -233,13 +233,13 @@ managers:
   team_page: "marcel.amirault"
 - handle: marcia
   name: "Marcia"
-  team_page: "XMDRamos"
+  team_page: "marcia"
 - handle: markpundsack
   name: "Mark P."
   team_page: "MarkPundsack"
 - handle: mikelewis
   name: "Mike L."
-  team_page: "miketechnically"
+  team_page: "mikelewis"
 - handle: mydigitalself
   name: "Mike B."
   team_page: "mydigitalself"
@@ -312,4 +312,6 @@ managers:
 - handle: deuley
   name: "Patrick"
   team_page: "deuley"
-  
\ No newline at end of file
+- handle: msedlakjakubowski
+  name: "Marcin"
+  team_page: "msedlakjakubowski"

data/release_posts/2019_09_22_gitlab_12_3_released.yml

@@ -2,7 +2,7 @@ features:
   top:
     - name: "Web Application Firewall for Kubernetes Ingress"
       available_in: [core, starter, premium, ultimate]
-      documentation_link: "https://docs.gitlab.com/ee/user/clusters/applications.html#modsecurity-application-firewall"
+      documentation_link: "https://docs.gitlab.com/ee/user/clusters/applications.html#web-application-firewall-modsecurity"
       video: "https://www.youtube.com/embed/o8-CU6TEH2w"
       reporter: stkerr
       stage: "defend"
@@ -16,7 +16,7 @@ features:
         to your app contains malicious code, such as SQL injection, cross-site scripting,
         or trojans. The WAF is pre-configured with a powerful set of rules, the OWASP ModSecurity Core Rules (CRS), to detect many different types of attacks out-of-the-box.
-        The [documentation](https://docs.gitlab.com/ee/user/clusters/applications.html#modsecurity-application-firewall) describes how to view the WAF logs so
+        The [documentation](https://docs.gitlab.com/ee/user/clusters/applications.html#web-application-firewall-modsecurity) describes how to view the WAF logs so
         you can see what type of malicious traffic your app is subjected to
         when it is running in production.

data/release_posts/2019_11_22_gitlab_12_5_released.yml

@@ -395,7 +395,7 @@ features:
       stage: verify
       issue_url: 'https://gitlab.com/gitlab-org/gitlab/issues/18986'
       description: |
-        GitLab CI/CD allows you to specify a list of files and directories which should be cached between jobs. Pulling files from cache rather than building from sratch can be a great way to speed up your pipelines. But caching can be bad if there's a new version of the file and the cache isn't updated so the old version of the file is used. Now in GitLab 12.5, managing caching has become much easier with the new ability to use the commit SHA as the cache key. Since this corresponds with the underlying source that the file was built from, it's a very natural way to ensure that cache expiration follows actual changes. This will make caching in your pipelines easier to set up and much more efficient.
+        GitLab CI/CD allows you to specify a list of files and directories which should be cached between jobs. Pulling files from cache rather than building from scratch can be a great way to speed up your pipelines. But caching can be bad if there's a new version of the file and the cache isn't updated so the old version of the file is used. Now in GitLab 12.5, managing caching has become much easier with the new ability to use the commit SHA as the cache key. Since this corresponds with the underlying source that the file was built from, it's a very natural way to ensure that cache expiration follows actual changes. This will make caching in your pipelines easier to set up and much more efficient.
     - name: "GitLab Runner 12.5"
       available_in: [core, starter, premium, ultimate]

data/release_posts/unreleased/jramsay-dedupe-internal-forks.yml

+features:
+  secondary:
+    - name: "Deduplicate forks of internal projects"
+      available_in: [core, starter, premium, ultimate]
+      documentation_link: "https://docs.gitlab.com/ee/administration/repository_storage_types.html#hashed-object-pools"
+      reporter: jramsay
+      stage: create
+      issue_url: "https://gitlab.com/gitlab-org/gitlab/issues/33318"
+      description: |
+        Forking workflows makes it easy to contribute to any project by
+        creating a copy of the upstream project to work on before opening a
+        merge request to merge your changes into the upstream project. For
+        popular projects, the server-side storage requirements needed for
+        thousands of copies accumulate quickly and increase hosting costs.
+
+        In GitLab 12.1, we introduced fork deduplication for public projects,
+        but many organizations missed out on the benefits because they
+        primarily use internal projects. In GitLab 12.5, creating a fork of
+        public or internal projects creates an object pool (if one doesn’t
+        already exist) and uses `objects/info/alternates` to reduce the storage
+        requirements of forks.
+
+        Thanks [Brian Kabiro](https://gitlab.com/briankabiro) for your
+        [contribution](https://gitlab.com/gitlab-org/gitlab/merge_requests/19295)!

data/role_levels.yml

@@ -199,7 +199,7 @@ executive_recruiter:
 people_experience:
   - title: "Coordinator"
     factor: 0.8
-    grade: 4
+    grade: 5
   - title: "Associate"
     factor: 1.0
     grade: 5
@@ -222,3 +222,35 @@ people_specialist:
   - title: "Team Lead/Manager (of people)"
     factor: 1.4
     grade: 8
+
+people_generalist:
+  - title: "Junior/Coordinator"
+    factor: 0.8
+    grade: 5
+  - title: "Generalist"
+    factor: 1.0
+    grade: 6
+    is_default: true
+  - title: "Partner"
+    factor: 1.2
+    grade: 7
+  - title: "Manager (of people)"
+    factor: 1.4
+    grade: 8
+
+manager_only:
+  - title: "Staff/Manager (of people)/Lead"
+    factor: 1.0
+    grade: 8
+
+ces:
+  - title: "Junior Specialist"
+    factor: 0.8
+    grade: 5
+  - title: "Specialist"
+    factor: 1.0
+    grade: 5
+    is_default: true
+  - title: "Senior Specialist"
+    factor: 1.2
+    grade: 6

data/roles.yml

@@ -9,21 +9,21 @@
   apply:
   open: false
-- title: "Accounting Manager"
+- title: "Manager, Accounting"
   description: /job-families/finance/accounting-manager/
   levels: manager_basic
   salary: 130200
   apply:
   open: false
-- title: "Accounting Operations Manager"
+- title: "Manager, Accounting Operations"
   description: /job-families/finance/accounting-operations-manager/
   levels: manager_basic
   salary: 130200
   apply:
   open: false
-- title: "Technical Accounting Manager"
+- title: "Manager, Technical Accounting"
   description: /job-families/finance/technical-accounting-manager/
   levels: manager_basic
   salary: 165000
@@ -44,7 +44,7 @@
   apply:
   open: false
-- title: "Accounting & External Reporting Manager"
+- title: "Manager, Accounting & External Reporting"
   description: /job-families/finance/accounting-and-external-reporting-manager
   levels: manager_basic
   salary: 135000
@@ -109,7 +109,7 @@
 - title: "Candidate Experience Specialist"
   description: /job-families/people-ops/candidate-experience-specialist
-  levels: ic_basic
+  levels: ces
   salary: 77000
   apply:
   open: false
@@ -247,9 +247,9 @@
   apply:
   open: false
-- title: "Diversity and Inclusion Partner"
+- title: "Diversity and Inclusion"
   description: /job-families/people-ops/diversity-inclusion-partner/
-  levels: basic
+  levels: people_generalist
   salary: 120000
   apply:
   open: false
@@ -261,23 +261,16 @@
   apply:
   open: true
-- title: "Employment Branding Lead"
+- title: "Talent Brand Manager"
   description: /job-families/people-ops/employment-branding-specialist/
   levels: basic
   salary: 104000
   apply:
   open: false
-- title: "Engineering Management, Infrastructure"
-  description: /job-families/engineering/engineering-management/infrastructure/
-  levels: false
-  salary: 252000
-  apply:
-  open: false
-
-- title: "Engineering Management, Quality"
+- title: "Manger, Quality Engineering"
   description: /job-families/engineering/engineering-management-quality/
-  levels: false
+  levels: manager_only
   salary: 203000
   apply:
   open: false
@@ -352,9 +345,9 @@
   apply:
   open: false
-- title: "Frontend Engineering Manager"
+- title: "Manager, Frontend Engineering"
   description: /job-families/engineering/frontend-engineering-manager/
-  levels: false
+  levels: manager_only
   salary: 183400
   apply:
   open: false
@@ -373,9 +366,9 @@
   apply:
   open: false
-- title: "Engineering Manager, Growth"
+- title: "Manager, Growth Engineering"
   description: /job-families/engineering/engineering-management-growth/
-  levels: false
+  levels: manager_only
   salary: 224000
   apply:
   open: false
@@ -401,7 +394,7 @@
   apply:
   open: false
-- title: "Internal Audit Manager"
+- title: "Manager, Internal Audit"
   description: /job-families/finance/internal-audit-manager/
   levels: manager_basic
   salary: 140000
@@ -410,14 +403,14 @@
 - title: "Internal Auditor"
   description: /job-families/finance/senior-internal-auditor/
-  levels: basic
+  levels: ic_basic
   salary: 100000
   apply:
   open: false
 - title: "Internal Strategy Consultant" # Staff Level Position
   description: /job-families/chief-executive-officer/internal-strategy-consultant/
-  levels: false
+  levels: manager_only
   salary: 163800 # 117000 x 1.4
   apply:
   open: false
@@ -429,7 +422,7 @@
   apply:
   open: false
-- title: "IT Manager"
+- title: "Manager, IT"
   description: /job-families/finance/manager-it/
   levels: manager_basic
   salary: 140000
@@ -443,9 +436,9 @@
   apply:
   open: false
-- title: "Learning and Development Partner"
+- title: "Learning and Development"
   description: /job-families/people-ops/learning-development-specialist/
-  levels: basic
+  levels: people_generalist
   salary: 120000
   apply:
   open: false
@@ -501,7 +494,7 @@
 - title: "Paralegal"
   description: /job-families/legal/paralegal/
-  levels: payroll_basic
+  levels: basic
   salary: 95000
   apply:
   open: false
@@ -557,7 +550,7 @@
   apply:
   open: false
-- title: "Procurement Manager"
+- title: "Manager, Procurement"
   description: /job-families/finance/procurement-manager/
   levels: manager_basic
   salary: 155000
@@ -592,9 +585,9 @@
   apply:
   open: false
-- title: "Product Marketing Management"
+- title: "Manager, Product Marketing"
   description: /job-families/marketing/product-marketing-management/
-  levels: false
+  levels: manager_only
   salary: 207200
   apply:
   open: false
@@ -676,7 +669,7 @@
   apply:
   open: false
-- title: "Sales Commissions Manager"
+- title: "Manager, Sales Commissions"
   description: /job-families/sales/sales-commissions-manager/
   levels: manager_basic
   salary: 150000
@@ -690,7 +683,7 @@
   apply:
   open: false
-- title: "Sales Systems Manager" # (Business Systems Admin Manager)
+- title: "Manager, Sales Systems" # (Business Systems Admin Manager)
   description: /job-families/sales/senior-manager-sales-systems/
   levels: manager_basic
   salary: 154000
@@ -718,9 +711,9 @@
   apply:
   open: false
-- title: "Security Management"
+- title: "Manager, Security"
   description: /job-families/engineering/security-management/
-  levels: false
+  levels: manager_only
   salary: 226800
   apply:
   open: false
@@ -734,7 +727,7 @@
 - title: "Solutions Manager"
   description: /job-families/sales/sr-solutions-manager/
-  levels: engineering_ic
+  levels: product_manager
   salary: 178000
   apply:
   open: false
@@ -746,7 +739,7 @@
   apply:
   open: false
-- title: "GitLab.com Support"
+- title: "Support Agent"
   description: /job-families/engineering/dotcom-support/
   levels: engineering_ic
   salary: 82000
@@ -823,9 +816,9 @@
   apply:
   open: false
-- title: "Technical Writing Manager"
+- title: "Manager, Technical Writing"
   description: /job-families/product/technical-writing-manager/
-  levels: false
+  levels: manager_only
   salary: 161000
   apply:
   open: false
@@ -851,9 +844,9 @@
   apply:
   open: false
-- title: "UX Manager"
+- title: "Manager, UX"
   description: /job-families/engineering/ux-management/
-  levels: false
+  levels: manager_only
   salary: 203000
   apply:
   open: false

data/sponsors.yml

+- name: AWS
+  logo: /images/events/gitlab-commit/sponsors/logo-aws.svg
+  landing: true
+  industry_type: 'technology'
+  asset_link: https://aws.amazon.com/
 - name: Google Cloud
   logo: /images/events/gitlab-commit/sponsors/logo-google-cloud.svg
   landing: true
@@ -13,6 +18,11 @@
   landing: true
   industry_type: 'technology'
   asset_link: https://www.cncf.io/
+- name: Tidelift
+  logo: /images/events/gitlab-commit/sponsors/logo-tidelift.svg
+  landing: true
+  industry_type: 'technology'
+  asset_link: https://tidelift.com/
 - name: Mattermost
   logo: /images/events/gitlab-commit/sponsors/logo-mattermost.svg
   landing: true

data/stages.yml

@@ -41,7 +41,7 @@ stages:
         backend_engineering_manager: Liam McAndrew
         frontend_engineering_manager: Dennis Tang
         support: Blair Lunceford
-        test_automation_engineers:
+        sets:
           - Sanad Liaquat
         uxm: Shane Bouchard
         ux:
@@ -64,7 +64,7 @@ stages:
         backend_engineering_manager: Liam McAndrew
         frontend_engineering_manager: Dennis Tang
         support: Blair Lunceford
-        test_automation_engineers:
+        sets:
           - Sanad Liaquat
         uxm: Shane Bouchard
         ux:
@@ -86,7 +86,7 @@ stages:
         cm: Suri Patel
         backend_engineering_manager: Liam McAndrew
         frontend_engineering_manager: Dennis Tang
-        test_automation_engineers:
+        sets:
           - Sanad Liaquat
         uxm: Shane Bouchard
         ux:
@@ -108,7 +108,7 @@ stages:
         backend_engineering_manager: Dan Jensen
         frontend_engineering_manager: Dennis Tang
         support: Blair Lunceford
-        test_automation_engineers:
+        sets:
           - Désirée Chevalier
         uxm: Shane Bouchard
         ux:
@@ -156,7 +156,7 @@ stages:
         backend_engineering_manager: Sean McGivern
         frontend_engineering_manager: Donald Cook
         support: Ben Prescott
-        test_automation_engineers:
+        sets:
           - Walmyr Lima e Silva Filho
         uxm: Shane Bouchard
         ux:
@@ -179,7 +179,7 @@ stages:
         backend_engineering_manager: John Hope
         frontend_engineering_manager: Donald Cook
         support: TBD
-        test_automation_engineers:
+        sets:
           - Walmyr Lima e Silva Filho
         uxm: Shane Bouchard
         ux:
@@ -201,7 +201,7 @@ stages:
         backend_engineering_manager: John Hope
         frontend_engineering_manager: Donald Cook
         support: TBD
-        test_automation_engineers:
+        sets:
           - Walmyr Lima e Silva Filho
         uxm: Shane Bouchard
         ux:
@@ -245,13 +245,13 @@ stages:
       source_code:
         name: Source Code
         pm: James Ramsay (Interim)
-        pmm: John Jeremiah
+        pmm: Jordi Mon
         cm: Suri Patel
         backend_engineering_manager: Michelle Gill
         frontend_engineering_manager: André Luís
         handbook: engineering/development/dev/create-source-code-be
         support: TBD
-        test_automation_engineers:
+        sets:
           - Mark Lapierre
         uxm: Shane Bouchard
         ux:
@@ -268,13 +268,13 @@ stages:
       knowledge:
         name: Knowledge
         pm: Christen Dybenko
-        pmm: John Jeremiah
+        pmm: Jordi Mon
         cm: Suri Patel
         backend_engineering_manager: Darva Satcher
         frontend_engineering_manager: André Luís
         handbook: engineering/development/dev/create-knowledge-be
         support: TBD
-        test_automation_engineers:
+        sets:
           - Tomislav Nikić
         uxm: Shane Bouchard
         ux:
@@ -295,7 +295,7 @@ stages:
         frontend_engineering_manager: André Luís
         handbook: engineering/development/dev/create-editor-be
         support: TBD
-        test_automation_engineers:
+        sets:
           - Tomislav Nikić
         uxm: Shane Bouchard
         ux:
@@ -314,13 +314,13 @@ stages:
       editor:
         name: Editor
         pm: Kai Armstrong
-        pmm: John Jeremiah
+        pmm: Jordi Mon
         cm: Suri Patel
         backend_engineering_manager: Darva Satcher
         frontend_engineering_manager: André Luís
         handbook: engineering/development/dev/create-editor-be
         support: TBD
-        test_automation_engineers:
+        sets:
           - Tomislav Nikić
         uxm: Shane Bouchard
         ux:
@@ -350,7 +350,7 @@ stages:
         backend_engineering_manager: ZJ (Interim)
         frontend_engineering_manager: Tim Z (Interim)
         support: Will Chandler
-        test_automation_engineers:
+        sets:
           - Mark Lapierre
         uxm: Shane Bouchard
         ux:
@@ -373,7 +373,7 @@ stages:
         backend_engineering_manager: ZJ (Interim)
         frontend_engineering_manager: Tim Z (Interim)
         support: TBD
-        test_automation_engineers:
+        sets:
           - Mark Lapierre
           - Tomislav Nikić
         uxm: Shane Bouchard
@@ -412,7 +412,7 @@ stages:
         backend_engineering_manager: Elliot Rushton
         frontend_engineering_manager: Daniel Cipoletti
         support: Namho Kim
-        test_automation_engineers:
+        sets:
           - Zeff Morgan
         uxm: Nadia Udalova
         ux:
@@ -434,7 +434,7 @@ stages:
         backend_engineering_manager: Elliot Rushton
         frontend_engineering_manager: Daniel Cipoletti
         support: Namho Kim
-        test_automation_engineers:
+        sets:
           - Zeff Morgan
         uxm: Nadia Udalova
         ux:
@@ -453,7 +453,7 @@ stages:
         backend_engineering_manager: Elliot Rushton
         frontend_engineering_manager: Daniel Cipoletti
         support: Namho Kim
-        test_automation_engineers:
+        sets:
           - Zeff Morgan
         uxm: Nadia Udalova
         ux:
@@ -555,7 +555,7 @@ stages:
         backend_engineering_manager: Thomas Woodham
         frontend_engineering_manager: Lukas Eipert (Interim)
         support: Thiago Presa
-        test_automation_engineers:
+        sets:
           - Aleksandr Soborov
         uxm: Valerie Karnes
         ux:
@@ -567,7 +567,7 @@ stages:
           channel: g_secure-static-analysis
           alias: secure_static_analysis_be
         gitlab_group: gitlab-org/secure/static-analysis-be
-      
+
         internal_customers:
           - Security Department
           - Engineering Department
@@ -583,7 +583,7 @@ stages:
         backend_engineering_manager: Seth Berger
         frontend_engineering_manager: Lukas Eipert (Interim)
         support: Thiago Presa
-        test_automation_engineers:
+        sets:
           - Aleksandr Soborov
         uxm: Valerie Karnes
         ux:
@@ -611,7 +611,7 @@ stages:
         backend_engineering_manager: Olivier Gonzalez (Interim)
         frontend_engineering_manager: Lukas Eipert (Interim)
         support: Greg Myers
-        test_automation_engineers:
+        sets:
           - Aleksandr Soborov
         uxm: Valerie Karnes
         ux:
@@ -735,7 +735,7 @@ stages:
         backend_engineering_manager: Seth Engelhard (Interim)
         frontend_engineering_manager: Jean du Plessis
         support: Lewis Brown
-        test_automation_engineers:
+        sets:
           - Dan Davison
         uxm: Aaron K. White
         ux:
@@ -760,7 +760,7 @@ stages:
         backend_engineering_manager: Nicholas Klick
         frontend_engineering_manager: Jean du Plessis
         support: Lewis Brown
-        test_automation_engineers:
+        sets:
           - Dan Davison
         uxm: Aaron K. White
         ux:
@@ -1119,7 +1119,7 @@ stages:
         frontend_engineering_manager: André Luís (Interim)
         support: Aric Buerer
         uxm: Jacki Bauer
-        test_automation_engineers:
+        sets:
           - Jennie Louie
         tech_writer: Evan Read
         slack:
@@ -1145,7 +1145,7 @@ stages:
         gitlab_group: gitlab-org/memory-team
         handbook: engineering/development/enablement/memory/
         cm: Erica Lindberg
-        test_automation_engineers:
+        sets:
           - Grant Young
           - Nailia Iskhakova
         support: TBD

data/webcasts.yml

@@ -42,8 +42,8 @@
     * Success stories from this approach
     
 - url: mastering-continuous-development-spanish
-  title: Dominando el Desarrollo Contínuo de Software
-  subtitle: Elimina las complejidades en la cadena de herramientas y escala con CI/CD integrado de GitLab
+  title: Dominando el Desarrollo Continuo de Software
+  subtitle: Elimina las complejidades de su cadena de herramientas y escala con CI/CD integrado de GitLab
   date: December 11th, 3:00 PM Argentina and Chile / 1:00 PM Colombia / 12:00 PM Mexico
   form: 1592
   success_message: "Gracias por registrarte. Recibirá un correo electrónico con detalles adicionales de la transmisión por Internet."
@@ -59,7 +59,7 @@
     ### En este webcast, cubriremos:
     * Tres enfoques principales para la metodología de desarrollo continuo de software
-    * Los beneficios de las prácticas de Integración, Entrega e Implementación Contínua
+    * Los beneficios de las prácticas de integración, entrega e implementación continua
     * Demostración de un pipeline de CI/CD de GitLab para construir, probar, implementar y monitorear su código
     
 - url: mastering-continuous-development-portuguese
@@ -72,15 +72,15 @@
   description: "Aprenda sobre o desenvolvimento contínuo de software e como o CI/CD integrado da GitLab pode ajudá-lo a acelerar seu ciclo de desenvolvimento de software em 200%."
   content: |
-    **Não deixe que as suas ferramentas te atrasem.** Ao aplicar métodos contínuos em suas práticas de desenvolvimento, ter o aplicativo certo para apoiar sua iniciativa é essencial para o seu sucesso.
+    **Não deixe que as suas ferramentas te atrasem.** Ao aplicar métodos contínuos em suas práticas de desenvolvimento, ter o aplicativo certo para apoiar a sua iniciativa é essencial para o seu sucesso.
     
-    Os plug-ins tradicionais de CI/CD, como o Jenkins, não são escaláveis, pois conectá-lo a todas as diferentes ferramentas do seu stack de tecnologia adiciona complexidade e pontos de falha ao processo. Quando a sua ferramenta de CI/CD está pronta para usar desde o começo ,sem necessidade de integrar, a manutenção e o gerenciamento são simplificados, permitindo que você obtenha produtividade mais rapidamente.
+    Os plug-ins tradicionais de CI/CD, como o Jenkins, não são escaláveis, pois conectá-lo a todas as diferentes ferramentas do seu stack de tecnologia adiciona complexidade e pontos de falha ao processo. Quando a sua ferramenta de CI/CD está pronta para usar desde o começo, sem necessidade de integrar, a manutenção e o gerenciamento são simplificados, permitindo que você obtenha produtividade mais rapidamente.
     
-    Aprenda sobre o desenvolvimento contínuo de software e como o CI/CD integrado da GitLab pode ajudá-lo a acelerar seu ciclo de desenvolvimento de software em 200%.
+    Aprenda sobre o desenvolvimento contínuo de software e como o CI/CD integrado da GitLab pode ajudá-lo(a) a acelerar seu ciclo de desenvolvimento de software em 200%.
     ### Neste webcast, falaremos sobre:
     * Três abordagens principais para a metodologia de desenvolvimento contínuo de software
-    * Os benefícios das práticas de Integração, Entrega e Implantação Contúnua
+    * Os benefícios das práticas de integração, entrega e implementação contínua
     * Demonstração do pipeline de CI/CD da GitLab para construir, testar, implementar e monitorar o seu código
     
 - url: mastering-continuous-development-fr

source/company/culture/all-remote/hiring/index.html.md

@@ -41,7 +41,7 @@ True to those values, GitLab strives to hire team members who are passionate, em
 Hiring an all-remote team from across the globe allows GitLab to pay local rates, which you can learn more about [on the company blog](/blog/2019/02/28/why-we-pay-local-rates/). By hiring brilliant minds in locations with lower costs of living, GitLab is able to save money to hire even more people as we scale our business. 
-For now, this gives GitLab a tremendous competitive advantage. We are sourcing talent from places that most companies overlook, and we're creating [a more diverse team](/company/culture/inclusion/#fully-distributed-and-completely-connected) all the while. We hope that this advantage fades, as more companies embrace all-remote and widen their recruiting funnel beyond the usual talent centers.
+For now, this gives GitLab a tremendous competitive advantage. We are sourcing talent from places that most companies overlook, and we're creating [a more diverse team](/company/culture/inclusion/#fully-distributed-and-completely-connected) all the while. We hope that [this advantage fades](/company/culture/all-remote/vision/#diminishing-competitive-advantage), as more companies embrace all-remote and widen their recruiting funnel beyond the usual talent centers.
 We've published our [hiring process](/handbook/hiring/interviewing/), including example screening questions, in our handbook. 
 While this may be unique, we see it as simply staying true to our [transparency value](/handbook/values/#transparency). The process shouldn't be a mystery. 
@@ -56,6 +56,57 @@ We are growing rapidly and continuously expanding our hiring capabilities in oth
 Learn more at our [Country Hiring Guidelines](/jobs/faq/#country-hiring-guidelines) page.
+## What qualities do you look for in remote hires?
+
+Put simply, we look for candidates that align with our [values](/handbook/values/) and inform us that said values resonate with them.
+
+Having prior experience working remotely is appreciated, but by and large we look for the same attributes that a colocated company would. Qualities such as timeliness, dependability, respect, a heart of collaboration, perseverance, empathy, kindness, and ambition are valued.  
+
+Great self-awareness and expert communication skills are necessary to thrive in an all-remote setting. 
+
+Even if someone has not worked in a remote environment before, chances are high that they have spent time on work while outside of their office. Consider asking candidates for examples of how they managed those instances (e.g. working while traveling, advancing a university project while away from campus, etc.), looking specifically for how they embrace autonomy and [blameless problem solving](/handbook/values/#blameless-problem-solving). 
+
+Qualities that may be considered unique to a remote workplace are listed below.
+
+1. Appreciation for [self-learning and self-service](/company/culture/all-remote/self-service/)
+1. Appreciation for [documentation](/company/culture/all-remote/management/#scaling-by-documenting) 
+1. Proven ability to be a [manager of one](/handbook/values/#managers-of-one) 
+1. Proven ability to work [asynchronously](/company/culture/all-remote/management/#asynchronous)
+
+When asked during an [INSEAD](http://insead.edu/) case study [interview](https://youtu.be/EuGsen3FxXc) if anyone could learn to work well in an all-remote setting, GitLab co-founder and CEO Sid Sijbrandij provided the following reply.
+
+> What's really important in all-remote is that you are a [manager of one](/handbook/values/#managers-of-one). 
+>
+> You're not going to have someone expecting you at the office. You're not going to have hour-to-hour hand-holding, so you have to be able to work independently and manage yourself. 
+>
+> For [asynchronous communication](/company/culture/all-remote/management/#asynchronous), which is essential to bridge time zones, it is important that you can write well — that you're concise and precise in your written communication. — *GitLab co-founder and CEO Sid Sijbrandij*
+
+## Make your strategy public
+
+You cannot expect to hire people who are passionate about executing your strategy if you only share the strategy *after* they are onboard. 
+
+Make your strategy public and ensure that applicants are aware of it, along with your values, during the interview process. You can hire someone with excellent attributes, but if they are not aligned with your strategy and values, it may be difficult for that person to thrive within your organization. 
+
+<!-- blank line -->
+<figure class="video_container">
+  <iframe src="https://www.youtube.com/embed/EuGsen3FxXc?start=2493" frameborder="0" allowfullscreen="true"> </iframe>
+</figure>
+<!-- blank line -->
+
+In the [GitLab Unfiltered](https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A) video above, GitLab co-founder and CEO Sid Sijbrandij discusses hiring (amongst other topics) with researchers from [INSEAD](https://www.insead.edu/). 
+
+> It's not about having the best strategy. The strategy tends to be obvious. It's about executing the best.
+>
+> To execute the best, it needs to be super clear. Nothing is clearer than writing it down explicitly and having the whole world be able to amend it.
+>
+> People need to be aligned to it. How can you have people aligned to your strategy if you only tell it after you hire them?
+>
+> You may hear something akin to: 'Our strategy is very important, and you need to be aligned to it! We'll only tell you after you join the company.'
+>
+> I think that's bananas. That's what every company in the world does. If your strategy is really important, you want to make sure people buy in *before* they join, and people that don't buy in don't actually join the company.
+>
+> Execution depends on people, and this allows us to attract the best people because [we are public about what we do](/company/strategy/). — *GitLab co-founder and CEO Sid Sijbrandij*
+
 ## Using video calls to interview and engage
 At GitLab, we do not rely on in-person interviews. Instead, we utilize [Zoom](/handbook/tools-and-tips/#zoom) to connect with candidates via [video calls](/handbook/communication/#video-calls). 

source/company/culture/all-remote/learning-and-development/index.html.md

@@ -15,6 +15,14 @@ On this page, we're detailing how [learning and development (L&D)](/handbook/peo
 ## How does learning and development (L&D) work in an all-remote environment?
+<!-- blank line -->
+<figure class="video_container">
+  <iframe src="https://www.youtube.com/embed/trYrbPYOf_c" frameborder="0" allowfullscreen="true"> </iframe>
+</figure>
+<!-- blank line -->
+
+*A GitLab Live Learning session, embedded above and uploaded to [GitLab Unfiltered](https://youtu.be/QTPeyRW766Q), is an example of L&D iteration.*
+
 Credit the conventional classroom environment for implying that learning is best achieved in a face-to-face, in-person setting. That mentality largely translates to the working world, where it is assumed that learning and development is best suited for boardrooms and lecture halls.
 In an all-remote company, learning and development can still occur on a face-to-face basis, albeit through webcams and video chat software. Even in colated organizations, a growing percentage of learning and development — particularly required training courses assigned by human resource departments — are delivered via webcast.
@@ -45,7 +53,7 @@ Most challenges associated with all-remote L&D can be addressed at the [hiring s
 </figure>
 <!-- blank line -->
-In the [GitLab Unfiltered](https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A) video above, GitLab team members discuss the challenges and reasoning behind intentional documentation with Miki and Sandra from [Job Portraits](https://www.jobportraits.com/).
+*In the [GitLab Unfiltered](https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A) video above, GitLab team members discuss the challenges and reasoning behind intentional documentation with Miki and Sandra from [Job Portraits](https://www.jobportraits.com/).*
 Learning involves much more than comprehending what's necessary to complete a job. In fact, we hope candidates aspire to learn about GitLab's [history](/company/history/), [all-remote culture](/company/culture/all-remote/), and [values](/handbook/values/) prior to joining the company.
@@ -57,7 +65,7 @@ Particularly in all-remote companies — where everything from interviewing to o
 GitLab's Handbook would [cover thousands of pages if printed](/handbook/about/#count-handbook-pages). Each page is loaded with institutional knowledge on important topics like [hiring](/handbook/hiring/index.html), [values](/handbook/values/), and [benefits](/handbook/benefits/index.html), Content is contributed, refreshed, and refined by hundreds of team members across the company.
-We encourage other all-remote companies to adopt this handbook first approach. Simply, we default to adding knowledge to our handbook *before* disseminating elsewhere. Learn more about [GitLab's Handbook usage](/handbook/handbook-usage/).
+We encourage other all-remote companies to adopt this [handbook first approach](/handbook/handbook-usage/#why-handbook-first). Simply, we default to adding knowledge to our handbook *before* disseminating elsewhere. Learn more about [GitLab's Handbook usage](/handbook/handbook-usage/).
 From a learning and development standpoint, this approach ensures that all team members have access to all learnings — past, present, and future — at all times. This is a highly [inclusive](/company/culture/inclusion/) way to manage knowledge, and it reflects our [mission](/company/strategy/#mission) to change all creative work from read-only to read-write so that **everyone can contribute**.
@@ -69,6 +77,14 @@ This is powerful in that it encourages team members to continually be mindful of
 This creates an atmosphere where all team members are hungry to learn from one another. Indeed, those in charge of learning and development in an all-remote company should look to colleagues across the organization to understand which areas are most misunderstood, and what modules would generate the most interest.
+## Responsibilities from managers and leaders
+
+GitLab's [100% remote culture](https://about.gitlab.com/company/culture/all-remote/) and our workplace methodologies are highly unique. You should not expect to transfer the norms of colocated corporations into a work from anywhere scenario. Those who thrive at GitLab take the opportunity to drop prior workplace baggage at the door, embrace a liberating and empowering [set of values](https://about.gitlab.com/handbook/values/), and give themselves permission to truly operate differently.
+
+So differently, in fact, that many of GitLab's most effective [processes](https://about.gitlab.com/company/culture/all-remote/management/) would be discouraged or forbidden in conventional corporations.
+
+Hence, GitLab managers are [expected](/handbook/leadership/#management-group) to coach their reports to utilize [asyncronous communication](/company/culture/all-remote/management/#asynchronous), be [handbook-first](/handbook/handbook-usage/#why-handbook-first), design an [optimal workspace](/company/culture/all-remote/workspace/), and understand the importance of [self-learning/self-service](/company/culture/all-remote/self-service/). 
+
 ## Trust and communication
 <!-- blank line -->
@@ -77,11 +93,11 @@ This creates an atmosphere where all team members are hungry to learn from one a
 </figure>
 <!-- blank line -->
-In the [GitLab Unfiltered](https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A) video above, senior backend engineer Charlie A. describes her experience working in an all-remote setting, from onboarding to fully embracing autonomy.
+*In the [GitLab Unfiltered](https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A) video above, senior backend engineer Charlie A. describes her experience working in an all-remote setting, from onboarding to fully embracing autonomy.*
 > I've been challenged to be able to say, 'It's OK for me to not know this.' It's OK for me to ask somebody else and not feel bad about it. It's OK to not know everything. In this kind of setting, it's impossible for one person to know everything, so you have to rely on your coworkers to tell you.
 >
-> Impeccable communication and trust is the backbone of any relationship. When it comes to a working environment, [those elements] make it much easier to do what you need to do. - [Charlie A. — Senior Backend Engineer](https://gitlab.com/cablett)
+> Impeccable communication and trust is the backbone of any relationship. When it comes to a working environment, [those elements] make it much easier to do what you need to do. - [*Charlie A. — Senior Backend Engineer*](https://gitlab.com/cablett)
 Companywide trust and impeccable communication serve as the bedrock for learning and development in any company, all-remote organizations included. This relies on a [set of values](/handbook/values/) that encourages behaviors which are at odds with micromanagement.
@@ -97,12 +113,12 @@ Proper learning and development requires more than a curriculum. It requires an
 </figure>
 <!-- blank line -->
-In the Traction Conference [video](https://youtu.be/CH-NHoBOeho) above, GitLab co-founder and CEO Sid Sijbrandij shares how onboarding works within an all-remote setting with Frederic Lardinois of [TechCrunch](https://techcrunch.com/).
+*In the Traction Conference [video](https://youtu.be/CH-NHoBOeho) above, GitLab co-founder and CEO Sid Sijbrandij shares how onboarding works within an all-remote setting with Frederic Lardinois of [TechCrunch](https://techcrunch.com/).*
 At a high level, this is how new team members are onboarded at GitLab.
 * On a new hire's first day, they are invited to create a GitLab account
-* Within their GitLab account is an [onboarding issue](https://gitlab.com/gitlab-com/people-ops/employment/blob/master/.gitlab/issue_templates/onboarding.md#all-gitlabbers) with over 200 tasks
+* Within their GitLab account is an [onboarding issue](https://gitlab.com/gitlab-com/people-ops/employment/blob/master/.gitlab/issue_templates/onboarding.md#all-gitlabbers) with over 200 tasks, including [GitLab's Guide to Starting a Remote Role](/company/culture/all-remote/getting-started/)
   * Onboarding items are extremely prescriptive
   * Rather than bundling a complex series of asks into one "task," as is common elsewhere, GitLab strives to remove ambiguity
 * Each new hire is assigned an Onboarding Buddy as an added resource beyond the individual's manager
@@ -141,7 +157,7 @@ From a learning and development standpoint, this transparency is vital in provid
 </figure>
 <!-- blank line -->
-In the [video](https://www.youtube.com/watch?v=Cxs5EMHNf6g) above, published on the [GitLab Unfiltered YouTube channel](https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A), [Chrissie B.](https://gitlab.com/cbuchanan) documents a question from a fellow GitLab team member — "*How do you create a blog post as a non-technical user?*" — by capturing the answer and walkthrough on video.
+*In the [video](https://www.youtube.com/watch?v=Cxs5EMHNf6g) above, published on the [GitLab Unfiltered YouTube channel](https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A), [Chrissie B.](https://gitlab.com/cbuchanan) documents a question from a fellow GitLab team member — "How do you create a blog post as a non-technical user?" — by capturing the answer and walkthrough on video.*
 This is a classic example of a GitLab team member answering once so that multitudes will benefit, reinforcing our [Efficiency value](/handbook/values/#efficiency). Notice that Chrissie's primary function is not within learning and development, yet her contribution leads to a more educated workforce.
@@ -151,7 +167,7 @@ This is a classic example of a GitLab team member answering once so that multitu
 </figure>
 <!-- blank line -->
-In the [video](https://www.youtube.com/watch?v=7RbVQwU69H0) above, published on the [GitLab YouTube channel](https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg), a member of the People Operations team conducts a training on decision making. Being unable to attend in person matters not, as the training is archived for later viewing.
+*In the [video](https://www.youtube.com/watch?v=7RbVQwU69H0) above, published on the [GitLab YouTube channel](https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg), a member of the People Operations team conducts a training on decision making. Being unable to attend in person matters not, as the training is archived for later viewing.*
 ## Ask Me Anything (AMA), group conversations, and key meetings
@@ -167,7 +183,9 @@ Reinforcing GitLab's [Transparency value](/handbook/values/#transparency), we ro
 </figure>
 <!-- blank line -->
-In the [video](https://www.youtube.com/watch?v=MvxSF_c3ztg) above, published on the [GitLab Unfiltered YouTube channel](https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A), GitLab CMO Todd Barr conducts an AMA. More AMAs are listed below.
+*In the [video](https://www.youtube.com/watch?v=MvxSF_c3ztg) above, published on the [GitLab Unfiltered YouTube channel](https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A), GitLab CMO Todd Barr conducts an AMA.* 
+
+More AMAs are listed below.
 * [AMA with GitLab co-founder and CEO Sid Sijbrandij](https://www.youtube.com/watch?v=u1jv1HOc8fw)
 * [AMA with David Hornik (Board Member)](https://www.youtube.com/watch?v=LwZNbF6_PX0)
@@ -186,7 +204,9 @@ Learn more about [Group Conversations in GitLab's Handbook](/handbook/people-gro
 </figure>
 <!-- blank line -->
-In the [video](https://www.youtube.com/watch?v=MN3mzvbgwuc) above, published on the [GitLab YouTube channel](https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg), GitLab co-founder and CEO Sid Sijbrandij leads a Functional Group Update Training. More Group Conversations are listed below.
+*In the [video](https://www.youtube.com/watch?v=MN3mzvbgwuc) above, published on the [GitLab YouTube channel](https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg), GitLab co-founder and CEO Sid Sijbrandij leads a Functional Group Update Training.* 
+
+More Group Conversations are listed below.
 * [Infrastructure Group Conversation](https://www.youtube.com/watch?v=CrHpG-dt9yk)
 * [Growth Group Conversation](https://youtu.be/Sd21OgztLws?t=104)
@@ -208,7 +228,7 @@ Learn more about [GitLab's OKRs](/company/okrs/).
 </figure>
 <!-- blank line -->
-In the [video](https://youtu.be/FXpBol1TwiI) above, published on the [GitLab Unfiltered YouTube channel](https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A), members of GitLab's marketing team discuss a plan to operationalize marketing metrics for use in KPI and OKR presentations.
+*In the [video](https://youtu.be/FXpBol1TwiI) above, published on the [GitLab Unfiltered YouTube channel](https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A), members of GitLab's marketing team discuss a plan to operationalize marketing metrics for use in KPI and OKR presentations.*
 For each GitLab executive, we hold a monthly call to discuss Key Performance Indicators (KPI) and Objectives and Key Results (OKR). This goes well beyond the usual scope of learning and development by providing on-the-job education on metrics that impact various parts of the company. Said another way, learning and development has greater impact when it's mapped to something tangible.