GitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsGitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsThis page outlines details for in-person events. For virtual event information, please visit the Virtual Events Page.
There are 3 groups within marketing who handle external events. Each group has a specific purpose. Please review each page for specific details.
Marketing Programs supports Corporate and Field Marketing in relation to all events with communication timeline, technical tracking, reporting, email deployment, landing page creation, and more as required by the event.
GitLab’s top priority is the health and safety of our attendees and team members. GitLab reserves the right to switch any hosted in-person event to a virtual event. If this is done, we will communicate to all attendees via email.
Travel guidance on COVID-19 can be found here.
To determine who would handle the event, please refer to our events decision tree. If it is not clear who should own an event based on the decision tree, please email events@gitlab.com
.
Please only request event support/sponsorship if your proposed event fits the following criteria:
If your event fits the criteria above and you would like support from marketing, create an issue in the appropriate marketing project.
For Corporate Event DRIs:
If you are the DRI for the event see below for "event execution" for next steps once you have opened and completed issue template. We are using Epics as the SSOT for the event over Meta Issues.Please Note:
These requests will be reviewed by the appropriate regional Field Marketing Manager. Even if the event is free or low-cost, all requests must be approved by Field Marketing prior to any commitment to ensure the event or tactic aligns to the marketing strategy, meets MQL objectives and Field Marketing can properly execute to maximize GitLab’s future success.
Event_Tactic_Request
issue and follow the instructions.Be sure you review the issue template and provide all necessary information that is asked of you in the issue. We especially need goals/ reason to attend.
Campaign Tag
NOTE: Event owners are DRI to create/setup campaign names & tags!
campaign tag
(using proper ISOdate_Name
format & within 31 character limit) into the associated budget line item. When Field Marketing Event Owner (DRI) begins campaign process, they will utilize the campaign tag
that is auto-created in the Field Marketing budget document (this campaign tag is created in the campaign's line item by formula).
Campaign Tag
ISO date = first day of event (if multiday) - Example: AWS reInvent Dec 2-5, 2019, Campaign Tag
= 20191202_AWS_re:Invent
this will also be applied to the SFDC Campaign name & Marketo Program namecampaign tag
form the budget document into the Corporate request issue or Field Marketing issue.campaign tag
as the SFDC Campaign and Marketo Program name so it is the unique identifier across all systems.If the overarching event includes a speaking session, workshop, dinner, and/or happy hour (anything that requires a separate SFDC campaign and list upload), please follow the steps below and abide by the SLA guide to give necessary time for work to be complete.
⏰ SLAs for YES/NO section to be filled out for an ancillary event before moving to WIP:
The purpose of creating a new issue for each ancillary event is to better facilitate the needs for each event, to clearly indicate the timelines, and to clarify the DRIs which may be different for the different events. For example, if there is a speaking session hosted by a GitLabber at a larger conference, and the speaker is planning to write the email copy after the event, the timeline and DRI would be different from the timeline and DRI for the general booth follow email.
Steps for Ancillary Events:
status:wip
.
Related issue
to the original issue for reference.status:plan
to status:wip
.
NOTE: The Epic is the main hub for all event information. All issues associated with the Event must be linked to the Epic!
## Event Details
* `Place details from the event issue here`
* Event DRI:
* Marketo program type:
* Campaign utm `enter utm here` (Format: Campaign Tag, must be all lowercase, with no spaces, underscores, or special characters)
* Event Budget:
* Event Goals:
* [Add the planning sheet]()
* Link to event landing page:
* Related GTM motions (sleect allt hat apply)
* [ ] CI
* [ ] DevOps
* [ ] GitOps
## Program Tracking Details
* Campaign Type: `enter utm here- usually Owned Event'
* SFDC Campaign: To be added by Verticurl
* MKTO Program: To be added by Verticurl
* UTM Campaign: `enter utm here`
* Finance Tag: `enter utm here`
## [Copy for landing page and emails >>]() - [template](<a href="https://docs.google.com/document/d/1j43mf7Lsq2AXoNwiygGAr_laiFzmokNCfMHi7KNLjuA/edit">https://docs.google.com/document/d/1j43mf7Lsq2AXoNwiygGAr_laiFzmokNCfMHi7KNLjuA/edit</a>)
* Alliances/Partner Marketing involved - (if yes, must designate a DRI)
* Will this event include use of Marketing Development Funds (MDFs)? YES/NO
* [Requesting MDF Funds](<a href="https://about.gitlab.com/handbook/marketing/strategic-marketing/analyst-relations/channel-marketing/#requesting-mdf-funds"</a>)
## Issues to be created
* [ ] [Facilitate tracking issue created](<a href="https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-01-facilitate-tracking">https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-01-facilitate-tracking</a>) - Event owner creates, issue goes through triage
* [ ] [List clean and upload issue created](<a href="https://gitlab.com/gitlab-com/marketing/marketing-operations/issues/new?issuable_template=event-clean-upload-list">https://gitlab.com/gitlab-com/marketing/marketing-operations/issues/new?issuable_template=event-clean-upload-list</a>) - MOps creates, assigned to event owner and MOps
* [ ] [Follow up email issue created](<a href="https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-04-follow-up-email">https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-04-follow-up-email</a>) - Event owner creates, issue goes through triage
* [ ] [Add to nurture issue created](<a href="https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-05-add-to-nurture">https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-05-add-to-nurture</a>) -(Optional) Event owner creates, issue goes through triage
* [ ] [Marketo landing page copy issue created](<a href="https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=marketo-landing-page-copy">https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=marketo-landing-page-copy</a>) - Event owner creates, assign to Corp/FMM and FMC
* [ ] [Marketo landing page creation issue created](<a href="https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=marketo-landing-page-creation">https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=marketo-landing-page-creation</a>) - Event owner creates, issue goes through triage
* [ ] [Invitation and reminder issue created](<a href="https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-03-invitations-reminder">https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-03-invitations-reminder</a>) - (Optional) Event owner creates, issue goes through triage
* [ ] [Target segment issue created](<a href="https://gitlab.com/gitlab-com/marketing/marketing-operations/issues/new?issuable_template=dma_request">https://gitlab.com/gitlab-com/marketing/marketing-operations/issues/new?issuable_template=dma_request</a>) - (Optional) MOps creates, assigned to event owner and MOps
* [ ] [Onsite registration form & landing page](<a href="https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-08-onsite-reg-form-lp">https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-08-onsite-reg-form-lp</a>) - (Optional) Event owner creates, issue goes through triage
cc @jburton to create list upload issue and DMA request as required
[Issue naming convention] - [Event Name]
⚠️ Note: MOps is required to create their list clean and upload issue, and DMA list issue in their project with the proper template and associate back to the epic.
☝️ Tip: DRIs use this document to auto-populate timelines / SLAs for events. They will add the event as a new row when it is created with a status of Plan, add the start and end date, and look at the resulting due dates for each action item.
Speaker Request
issue template.Speaker Request
to your regional Customer Reference lead. The Customer Reference lead will work with the Event Managers and the Sales team in identifying and engaging with customers to speak at events.events.yml
- Detailed instructionsevents.yml
OR a Marketo landing page. (Detailed instructions) Marketo will be used if ALL of the following criteria are met:Social Request
template for general social awareness posts and any social ads that need to be created.events@gitlab.com
.Corporate Marketing
project for booth design. Assign to Design team and provide booth spec and due date. Provide as much notice as possible.Corporate Marketing
project.If the overarching event includes a speaking session, workshop, dinner, and/or happy hour (anything that requires a separate SFDC campaign and list upload), please follow the steps below and abide by the SLA guide to give necessary time for work to be complete.
⏰ SLAs for YES/NO section to be filled out for an ancillary event before moving to WIP:
The purpose of creating a new issue for each ancillary event is to better facilitate the needs for each event, to clearly indicate the timelines, and to clarify the DRIs which may be different for the different events. For example, if there is a speaking session hosted by a GitLabber at a larger conference, and the speaker is planning to write the email copy after the event, the timeline and DRI would be different from the timeline and DRI for the general booth follow email.
Steps for Ancillary Events:
status:wip
.
Below is the tactical process DRIs take to organize actions and timelines for field and corporate events. This process was created by MPM's to keep projects organized and on track. Please comment in the #marketing_programs slack if you have any questions.
⚠️ *If the FMM does not list the elements needed of the MPM in the issue, the MPM will not be able to move forward. Having this information up-front will minimize back-and-forth with MPM and let them take action appropriately and efficiently.
## [Main Issue >>]()
## [Copy for landing page and emails >>]() - [template](https://docs.google.com/document/d/1j43mf7Lsq2AXoNwiygGAr_laiFzmokNCfMHi7KNLjuA/edit)
## Event Details
* `place details from the event issue here`
* [ ] [main salesforce campaign]()
* [ ] [main marketo program]()
* [ ] campaign utm `enter utm here` (Format: Campaign Tag, must be all lowercase, with no spaces, underscores, or special characters)
## Issue creation
* [ ] [List clean and upload issue created](https://gitlab.com/gitlab-com/marketing/marketing-operations/issues/new?issuable_template=event-clean-upload-list) - MOps creates, assigned to event owner and MOps
* [ ] [Follow up email issue created](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-04-follow-up-email) - MPM creates, assigned to event owner and MPM
* [ ] [Add to nurture issue created](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-05-add-to-nurture) -(Optional) MPM creates, assigned to event owner and MPM
* [ ] [Landing page issue created](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-02-landing-page) - (Optional) MPM creates, assigned to event owner and MPM
* [ ] [Invitation and reminder issue created](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-03-invitations-reminder) - (Optional) MPM creates, assigned to event owner and MPM
* [ ] [Target segment issue created](https://gitlab.com/gitlab-com/marketing/marketing-operations/issues/new?issuable_template=dma_request) - (Optional) MOps creates, assigned to event owner and MOps
* [ ] [Onsite registration form & landing page](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=MPM-08-onsite-reg-form-lp) - (Optional) MPM creates, assigned to event owner and MPM
cc @jburton to create list upload issue and DMA request as required
[Issue naming convention] - [Event Name]
⚠️ Note: MOps is required to create their list clean and upload issue, and DMA list issue in their project with the proper template and associate back to the epic.
☝️ Tip: MPMs use this document to auto-populate timelines / SLAs for events. They will add the event as a new row when it is created with a status of Plan, add the start and end date, and look at the resulting due dates for each action item.
In this timeline, BD = Business Days, and incorporates US public holidays and T = start date of the event.
In this timeline, BD = Business Days, and incorporates US public holidays and T = start date of the event.
Sometimes, it becomes necessary to change the date of an offline event. Once the FMM has identified that the date will change, the FMM will:
If the change in the date is related to COVID-19, the FMM will:
If the date changes after the MPM set up the issues, epic, and tracking for the event, the MPM must make the following updates:
FMM and MPM determine format of this virtual event from documented options. FMM lets interested teams know that the event has switched to digital, the existing landing page is no longer accepting registrations and sales-nominated flow has been stopped (if applicable).
YYYYMMDD_HostName_Topic (External Webcast Template)
template and save to the GitLab Webcasts
folder. If you are using the same campaign tag as the original live event, add "OLD" to the beginning of the existing live event Marketo program as Marketo will not allow two programs with the same name.GitLab Webcasts
folder for the virtual event.Virtual Events
cloning YYYYMMDD_WebcastTopic_Region (Single time slot)
or YYYYMMDD_WebcastTopic_Region (Multiple Time Slot)
template and save to the GitLab Webcasts
folder. If you are using the same campaign tag as the original live event, add "OLD" to the beginning of the existing live event Marketo program as Marketo will not allow two programs with the same name.GitLab Webcasts
folder for the virtual event.OLD
at the beginning of the title.Registration
and Interesting Moments
smart campaigns.We’ve gone virtual! Please register the virtual event page [link to new page] to register for this event.
Reminder Email
smart campaign from the original event program to send a note to those that have already registered with directions about how to re-register for the virtual event.aborted
These will be Virtual Sponsorships with booths (not just a sponsored webcast).
This event has changed from live to virtual. Original date [2020-xx-xx], New Date: [2020-xx-xx], This [epic/issue] reflects information for the virtual event.
Date can be left off if it is the same.Virtual Events
cloning YYYYMMDD_Vendor_VirtualConfName (Virtual Conference Template)
template and save to the Virtual Sponsorships
folder. If you are using the same campaign tag as the live event, add "OLD" to the beginning of the existing Marketo program as Marketo will not allow two programs with the same name.Virtual Sponsorships
folder for the virtual event.OLD
at the beginning of the title. If the original Marketo program wasn’t being used yet (no invites, no members, only linked to SFDC) it can also be deleted or moved to an archived folder.Interesting Moments
smart campaign.aborted
Once the DRI has identified that an event is cancelled, the FMM will:
Sponsorships and Events
calendarThe FMC will:
If an offline event is cancelled after the MPM set up the issues, epic, and tracking for the event, the MPM will:
Aborted
. No other changes.Aborted
. No other changes.For a full breakdown of our various types of events, please review this list.
The above planning list is not exhaustive - see planning issue template in field marketing project for most up to date list of tasks.
Some events require technical staffing (Solutions Architects and/or others from the Customer Success team). To request technical staffing, do the following:
technical-staff::required
to the meta issue - this will make it appear on the Event Technical Staffing boardtechnical-staff-type
labels to the issue to indicate which group(s) might be able to send staff. For example, if the event is on the west coast of the USA, consider adding technical-staff-uswest
and technical-staff-commercial
It is important that we are communicating with our customers and prospects that we are monitoring COVID-19. Please include the following in all email outreach for hosted events.
It is important that we are communicating with our customers and prospects when are attending an event. This is done through a targeted email sent through Marketo & also through SDR & SAL outreach.
We use several email aliases for pre and post event outreach. Below are guidlines as to which one should be used based on the event
info@
info@
fieldmarketing@
As propects register for the event the Field Marketing team has the ability to track any potential dietary concerns:
If the FM DRI for an event needs to reach out to someone prior to the event, they will do so leveraging their personal @gitlab.com
email address & cc fieldmarketing@
alias.
The Dietary Restrictions
field can be leveraged as a list filter by the MPMs if they are needing to send a bulk email of any kind.
Campaign Status
:
Sales Invited
= You have personally invited the person to the event.Sales Nominated
= Marketing will invite the person on your behalf. They will receive invitation email pre-event plus any confirmations/reminders if they register. Video training on how add is also available.Marketing Invited
= Marketing will be sending geo-targted invitation emails to specific events pulling the names from our active database. Anyone included in this master send will be added to the campaign with this status.Email Address
to existing records regardless if LEAD or CONTACT object.#sdr_global
slack channel with a link to SFDC campaign, link to SDFC LEAD & CONTACT view, and link to Outreach view (if exists).
sdr
slack alias and cc the @sdr-leadership
slack alias.Common lead questions:
Contact Status
on the record as follow up is done.For FIELD events that don't have badge scanners onsite, the FMM event owner can request an onsite registration form and landing page which can be used to collect names at the booth. The landing page (including the form) can be accessed by a unique URL via iPad, mobile phone or laptop and should only be used by staff at the booth and deactivated post-event by Marketing Ops.
How to create an onsite registration form
No Lead Scanner - Onsite Reg
landing page under assets. Update the URL to be relevant to the event.03 No Lead Scanner - Onsite Event Reg
Campaign and check that Smartlist and Flow are set up correctly for the relevant landing page. MPM then to ACTIVATE this campaign.How to use the onsite registration form
Follow Up Requested
> lead status = MQL
Visited Booth
> lead status = Inquiry
For OWNED events, the Marketo program is pushed to the Marketo Check-in app that allows the FMM team to be self-sufficient when it comes to updating an event registration list.
User Experience Flow (Registration & Check-In) With System Actions
Registered
Registered
to Attended
Registered
status to be No Show
12 hours after the event⚠️ Important! FMM must check-in all individuals and sync to Marketo within 12 hours of the start time of the event so that automation can flip the correct records to No Show
.
View: Summary
to View: Schedule
created date
, not the event datedate
,end
, and event times (remember all times are based on the MPM's timezone setting in Marketo)tentative
to confirmed
. Slide bar will change from gray to orange when done correctly.
The event will not be visible in the Marketo Check-in app until 7 days prior to the eventIf FMM is unsure they will have internet at venue, it is very important to fully sync program while connected to the internet before event.
Status
= Registered
will show in the list on the left side of the app.
Last Name
through the list.
Phone
Campaign Member Status
= Attended
and the sync to SFDC will beginRegisterd
-> No Show
statusIf you need support, use the #mktgops slack channel.
Swag selection and creation is managed by Corporate Marketing. All information on swag can be found in the Corporate Marketing handbook. For event related swag and tracking purposes, we utilize the tags swag_corporate
and swag_community
.
GitLab's Community Relations team reviews and manages our community events (typically an event with less than 250 attendees that is targetting end users of GitLab) including Meetups. The Community Relations handbook has additional information on the events the Community Relations team will support.
For Field Marketing campaign tag details, please visit the Field Marketing page here.
For all details regarding Field Marketing Swag and Event Assets, please visit the Field Marketing page here.
A QR code with a general GitLab PathFactory track and a QR code with a general PubSec PathFactory track are available for use. FMMs/DRIs can follow the links below to print and display at events. Table-top signs to display the QR codes are available in Nadel - search for Tabletop Display
.
Field Marketing is able to create additional QR code signs using a template by following instructions here. Please be sure to make a copy of the file rather than editing directly.
If this template does not meet your needs, additional designs may be requested by opening an issue in the corporate marketing repo. Be sure to include:
@mnguyen4
& @shanerice
if your MPM is not availableDesign will then create and provide a PDF for the FMM/FMC to print on their own for the event.
Items to Purchase:
Marketo Check-in App on iPad:
Creating Event Badges:
SFDC
Name Tag Export
in the Field Marketing
folder, or go to this link.Select Campaign
by clicking the lookup next to the fieldRun Report
Export Details
Export File Format
field, select either Excel Format
or Comma Delimited
(whichever works best on your laptop)Avery Template
Templates
select Avery Design & Print
Start Designing
Quick Search
, type in the badge number found on the box of your previously purchased Avery badges (link provided in Items to Purchase
above) - Avery 74541Select this Template
Apply from a Saved Project
Select and Customize
on the horizontal orientation optionGitLab Connect
template option with our standard Tanuki logo and click Apply this Design
Import Data Mail Merge
Replace Spreadsheet
and Browse for File
Next
and then drag and arrange fields to your preference and click Finish
Navigator
section will allow you to format and make changes to all badges or individual badgesPreview and Print
and Print it Yourself
Get PDF to Print
Open PDF
and print utilizing the Avery badge paper previously purchasedFor venue search requests, the FMM can open an issue utilizing the Venue_Search
template. Follow the instructions to provide event details and assign to the regional FMC.
At GitLab owned events we will sometimes host 10 minute lightning meetings with the GitLab CXO(s) in attendance. We do this to facilitate many interactions with our leadership in a short amount of time.
In an effort to publicly share where people can find GitLab at events in person throughout the world, we have created about.gitlab.com/events. This page is to be updated by the person responsible for the event. To update the page, you will need to contribute to the event master.yml. If you need more information about our exact involment in an specific event please visit the marketing project in gitlab.com and search the name of the event for any realted issues. The "Meta" issue should include the most thorough and high level details about each event we are participating in. Place your event in the order in which it is happening. The list runs from soonest to furthest in the future. Save event images and headers here: Save images for featured events here
Diversity
, Conference
,
MeetUp
, Speaking Engagement
, Webinar
, Community Event
or GitLab Connect
. Events cannot have more than one type. If more than one apply, choose the best. If you feel your event doesn’t fit in the below category, do not just manually add a type. Please reach out to events@gitlab.com to suggest a new type of event.Date starts
and Date ends
section)AMER
, LATAM
, EMEA
, APAC
, or Online
- topic: The Best DevOps Conference Ever
type: Conference
date_starts: January 1, 2050 # Month DD, YYYY
date_ends: January 3, 2050 # Month DD, YYYY
description: |
The Best DevOps Conference Ever brings together the best minds in the DevOps land. The conference consists of 3 full days of DevOps magic, literally magic. Attendees will have the opportunity to partake in fire talks and moderated sessions. This is one you won’t want to miss.
location: Neverland, NVR
region: APAC
social_tags: DEVOPS4LIFE
event_url: https://2050.bestdevops.org
- topic:
type:
date_starts:
date_ends:
description:
location:
region:
social_tags:
event_url:
For featured events include:
featured:
background: background/image/src/here.png
All landing pages require the involvement of a Marketing Program Manager (MPM) as there are required steps to set up programs & tracking in both Marketo/Salesforce to correctly manage inbound submissions from the landing page.
For corporate tradeshows we will want to create an event specific page that links from the about.gitlab.com/events page. The purpose of this page is to let people know additional details about GitLab’s presence at the event, how to get in touch with us at the event, and conference sessions we are speaking in (if applicable).
For select Field Marketing events, that meet the critera below, a Marketo landing page is used instead of an events.yml
created landing page. By doing this, the MPMs own the creation of these pages and they are the only ones who will have edit access to these pages.
When to specifically use a Marketo landing page vs. the events yml:
Steps to take to create the new events.yml
generated landing page:
Data
, then to events.yml
contact:
to distinguish a header title.form:
- topic: AWS re:Invent
type: Conference
date_starts: December 2, 2019
date_ends: December 6, 2019
description: |
AWS re:Invent 2019 is the Amazon Web Services annual user conference dedicated to cloud strategies, IT architecture and infrastructure, operations, security and developer productivity.
location: Las Vegas, NV, USA
region: AMER
social_tags: AWSreInvent2019
event_url: https://about.gitlab.com/events/aws-public-sector-summit/
# Giving the following data will give this event it's own dedicated page on about.gitlab.com, must provide a unique url.
# If it is text, it needs to be wrapped in "double quotes". This is so you can use characters like : and ' without breaking anything.
url: aws-reinvent
header_background: /images/blogimages/gitlab-at-vue-conf/cover_image.jpg
header_image: /images/events/aws-reinvent.svg
header_description: "Drop by our booth to see a demo and speak with our GitLab experts!"
booth: "S1607"
form:
title: "Request a meeting!"
description: "Let us show you how GitLab can impact your business."
number: 1691
success message: "Thank you for requesting to meet! We'll be in touch shortly with more information."
content:
- title: "Make sure to stop by the GitLab booth at AWS re:Invent!"
body: "Speak with our experts and learn how GitLab simplifies your deployment pipeline to accelerate delivery by 200%. See a live demo, learn about our latest releases, and explore what’s on the roadmap for GitLab."
- title: "Request a meeting"
body: "Fill out the form to request a meeting with GitLab. We'll share how we can impact your business as a complete DevOps platform, delivered as a single application. From project planning and source code management to CI/CD, monitoring, and security."
- title: "Activities at AWS re:Invent"
list_links:
- text: "Register for our happy hour!"
link: "#"
- text: "Join our speaking sessions - see details below."
speakers:
- name: "Priyanka Sharma"
title: "Director of Technical Evangelism"
image: /images/team/priyankasharma-crop.jpg
date: "Wednesday, May 22"
time: "14:00 - 14:35"
location: "Hall 8.0 F5"
topic: "[The Serverless Landscape and Event Driven Futures](https://kccnceu19.sched.com/event/MPeI/the-serverless-landscape-and-event-driven-futures-dee-kumar-cncf-priyanka-sharma-gitlab?iframe=no&w=100%&sidebar=yes&bg=no)"
description: "Serverless design patterns have grown in popularity amongst developers and enterprises alike and the ecosystem is exploding. Developers like moving faster by focusing on business logic without worrying about the underlying infrastructure. Today, there are umpteen solutions and OSS projects in the market and the space needs some organization to maximize effort. There is a lot of curiosity and confusion around serverless computing. What is it? Who is it for? Is it a replacement for IaaS, PaaS, and containers? Does that mean the days of servers are over? The CNCF created the Serverless Working Group to explore the intersection of cloud native and serverless technology. The first output of the group was creation of serverless landscape. The landscape lists some of the more common/popular Serverless projects, platforms, tooling, and services."
- name: "John Jeremiah"
title: "Director, Product Marketing"
image: /images/team/johnjeremiah-crop.jpg
date: "June 12, Wednesday"
time: "1:25 PM–1:45 PM"
location: "Partner Pavilion"
topic: "Accelerating Speed to Mission: A Digital Transformation"
description: "Velocity and speed of execution determine the winners. The faster your software teams can deliver, the bigger your advantage. The traditional software development processes have multiple layers of friction, checkpoints, and bottlenecks, often making simple projects complex, expensive, and lengthy. One of the hardest parts of delivering software is keeping everyone aligned and focused. Teams waste time waiting for inputs, fixing mistakes, shifting from one tool to another, waiting for infrastructure, and maintaining complexly integrated toolchains; this all creates friction and slows innovation. It doesn't have to be slow, learn how to accelerate your software delivery and increase your mission velocity."
- topic:
type:
date_starts:
date_ends:
description: |
location:
region:
social_tags:
event_url:
# Giving the following data will give this event it's own dedicated page on about.gitlab.com, must provide a unique url.
# If it is text, it needs to be wrapped in "double quotes". This is so you can use characters like : and ' without breaking anything.
url:
header_background:
header_image:
header_description:
booth:
form:
title:
description:
number:
success message:
content:
- title:
body:
- title:
list_links:
- text:
link:
- text:
link:
- text:
link:
speakers:
- name:
title:
image:
date:
time:
location:
topic:
description:
- name:
title:
image:
date:
time:
location:
Please see Emails & Nurture handbook page for in-depth details on email marketing
Email Approval:
If you’re looking for information about speaking at an events head over to our Corporate Marketing page for complete details.