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||Staff Developer Evangelist|
|Christina Hupy, PhD||Manager, Education Program|
|Christos Bacharakis||Senior Code Contributor Program Manager|
|David Planella||Director of Community Relations|
|Jamie Rachel||Evangelist Program Manager|
|John Coghlan||Manager, Developer Evangelism|
|Michael Friedrich||Senior Developer Evangelist|
|Nuritzi Sanchez||Senior Open Source Program Manager|
|Philip "Pj" Metz||Education Evangelist|
#community-relationsSlack channel, or by tagging the
Every six weeks, we run a Group conversation for the benefit of other team members. When posting to the What's happening at GitLab Slack to announce a Group Conversation, use the following format to create an engaging and entertaining post.
[Intro with emoji] Please join me on [Day, 202X-XX-XX, time] for the :community: community Relations Group Conversation! :flashlight: We plan on highlighting: - [list of highlights] :google_slides: Check out the [slides link] to learn what we've been up to. :google_docs: Please add questions to the [ agenda doc link] ahead of time so we can jump right in. :ninja_turtle_jumping_yay: [outro with call to action to join and some more emojis] See you then!
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.
OKRs we seek to align with:
To update our list of current OKRs:
Community Relationsproject. The naming convention we use for OKRs is:
FY-Year-Quarter OKR: Description of OKR
open source program
Issue Health: We use issue health indicators to help people understand an OKRs status at a glance. These status indicators are:
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.
We take inspiration from the great work being done by other communities. Some of the communities who we take inspiration from:
The Community Learning Pathway is a course built to educate the community on how the Community works, the different community programs and how to contribute the GitLab. Members of the Community and GitLab team members who complete the course will earn a badge.