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

Evangelist Program

On this page


At GitLab our mission is to change all creative work from read-only to read-write so that everyone can contribute. In order to fulfill this mission, we need to create both the tools and platform to enable this change and a community of contributors who share our mission. We are just getting started in building the GitLab community and we encourage everyone to contribute to its growth.

There are many ways to participate in the GitLab community today: contributing to an open source project, contributing to our documentation, hosting your open source project on GitLab, or teaching your colleagues and collaborators about the value of Concurrent DevOps.

We are building an evangelist program to support people who share our mission and want to give tech talks, run local meetups, or create videos or blogs. We will be announcing more in Q1. For now, please email if you have feedback on our vision, ideas for how we can build our community, or suggestions for a name for our evangelist program.

How to see what we're working on

We use the Evangelist Program label to track issues. The Evangelist Program issue board provides an overview of these issues and their status.

For meetups, the Meetups label is used to track meetup issues within the marketing group. These issues typically exist in the Evangelist Program subgroup but they can also exist in Field Marketing, Corporate Marketing, or other marketing subgroups. They are listed in the Q1 OKR Epic and on the Meetups board.

We plan to replicate this process of having a label, epic, and issue board for future OKRs and will update this page so you can see what we are working on and track our progress.

Upcoming events

The Community Events calendar includes a list of our upcoming meetups, hackathons, office hours, and other community events.


GitLab supports team members and members of the wider GitLab community who want to organize or speak at meetups. Our goal in supporting these events to better engage with and increase connections among the GitLab community, increase awareness of GitLab, and better educate the technology community.

Organize a meetup

Speak at a meetup

Meetups help us raise awarness of GitLab and build communities in new places. We love to track them to know where the community is growing. If you are speaking at a meetup as a representative of GitLab or you are giving a talk about GitLab, please let us know! Here's how and why we do this:

Community events

We'd love to support you if you are organizing or speaking at a community-driven event, be it GitLab-centric or around a topic where GitLab content is relevant (e.g. DevOps meetup, hackathon, etc.). Depending on the number and type of attendees at an event, it may be owned by Corporate Marketing, Field Marketing, or Community Relations. Our events decision tree is a guide to help you find the right team to handle an event request.

Events Decision Tree: event decision tree

Submit an event request to our team

To submit a community event for support or sponsorship:

  1. Review our events decision tree to ensure you are directing your event inquiry to the appropriate team.
  2. Submit an issue using the sponsorship-request template.
  3. For Service Desk or other auto-generated issues that contain sponsorship requests, we will retroactively apply the 'sponsorship-request' to the issue. The process for updating an issue with no template to the 'sponsorship-request' template is: copy text from original issue, assign 'sponsorship-request' template to issue, paste text from original issue into the appropriate field at bottom of template, update remaining fields.
  4. GitLab XDRs: for contact requests received in Salesforce via the Sales webform requesting event sponsorship, please change ownership to GitLab Evangelist in SFDC & be sure to "check the box" to send a notification.
  5. GitLab's Evangelist Program Manager will review the request and follow up with the event contact.

How we assess requests

We ask the following questions when assessing an event:

Each question is graded on a scale of 0-2. We then tally the scores and assign the event to a sponsorship tier.

We ask these questions and use this scorecard to ensure that we're prioritizing GitLab's and our community's best interests when we sponsor events.

If you have questions, you can always reach us by sending an e-mail to

Find a tech speaker

We'd love to support you if you are organizing an event, be it GitLab-centric or around a topic where GitLab content is relevant (e.g. DevOps meetup, hackathon, etc.).

You can get in touch with speakers from the GitLab team and the wider community to participate and do a talk at your event. We maintain a list of active speakers on our Find a GitLab speaker page. Once you find a speaker in your region, contact them directly. For GitLabbers, you can also check the #cfp channel on Slack where many of our active tech speakers will see your speaker request. Most speakers will also be able to do talks remotely if the event is virtual or if travel is a challenge.

If you have questions, you can always reach us by sendind an e-mail to

Become a tech speaker

If you are aware of people from the GitLab community who are interested in giving a tech talk relating to GitLab, please direct them to our Become a Speaker page for more information on the type of support we provide.

For GitLabbers who want to become a tech speaker, contact and check out the #cfp channel on Slack to discover upcoming opportunities. Additional detail on the logistics of giving a talk once your proposal has been accepted can be found on the Corporate Marketing page.

Resources for speakers

Contribute content

GitLab actively supports content contributors. Our community team tracks GitLab content and our evangelist program manager and editorial team regularly reviews the content. If you would like to submit your content for review, please create an issue on our evangelist program project.

We make an effort to amplify and support content contributions that generate value for our community. Criteria we consider include: how well a post addresses an issue in the Community Writers issue tracker, how well a post aligns with our strategy and values, and how well a post is written.

As we identify posts that meet our criteria, we decide how we want to support the posts. We may also identify creators who we want to partner with on content. Writers who are looking for inspiration may want to visit our Community Writers issue tracker which tracks blog post ideas submitted by our community.

You can track the status of community content submissions on the Community Content board. Submissions go through the following steps:

  1. Review: review submissions for accuracy.
  2. Say thanks: contact the creators to say thank you, share a swag code, and highlight other ways they can contribute. $25/creator is the standard amount.
  3. Share: Post on social (with a credit to the author) or retweet.
  4. Syndicate: for posts that we love or that answer a common or important question, we may ask the author if we can add the post to our Medium publication or the GitLab blog.
  5. Curate: creators who have shown a depth of experience around topics important to GitLab and the wider GitLab community may be asked to submit talks or posts about said topics.


Coming soon. Contact if you have any questions.


Coming soon. Contact if you have any questions.

Evangelist Program Office Hours

Our Evangelist Program Manager hosts office hours via Zoom every Friday at 10:30am ET excluding holidays. They want to answer your meetup, events, and public speaking questions and hear your feedback on our programs! You can see the meeting information and join the call via the Community Events calendar.

Helpful Resources