Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Customer Advisory Boards

GitLab Customer Advisory Boards

Purpose: To help foster DevOps transformation and adoption we are establishing a Customer Advisory Board, where we focus on sharing DevOps best practices and lessons learned with each other. We believe that transparency and sharing is a key way to help encourage the success of DevOps transformations. The GitLab customer advisory board is intended to be home to learning and collaboration so we can all experience success through DevOps transformation.

Members Executives/Champions for DevOps within their organizations

Frequency: We meet every quarter on the first Wednesday of the month at 11 a.m. Eastern for 2 hours

Membership: As of Feburary 2021, we have 30 customer members in the CAB.

Meeting Recordings Meetings are recorded for internal and member use. Members can seek these recordings by emailing CAB@gitlab.com

Recurring Content Our content plan for the CABs is determined by customer feedback on specific requests/topics as relayed via regular member surveys. We will frequently ask for GitLab Product Managers to join to present the vision for their assigned DevOps stage. Typical CAB's include customer breakout sessions, birds of a feather discussions and customer presentations, we aim for 80:20 customer driven conversations. The CAB Manager will follow up CAB's with an email to members that includes a link to watch the recording and review meeting notes.

Recorded CAB meetings Due to the private nature of the Customer Advisory Board, video recordings and presentations are not linked here. If you are a GitLab employee, please join our internal CAB slack channel (#cab-shared-internal) or email CAB@gitlab.com.

CAB Nomination Process

  1. SAL's can nominate their customers for CAB membership via the customer contact view in SFDC (Nominate as a Reference tab).
  2. Process outlined here
  3. Complete the relevant fields, tick the CAB reference type and the details will be forwarded to the Customer Reference Team for review.
  4. We will revert to the nominator with regards to the membership.

CAB Membership Criteria

Please view our CAB membership charter that renews our commitment to the CAB and sets member expectations.

CAB Membership Management

Once a customer has been successful in securing membership; the CAB manager will active the onboarding templates. If a customer retires from the CAB, the CAB Manager will activate the offboarding template.

Issue Templates - please select from the dropdown menu within the CAB Project

CAB Onboarding Template

CAB Offboarding Template

CAB Epics

See management epics below; each CAB sessions has its own linked issue to manage that session.

Epic FY2021

Epic FY2022

CAB Management Templates

Issue Templates that are activated to manage a CAB sesssion

CAB-Shared Slack channels

A number of our customers continue the conversation with each other and with our product team in the CAB-Shared Slack channel (#cab-shared). Because our customers are active in this channel, please be aware of content shared. We encourage GitLab team members to join our internal CAB slack channel (#cab-shared-internal) to stay up-to-date with regards to the CAB.

Communicating to our CAB customer members on the customer slack channel

Please raise an issue via this issue template to request consideration to communicate on this channel Please provide as much context about your announcement as possible, specifically around the relevance and value to the members.

TAMs managing their customer feedback from the Product CAB

Find TAM process for managing customer feedback from the Product CAB.

Process

  1. The Customer Reference Manager (CRM) creates the “CAB TAM Follow up” issue template in the CAB project and uploads links to the recordings etc
  2. The CRM tags the TAMs and TAM managers in the issue to review the CAB recordings/ notes and transcripts when their customer has attended the CAB
  3. The TAM create new issues in the Product repo as per agreed process based upon their customer feedback (links to the customer SFDC account as per standard process for reporting)
  4. If the issue already exists please add the CAB label provided and add the customer SFDC record
  5. The TAM tags the issue with the CAB label (CAB Takeaway+FQ+FY) so we can track CAB input into product)
  6. The CRM schedules an annual meeting with CS/TAM/Product teams to review the CAB Takeaway label board in the Product Repo

2021 Meeting Schedule

October 6, 2021

July 14, 2021

April 7, 2021

2020 Meeting Schedule

December 2020 and January 2021 CAB on hold due to program relaunch in Q1

November 4, 2020

October 7, 2020

September 2, 2020

August 5, 2020

July 1, 2020

June 3, 2020

May 6, 2020

April 21, 2020

March 4, 2020

February 5, 2020

2019 Meeting Schedule

GitLab In-Person CAB Meeting - October 15 & 16, 2019*

GitLab Product Roadmap Review - September 4, 2019

* GitLab Product Roadmap Review - August 7, 2019*

GitLab Product Roadmap review - July 10, 2019

GitLab Verify direction update - June 5, 2019

***GitLab In-Person CAB Review -May 1, 2019

In-Person CAB Meeting- April 18-19, 2019

GitLab Configure review- March 6, 2019

GitLab Geo review-February 6, 2019

GitLab Manage review - January 9, 2019

###2018 Meetings

GitLab Release review-December 5, 2018

GitLab Create review-November 7, 2018

GitLab Plan review-October 17, 2018

Kickoff Meeting-September 5, 2018

GitLab Special Interest Group

Purpose: We are forming Special Interest Groups to foster specific and focused discussions about how to apply DevOps practices and GitLab capabilities in specific domains such as planning, development, CI/CD, security, etc. These Special Interest Groups will encourage sharing and collaboration of DevOps best practices and lessons learned between users and GitLab.

We believe that transparency and sharing is a key way to help us all learn and improve how we deliver for our customers. GitLab special interest groups are intended to be home to learning and collaboration.

Members Technical utilizers and advocates of GitLab

Frequency: We will try to meet virtually every 6 to 8 weeks

Membership: Approximately 8-15 users, GitLab Product Manager

The CRM team will track the customers who are part of SIG's in this tracking sheet and update ReferenceEdge with their details. The management and delivery of the SIG program is driven by the relevant product area.

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license