GitLab Summits

What, where, and when

We try to get together every 9 months or so to get face-time with one another, build community, and get some work done! Since our team is scattered all over the globe, we try to plan a different location for each Summit.

The summit is not a mandatory trip or a department offsite, nor is it a vacation or incentive trip. It's a chance for everyone to meet fellow GitLabbers across all departments and regions: part team building, part education, part customer interaction, and hopefully all fun.


The goal of our Summits is to get to know the people in the GitLab community better. The better you know people, the easier it is to collaborate. We want to build trust between groups.

Social media

You are encouraged to take pictures and post on social media. If you take pictures of people not on the podium please ask their permission. Please consider using the hashtag #GitLabSummit Our social media guidelines still apply.


All team members of the GitLab company, SOs, Core Team, contributors, customers, press, and anyone interested in joining.


Upcoming Summit

The next summit coming up will be in May 2019 in New Orleans, Louisiana in the United States! All info to prepare for this will be on the project page as soon as we've signed with a hotel


Counting down to May 2019!

Summit in Cape Town, South Africa

Last August, in 2018, our team had grown to about 320 people. Over 260 of them came to Cape Town, South Africa. We had over 85 SOs present and were also joined by a handful of customers, our advisors, and investors.

GitLab Summit - South Africa - 2018In August 2018, the whole team had grown to 320 GitLabbers!

Summit in Crete, Greece

By October 2017 we had 200 team members and 65 significant others getting together in Greece to enjoy the beautiful islands of Crete and Santorini.

The GitLab Team in October 2017When October 2017 came around, the whole team already counted 200 GitLabbers!

Summit in Cancun, Mexico

In January 2017, we met in Cancun, Mexico, where roughly 150 team members and 50 significant others flew in from 35 different countries.

The GitLab team in January 2017In January 2017, the whole team had grown to 150 GitLabbers!

Summit in Austin, Texas

In May 2016, our team of 85 met up in Austin, TX to see if they were (still) as awesome as they seemed on Google Hangout.

Here's some footage our team put together to show how much fun we had:

The GitLab team in May 2016Back in May 2016, the whole team was a total of 85 GitLabbers

Summit in Amsterdam, the Netherlands

Here are some impressions from our second summit in October 2015.

The GitLab team in October 2015In October 2015, the whole team had grown to almost 30 GitLabbers!

Summit in Novi Sad, Serbia

First summit, less then 10 people attending; highlight was lunch at Marin's mom's home in October 2013.

GitLab Summit - Serbia - 2013

Leisure time around the Summit

Bring your significant other

Having your children join you

Children are strongly discouraged from attending. We have observed from past summits that contributors who have chosen to bring children spend significantly less time collaborating with GitLab coworkers. Accordingly, we are requesting that if you must travel with family members you fully engage in as many group activities as you are physically able, invite team members to join you during meals, attend all company meetings, and recognize that the Summit is an investment in the continued growth of the organization.

Leaders at the Summit

For the context of this video, please see the summit challenges in the Greece recap

Company leaders who attend the summit should take the opportunity to engage with GitLabbers across the organization and should be mindful of silos and favoritism as they observe team dynamics.

Be conscious

Leaders should consider themselves "hosts" of the event, which means that, in addition to facilitating team building and interaction, they should be aware of potential issues that could arise during the event related to the behavior, health, and safety guidelines below. These include:

What should managers do?

Who to contact?


Extraverts and Introverts

Remember that you and your co-workers may have different personality types in terms of how you interact with others in large social situations. Consider the differences between extraverts and introverts:




References: Are Extraverts Happier Than Introverts? Psychology Today Are You an Extravert, Introvert, or Ambivert?

Health and safety

Cultural Impacts and Differences

It is important to recognize that people from different cultures have different ways of saying things, different body language, different ways of dressing/attire and even different ways of looking at things. You can review examples of typical cultural differences on the Center of Intercultural Competence.

Summit attendees should also remember:

Lost in Translation

Translation tends to sound easier than it is. People often think that it is just a matter of replacing each source word with a corresponding translated word, and then you are done. Assume best intent from your fellow team members and use it as an opportunity start a new dialogue. For more information you can review the following articles on LTC Language Solutions


Great WiFi is essential to the success of the summit. We can't have everyone in one location and not have excellent internet.

  1. Main room needs one access point for every 40 people attending in the main room and management, we have our own equipment but need to buy more.
  2. We need two different uplinks from two different providers.
  3. We need our own router between the uplinks and the WiFi.
  4. We need wired connections to the WiFi access points.
  5. We need to have WiFi working before the executive team arrives.
  6. We need very reliable fast connections if we are livestreaming during the summit.
  7. We need a map of the property with all wiring and access points drawn in 3 months before the summit starts.

Logistical basics


The following should be assigned and/or arranged a month before the Summit:

Summit Sessions

GitLab Summits have variety of sessions: UGCs, workshops, presentations, etc. A summit isn’t a conference, its a "meeting of minds”. Its a place to connect and collaborate in an environment where everyone can contribute. We don’t present to our users and customers, they present to us.


UGC stands for “user generated content.” The goal is for a group to come together to produce something collectively. A UGC “user” can be anyone in the GitLab community: GitLabber, significant other, customer, contributors, etc. including “GitLab users” (e.g. someone who uses GitLab).

