On this page

GitLab Meetups Checklist

This guide is intended to help Meetup organizers run events that their community will love. Our aim is to be as comprehensive as possible to enable everyone to become an organizer, regardless of experience. We realize that we don't have all the answers so if you find anything incorrect, notice something missing, or identify other changes to be made, please open an issue for our team to review. Happy planning!


GitLab supports community leaders who want to organize meetups and tech events in their cities and hometowns. As the first single application for the entire DevOps lifecycle, all events that discuss and educate on the software development lifecycle and developer experience are eligible for GitLab support.

Our goal in supporting these events is to increase awareness of GitLab and Concurrent DevOps, and to better educate the technology community about the power of our application.

Who can contribute

At GitLab, we believe everyone can contribute. We support people who are interested in organizing events or growing existing communities. If you have experience organizing tech events or meetup groups, that is great - but it is not required. We're happy to work with first-time organizers, too.

The only requirements for organizers are a passion for GitLab and a belief in our mission.

Why should you get involved

The benefits to organizing an event are as varied as the people who organize them. Everyone has their own reasons. That said, for tech events specifically, we have identified a few common threads that tie organizers together:

How GitLab can help

GitLab supports meetup organizers with planning and logistics support, connections to speakers, GitLab swag, and financial support for food and beverages for your events.

Planning a meetup

Getting started

What to do ASAP

- topic:
  type: MeetUp
  social_tags: GitLabMeetup
  1. Once you have finished updating the information, click the Commit button on the bottom left. It should say something like 1 unstaged and 0 staged changes. This will bring up a sidebar with an Unstaged and Staged area.
  2. Check the file to ensure your updates are what you expect. If they are, click the check mark next to the filename to "stage" these changes.
  3. Once you have verified all of the edits, enter a short commit message which describes the major updates in the commit. Then select Create a new branch. Name the branch in the format of add-meetup-YYMMDD or similar. Tick the Start a new merge request checkbox. Then click Commit once more.
  4. Click on the Activity link in the header to go to your Activity page. Once there, click on the blue Create merge request button at the top of the page.
  5. Fill out the merge request details. Please ensure you tick the box to Allow commits from members who can merge to target branch as detailed on the Allow collaboration on merge requests across forks page in our docs.
  6. Mention @johncoghlan in a comment in the merge request so our team can review and merge.

What to do one week before your event

What to do the day of your event

What to do the day after your event

Simple tips to take your meetup to the next level



GitLab logos can be found in our press kit.


These communication templates can help you get a head start on your communications with your community. Templates include sample agendas, reminder and thank you emails, and boilerplate language about GitLab for your group or event descriptions.

Signs for your meetup

Use these signs to help your members find what they need and free up your own time for deeper conversations then directing your guests to the bathroom or pizza.

Feedback form

Feedback is critical. A simple three question survey can help you improve your group and gives your members a chance to offer feedback.