|#corporate-events-team||General planning questions and open to all team members to inquire about upcoming or past events|
|#commit-standup||Communication hotline between Events, PMM, MPM, TE, Social/ PR, Community, and any other process/ planning/ logistics-specific conversations.|
|#gitlabcommit||General Commit related questions|
General Questions: events at gitlab dot com
Contribute-related Questions: contribute at gitlab dot com
Commit-related Questions: commit at gitlab dot com
Commit Sponsorship Questions: sponsorcommit at gitlab dot com
All GitLab events must check at least three or more of the goals of our events below to be considered.
**If you are looking to request a new Corporate Event, please use the following issue template
Suggested events will be subject to a valuation calculation - will it meet or exceed objectives listed above?
* Event Marketing — Project management, execute logistics, budget management, event staffing/training, lead collection/reporting, and ancillary events * Field Marketing — Field communication, meeting program support, onsite booth support, ancillary event support * Inside Sales Rep — Drive registration, booth support, lead follow-up * Customer Success (TAM, SAs attending) / Community Relations — Booth support, attend customer meetings, presentations/speaking engagements * Product/Alliance Marketing — Messaging, content creation (blogs, sponsorship deliverables, post event emails etc), onsite booth support * Technical Marketing — Demos creation, onsite support * Social and Communications — Pre-event, on-site, post-event social content creation, PR & media * Lifecycle Marketing — Event landing pages, email blasts, database email reviews, SEO, copyedit * Recruiting - Onsite booth support * Design — Look & feel, tone, collateral (print), digital, environmental * Large & MidMarket sales teams - Attending & setting up meetings * [Leading Organization Team](/handbook/marketing/community-relations/leading-organizations/) — Executive/customer meetings, attending social events (ex: receptions, dinners), panel discussions, speaking engagements, media interviews
For event execution instructions, please see the Marketing Events page for detailed instruction and the criteria used to determine what type of events are supported.
For both GitLab-owned and external events, speakers and content DRIs should build in steps for legal approvals from necessary parties on public-facing presentations before materials are due.
|Corporate Event||For all General Corporate Events related issues|
|Corporate Marketing||For all General Corporate Marketing issue tracking|
|Events||For all GitLab events|
|Sponsored Corporate Events||For all Sponsored in-person trade shows, events, auxiliary events, etc.|
|Virtual Events||For all Virtual Owned Events|
|Virtual Conference||For all Virtual Sponsored Events|
|Hybrid Conference||For all Sponsored events with an in-person and virtual component|
|GitLab Commit||For all Commit Event related|
|Contribute2022||For all Contribute 2022 Nashville Event|
|Event Execution Issue Templates|
|Event DRI Template|
|Event Travel Staffing Template|
|Promotional Game Rules Template|
|Sponsored Corporate Event Template|
|Internal Partner Issue Templates|
|FM Event SDR Support Issue Template|
|Social Media Event Promotion Issue Template|
|PR Media Podcast Involvement Issue Template|
|Brand Asset Design Requests Issue Template|
|Upload Clean Lead List Post Event Issue Template|
|Post Event Video Upload Issue Template||Pre & Post event outbound email Issue Template</tr>|
At GitLab, the Corporate Events team owns events that meet specific criteria (link), including those events that have a global hybrid or virtual element. By design, virtual events at GitLab are not a simple video call nor are they a static playlist. GitLab virtual events aim to retain the same brand personality, engagement, inclusivity, and fun as our in-person events.
A GitLab virtual event requires 16+ weeks of lead time in order to accommodate the successful planning, scripting, set-up, recording, editing, and executing of a program.
Virtual events require considerable lead time and effort to plan, especially if there are any planned live elements.
In order to create a premium virtual event experience, the Corporate Events team executes virtual events in order to maximize global audience participation and engagement. The considerations in place include:
The Corporate Events team believes that everyone can contribute to virtual events, and so prepares for content to be varied, accessible, and time appropriately to enable as much mental and physical engagement as possible. Plans include:
Having run several global-focused virtual events, the GitLab team has some best practices and recommendations to share with prospective speakers.
As part of the event planning and execution process at GitLab, the event lead will ensure that diversity, inclusion, and belonging initiatives are taken into consideration throughout the entire event process.
The planning committee will ensure that there is an inclusive environment when selecting CFP/keynote/speakers which aligns with GitLab's event requirements for speaking. This includes researching and sourcing for speakers from underrepresented groups and with various backgrounds including:
When working with a vendor or supplier, the team will ensure that the selected venue/vendor/supplier is supportive of GitLab’s DIB values. These may include, but are not limited to the following:
At GitLab, the Corporate Events team wants to continue to play our part and operate with integrity when we are making decisions. The team is consciously making decisions that help align with the company’s social and environmental efforts.
The Corporate Events team works with our swag vendor that sources swag with a goal of 95% of swag is sustainable or eco-friendly or work with companies that have sustainable initiatives. Some categories that the Corporate Events team considers when selecting suppliers are: