At GitLab, our mission is to change all creative work from read-only to read-write so that everyone can contribute.
The Community Relations team supports this mission by working with our community to ensure they receive support and recognition for contributing to GitLab. Contributing to GitLab can include blog posts, code, documentation, discussions on forums/social media, meetups, presentations, translations, UX design, and more. We also support educational institutions and open source projects to host their work on GitLab.
|Abubakar Siddiq Ango||Developer Evangelism Program Manager|
|Brendan O'Leary||Senior Developer Evangelist|
|David Planella||Director of Community Relations|
|John Coghlan||Manager, Developer Evangelism|
|Christina Hupy, PhD||Senior Education Program Manager|
|Nuritzi Sanchez||Senior Open Source Program Manager|
|Michael Friedrich||Developer Evangelist|
|Christos Bacharakis||Senior Code Contributor Program Manager|
|Jamie Rachel||Evangelist Program Manager|
|Philip "Pj" Metz||Education Evangelist|
#community-relationsSlack channel, or by tagging the
We use team-wide calendars for collective notification and to manage team logistics and events. Specific teams within Community Relations, might have their own calendars, such as the Developer Evangelism calendar.
Every quarter, we work on team Objectives and Key Results (OKRs) that align with company OKRs.
To update our list of current OKRs, team members create a new epic in the
Community Relations project, and tag it with their program-specific label (e.g.
open source program
education program etc), as well as the red
OKR label. The naming convention we use for OKRs are:
FY-Year-Quarter OKR: Description of OKR.
We use issue health indicators to help people understand at a glance whether the OKR and its key results are
needs attention or
The Community Relations team has several Key Performance Indicators and related Performance Indicators.
Learn more on the Community Operations budget page
In alignment with GitLab's core value of Diversity, Inclusion, and Belonging (DIB), the Community Relations team seeks to purposefully design DIB into every facet of its programs and operations. We seek to foster DIB at GitLab and within the wider GitLab community.
This section is meant to document tips and best practices that the Community Relations team, and GitLab team, should keep in mind as they plan events and activities.