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
firstname.lastname@example.org if you have feedback on our vision, ideas for how we can build our community, or suggestions for a name for our evangelist program.
We use the
Meetups labels to track issues. The Evangelist Program issue board provides an overview of these issues and their status.
Evangelist Program issues typically exist in the
Evangelist Program subgroup but they can also exist in Field Marketing, Corporate Marketing, or other marketing subgroups. Issues related to our OKRs are listed in the Q4 OKR Epics: Grow Heroes Program and Grow Heroes Activity. Our upcoming Meetups are tagged with the
Meetups label and listed on the Meetups board.
We plan to replicate this process of having a epic for future OKRs and using labels and boards to track ongoing work related to our KPIs (for example: Meetups). As our OKRs and KPIs change, this page will be updated so you can see what we are working on and track our progress.
We are actively looking at ways to improve the data collection for our Evangelist Programs. If you have ideas for how we can improve, please reach out to email@example.com.
We aim to participate in at least 20 GitLab Meetups per month. A GitLab Meetup is defined as a meetup with a presentation given by a GitLab team member or a wider community member about GitLab or a tangential topic. It does not include meetups without GitLab content where GitLab only provides support.
This KPI is tracked by counting the number of issues in the GitLab.com data with the Meetups label in the Marketing group. Each event should have one associated issue with the
Meetups label. The issue due date should be set to the event date. The combination of
Meetups label and due date will be used by our data dashboard to count the number of meetups each month.
This method of tracking can results in errors when meetup issues are created in other groups or when GitLab-related presentations at meetups are not shared with the Community Relations team.
The Community Events calendar includes a list of our upcoming meetups, hackathons, office hours, and other community events. After opening the calendar, you can click on the
+ in the bottom right corner of the browser window to add
Community Events to your list of calendars in Google Calendar.
IMPORTANT: Due to the COVID-19 pandemic, GitLab is not currently supporting in-person meetups in order to encourage responsible physical distancing within our community. We encourage organizers who wish to continue to bring their communities together to use remote meeting platforms like Zoom and Google Hangouts.
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.
Meetupslabel, and be given a due date on the date of the event. Meetup issues created by a GitLab team member will have those attributes added via the template.
firstname.lastname@example.org. You can find the list of GitLab meetups on the meetup.com page.
Start from a templatein the right sidebar and choosing a template that best fits your event.
GitLab provides support to meetup organizers to drive attendance at meetup events. In order to help support our organizers, the Evangelist Program Manager takes the following steps when an event is scheduled:
Organizers are encouraged to take the following steps to drive attendance to their events:
IMPORTANT: Due to the COVID-19 pandemic, GitLab is not currently supporting in-person meetups in order to encourage responsible physical distancing within our community. In order to reinforce this policy, we are suspending reimbursement for meetup expenses for in-person events at this time. We encourage organizers who wish to continue to bring their communities together to use remote meeting platforms like Zoom and Google Hangouts.
Approve billbutton in the mail.
Classdoes not include the appropriate finance tag (for example:
Q4_FY2020_Meetups) or there are other issues with the bill, the Evangelist Program Manager should click
Send back to AP.
For GitLab Team Members using Expensify for meetup-related expenses:
Q4_FY2020_Meetups) should be selected as a
Classificationwhen creating the expense.
GitLab Meetup Starter Kits containing t-shirts, stickers, and info cards are available in Printfection.
For GitLab team members, please follow these steps to provide meetup organizers with a link to order a GitLab Meetup Starter Kit:
+ GET NEW LINK.
MARK LINK AS SENTinside the popup.
For Meetup organizers:
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:
We use Zapier to scan Meetup.com and Twitter for GitLab events that occur outside the scope of our program. Events containing "GitLab" on Meetup.com or tweets containing "GitLab Meetup" are added to the GitLab Meetups sheet and shared in Slack in the #gitlab-meetups-feed channel. We review these events each week and reach out to thank organizers and speakers who are raising awareness for GitLab. In many cases, these organizers and speakers will also be offered support with future GitLab-related events.
GitLab Heroes engages, supports, and recognizes members of the wider GitLab community who make outstanding contributions to GitLab and our community around the globe. Examples of activities that may make a member of the wider GitLab community eligible for the Heroes program include:
Heroes are eligible for rewards to help enable and encourage contributions. These rewards include:
We have three levels of Heroes: Contributor, Hero, Superhero. A community member's contributions will determine at which level they enter the program and the benefits for Heroes increase as they progress through the levels. More detail can be found in the Hero's Journey section of the Hero's page.
Community members who are interested in applying for the Heroes program should apply through the application form on the Heroes page.
The Heroes program is managed by the Evangelist Program Manager with support from the GitLab's Technical Evangelism team. The Evangelist Program Manager leads the review of applications along with the Technical Evangelism team. The Evangelist Program Manager also serves as the main point of contact with the Heroes community, manages Heroes related marketing pages and events, and is responsible for the adminstration of the program including metrics and KPI tracking.
Select Heroes may be asked to join the GitLab Technical Evangelism Community (TEC). At that point, those community members will be supported by and engage with the Technical Evangelism team.
Please email us at email@example.com if you have questions about the GitLab Heroes program.
We use GitLab to manage our Heroes application process. To apply for GitLab Heroes, community members must follow these steps:
GitLab Heroes Applicationproject using GitLab's Service Desk feature.
heroes-applicationtemplate to their Service Desk issue.
After completing the above steps, the application is ready for review. The review committee consists of the Evangelist Program Manager as the lead with the Code Contributor Program Manager supporting. The composition of the review committtee is subject to change. Any changes will be reflected here.
Generally, applicants will receive a response from GitLab within two weeks of submitting an application. Following the review process, the Evangelist Program Manager will inform folks who are selected to be GitLab Heroes of your status including the level (
Superhero) at which time you will enter the program. If you have any questions about the status of your application, please reach out to firstname.lastname@example.org for support.
We conduct semi-annual reviews of the current GitLab Heroes members to ensure they are remaining active in the community in order to maintain their GitLab Heroes status. When a current GitLab Hero is inactive, the Evangelist Program Manager will contact them to identify the reasons and work with them to resolve any blockers or issues. When a GitLab Hero no longer plans to remain active in the GitLab community, the Evangelist Program Manager will remove them from the active membership of the program.
Upon acceptance, Heroes are asked to submit a Merge Request to add themselves to the GitLab Heroes members page.
To add yourself to the Heroes page, you will need:
- Crop image to a perfect square.
- Keep maximum dimension under 400 by 400 pixels.
- Use the JPEG (
.jpg) or PNG (
- Test image in color and black-and-white.
- Name file
yournameinlowercaseand add the appropriate file extension.
Once you have the above items, follow these steps to add yourself to the Heroes page:
Web IDEnear the middle of the page.
Forkto create a Fork of the repo which will allow you to make changes and submit a Merge Request.
heroes.ymlfile open in your browser once the fork has been created. Add the following fields to the end of the file and enter your information into each of the blank fields:
- type: person name: locality: country: role: GitLab Hero twitter: bio: gitlab: picture:
heroes.yml, use the file browser on the left side of the screen to navigate to
⋁icon next to the
heroesdirectory, select upload file, and upload the photo of yourself. Be sure to follow the picture requirements listed above and confirm that the file name matches your
Commitbutton in the bottom left. It should say something like
2 unstaged and 0 staged changes. This will bring up a sidebar with an
Create a new branch. Name the branch in the format of
YOURINITIALS-heroes-pageor similar. Tick the
Start a new merge requestcheckbox. Then click
Create merge requestbutton at the top of the page.
Allow commits from members who can merge to target branchas detailed on the Allow collaboration on merge requests across forks page in our docs.
@johncoghlanin a comment in the merge request so our team can review and merge.
Upon accepting new members to the GitLab Heroes program, newly accepted members should be invited to the GitLab Heroes project by the Evangelist Program manager.
To add a new member to the project:
Settings > Membersin the left sidebar.
Invite Member, input all new members using their GitLab username or email address associated with their application.
Choose a role permissionto
Access expiration dateone year from the date of acceptance.
Communication with Heroes applicants and members of the GitLab Heroes program is conducted through email updates, generally from the Evangelist program, and via the GitLab Heroes project. Please communicate using MRs and Issues in the GitLab Heroes project whenever possible to provide transparency to the wider GitLab community and allow for easier collaboration.
When communicating with GitLab Heroes, you may wish to use the email templates created for acceptances, declines, follow-ups for clarification on contributions, and regular program updates. Access to these templates is limited to GitLab employees due to the sensitivity of some of the content in the templates (such as codes for Heroes swag).
Please follow the process detailed in the GitLab Heroes project to request support from Heroes.
GitLab team members can issue a Gold or Ultimate license to GitLab Heroes by following the steps below. These licenses are only open to GitLab Heroes at the Hero or Superhero level. Licenses should be issued for 6 months and can be extended as long as the GitLab Hero maintains their Hero or Superhero status in the program.
GitLab Heroes swag is available only for GitLab Heroes.
Gitlab Heroes swag production and fulfillment is managed by Nadel. The Nadel team can assist with swag replenishment, ask questions about fulfillment, and other swag-related inquiries.
GitLab team members who wish to provide Heroes with swag, typically done upon acceptance to the program, please follow this process:
+ GET NEW LINK.
MARK LINK AS SENTinside the popup.
The GitLab Heroes project is used for discussion via Issues, as a repo for materials that GitLab Heroes create, and a home for other resources for members of the program. Everyone in the program will have Developer access. GitLab Heroes and our community are encouraged to contribute to the project.
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). 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:
To submit a community event for support or sponsorship:
GitLab Evangelistin SFDC & be sure to "check the box" to send a notification.
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
Student hackathons are the events most frequently submitting requests for support from GitLab. Hackathon organizers who wish to leverage GitLab's DevOps platform for their events are encouraged to use free trials for their events. This can de done by directing hackathon participants to apply for a free trial of GitLab for use during the hackathon which will allow them to use all of GitLab's features. In some cases, if your event meets the criteria above at a score of 9 or higher, we may also send stickers for participants or swags as prizes. Given the volume of requests we receive, providing financial support for these events is not feasible.
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.). There are a few ways you can get in touch with speakers from the GitLab team and the wider community to participate and do a talk at your event:
For GitLab team members, you can 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 sending an e-mail to
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 GitLab team members who want to become a tech speaker, contact
email@example.com 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.
GitLab team members and members of the wider GitLab community are encouraged to nominate community members to participate in our programs. This is a valuable way to contribute to the growth and sucess of the GitLab community.
To nominate a community member who may be interested in becoming a code contribtuor or meetup organizer, who actively shares their knowledge of GitLab in talks or blog posts, or who meets the criteria for the GitLab Heroes program, please contact the Community Relations team by emailing firstname.lastname@example.org.
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.
The Evangelist Program Manager must collect a signed
Media Consent and Release Form before their content is published by GitLab. GitLab team members can request a copy of the form to send to members of the wider GitLab community via the #legal channel in Slack.
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.