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.
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 email@example.com if you have feedback on our vision, ideas for how we can build our community, or suggestions for a name for our evangelist program.
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.
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
We love and support meetups. If you participate in local tech groups and are interested in having a GitLab speaker or GitLab as a sponsor, please submit an issue. Please note, providing sufficient lead time (at least a month) allows us to better support your event so feel free to reach out as soon as possible.
If you are interested in creating your own GitLab meetup or if you already have an existing meetup on meetup.com that you would like to link to GitLab's meetup.com Pro account, please email firstname.lastname@example.org. You can find the list of GitLab meetups on the meetup.com page.
When you are getting started, we recommend scheduling at least 2 meetups. Publish your first meeting with a date and topic, and then a second meeting with a date and topic. The second meeting can have a flexible topic based on how the first meeting goes. The point of setting two meet-ups is to help build momentum in the new group.
Often, we try to have GitLab employees attend the first couple of meetups. Once the group has hosted a couple of successful events, it becomes easier for the group to sustain itself. It is much harder to start new meetups versus maintaining existing ones. So we make an effort to support and keep new meetups going.
Reach out to other like-topic meetups and invite them to your meetup to help grow your community.
If you purchase any food & beverage for the meetup event, we can help reimburse the expense. A general guideline is $US 5/person for a maximum of $US 500 per each meetup. You will be asked to provide receipts, attendees list/photo, etc. If you have questions or need help with food & beverage reimbursements, please email email@example.com.
We recommend all Meetup organizers record their events, when possible. Options include:
Using Quicktime to simultaneously conduct screen recording and audio recording. The two recordings can be synced into a single video file.
To record the speaker, we recommend using a webcam with a microphone (such as the Logitech C922x). You can insert the slides as images into the video recording later using iMovie or your preferred video editing software.
We use Zapier to scan Meetup and Twitter for GitLab meetups and populate the corresponding worksheets in the GitLab Meetups sheet. This helps us connect with and thank organizers and speakers who are raising awareness for GitLab.
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:
Opening an issue helps us support you. A few ways we can help:
Marketing: We'll share the event on our blog, via social, and with GitLab community members in the area to raise awareness of the event.
Sponsorship: GitLab will cover the cost of food and beverages for meetup organizers.
Swag: Our swag is pretty popular so we'll send you plenty of stickers and maybe some other fun stuff to give away.
Speaker prep: If you need help with your deck or would like someone to offer feedback on a dry run of your talk, the Evangelist Program Manager is happy to help.
We track meetups via issues on the Meetups issue board. Take a look and see what we have coming up!
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:
Submit an event request to our team
To submit a community event for support or sponsorship:
Review our events decision tree to ensure you are directing your event inquiry to the appropriate team.
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.
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.
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:
Will there be a GitLab speaker? We do not require a speaker slot in return for sponsorship but we do prioritize events where the audience will be hearing about GitLab - either from a GitLab team member or a member of the wider GitLab community.
What type of people will be attending the event? We prioritize events attended by diverse groups of developers with an interest in DevSecOps, Cloud Native, Kubernetes, Serverless, Multi-cloud, CI/CD, Open Source, and other related topics.
Will we be able to interact with attendees? We prioritize events that provide opportunities for meetings, workshops, booth or stands to help people find us, and other interaction with attendees.
Where will the event be held? We aim to have a presence at events around the globe with a particular focus on areas with large GitLab communities and large populations of developers.
Is the event important for industry and/or open source visibility? We prioritize events that influence trends and attract leaders within the developer and open source communities. We also prioritize events organized by our strategic partners.
What is the size of the opportunity for the event? We prioritize events based on audience size, the number of interactions we have with attendees, and potential for future contributions to GitLab from attendees.
Each question is graded on a scale of 0-2. We then tally the scores and assign the event to a sponsorship tier.
Events scoring below 5 are not eligible for sponsorship.
Events scoring 6-8 are eligible for GitLab swag for attendees and other in-kind sponsorship.
Events scoring 9 or above are eligible for financial support.
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 firstname.lastname@example.org.
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 email@example.com.
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 firstname.lastname@example.org 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.
Additional GitLab-created presentations can be found within the folders contained in Decks and Product Marketing on the Marketing Drive.
You can find available speaking opportunities by checking the #cfp channel on Slack and the issue list for the Speaker Needed label.
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:
Review: review submissions for accuracy.
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.
Share: Post on social (with a credit to the author) or retweet.
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.
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 email@example.com if you have any questions.
Coming soon. Contact firstname.lastname@example.org 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.