UGC attributes

  1. Everyone can contribute. a. Limit to 15 people. (i.e. Small enough so that everyone can share)
  2. Content is generated from the discussion, not prepared ahead of time.
 3. Each UGC has a google doc to capture notes. a. Pro tip: Set up offline access for Google Drive so you can take notes even if wifi is spotty. The doc is then ready to share once you can connect to the internet again.
 4. Sharing in real-time is optional. a. Everyone can contribute, not everyone must contribute. b. Some folks prefer to listen. c. Some folks prefer to think about the session then add comments to google doc later.
  3. Can be GitLab or non-GitLab related a. GitLab related: produce notes that can be shared. Decided later is any action needs to be taken. Create an MR together on-site. b. Non-Gitlab related: Just have a discussion about something you enjoy with other people who enjoy the same thing to build a relationship.
  4. Preparation needed: a. A google doc for the session b. A facilitator

How to facilitate a UGC

  1. Give a short introduction to the topic (about 2 minutes) for folks that may not be familiar.
  2. Ask some questions to get people talking then let the discuss flow organically. Some example questions:
 a. Why did you come to this session? b. You mentioned X, can you tell us more about that? c. , do you have any thoughts on this topic?
    • Good to ask someone this if they’ve been quiet or haven’t participated yet. Some folks are waiting for an invitation to speak and will appreciate being asked specifically to share. Some folks will say, “no thanks” and prefer to listen. Both are ok. d. <name>, we’d like to hear what you have to say, but first let’s allow <name> finish their thought. - Good to interrupt someone who has just interrupted someone else so that everyone can contribute and one person doesn’t dominate the conversation.

UGC results

The following are measures of a successful UGC: 
 1. Contribution: the more people contributing, the better.

  1. Thorough notes: a Google Doc full of notes. There’s no expectation to act on the notes. Once the session is complete, you can decide if there’s a next action.
  2. Relationship building: some UGCs won’t have a next-step action; they were simply opportunities for people who enjoy the same thing to build relationships. Examples might include board games, cooking, or mountain climbing.
  3. Tangible artifacts: assets produced by the group (e.g. an MR, a demo, a diagram, a song, etc.)

UGC coordination

Here's an overview of how this works during our summits.


  1. A workshop is interactive training (e.g. Rails Girls, Kubernetes 101, Speaker Training, etc.) 
  2. Everyone can participate. It’s a workshop, not a presentation. Everyone in the room should be able participate.
 3. Can be a small or large number of people. Larger groups may need multiple facilitators or coaches to ensure everyone can participate.
  3. Requires preparation and coordination ahead of time to facilitate a productive workshop. a. Room needs to be set up. b. Outline or the training needs to be created. c. Supplemental materials may to be created. d. Good WIFI may be required.
  4. Can be simple and lightweight (e.g. bring your laptop and learn: how to use git, how to make an MR, how to contribute to GitLab, etc. This is content that already exists in the handbook/website, but it can be very helpful to have someone walk you through it in person.)

Workshop results

The following are measures of a successful workshop.

  1. Equipping: People learn a new skill or improve an existing skill.
  2. Participation: Everyone has the opportunity to participate.


  1. Presentations are one-way, one-to-many communication mode (one person speaking many people listening.)
  2. One-way, one-to-many communication is easy to do remote while UGC-style, many-to-many discussion is harder to do remote.
  3. If a GitLabber has an idea for a presentation they should do this outside of the Summit (e.g. schedule a remote call, livestream or upload the recording to YouTube, link it in the training section of the handbook, etc.)
  4. Customers and Users presentations are good for the Summit so that more GitLabbers can hear from our customers and experience greater customer empathy.

Presentation results

The following are measures of a successful presentation.

  1. TODO: Add results

Team UGCs

Most UGCs can, and should, have diverse group of folks attending like GitLabbers from different teams, SOs, customers, etc. There should also be scheduled time for teams to have team-only UGCs to discuss their work, strategize, and problem solve.

  1. Functional groups meet together (e.g. East Sales, Pipe-to-Spend, Site Reliability Engineering, etc.)
  2. Cross-functional groups meet together (e.g. Plan, Create, Verify, etc.)
  3. Customers meet together without any GitLabbers in the room to talk freely to each other.

Live stream

  1. During the summit we'll have a live stream that is interactive (viewers ask questions).
  2. The live stream is a way to generate tangible hiring and marketing benefits, this will help to sustain the large discretionary expense of the summit.
  3. There will be only one mobile camera crew and it will be easy to recognize.
  4. With the mobile camera crew will be two GitLab team members, a moderator for the chat and a facilitator that will interact with other team members.
  5. We want the viewers (our team members that couldn't make it, the wider community, friends and family) to feel like participants instead of an audience. From time to time the facilitator will seek interaction by talking with team members.
  6. You can always decline to enter in a conversation with the facilitator, just like you can decline a conversation with another team member.
  7. If you don't want to be approached by the facilitator under any circumstances you can ask for an identifier from the organization.
  8. The facilitator will avoid taking to team members wearing the identifier, significant others, and children. Significant others that want to interact are very welcome to approach the facilitator themselves.
  9. Team members wearing the identifier and significant others might be visible in the shot as passers-by's. The camera crew try to avoid children passers-by's. As said elsewhere on this page we strongly discourage children from attending.