Michael FriedrichCloud Resources for Developer Relations
This page outlines cloud resources and workflows used by the Developer Relations team at GitLab. It …
Developer Relations Workflows and Tools
Workflows
Team Workflows
- Code of Conduct Enforcement
- Team Budgets
- Developer Advocate Community Response Process
- Community Operations: Automated Community Programs
- Swag operations
- Content Review / Fix Fridays
Community platforms
Integrations
Communication
Tool Stack Overview
These are the tools the Developer Relations team is the DRI for:
| Tool | Description | How we use it | Technical owner |
|---|---|---|---|
| Common Room | Common Room is a community growth platform that brings together community data to surface insights. |
 Fatima Sarah Khalid |
|
| Discord | Community discussion/chat system for Developer Relations and support teams to collaborate and share knowledge with the wider community. |
Fatima Sarah Khalid |
|
| Discourse | Community discussion platform for Developer Relations and support teams to collaborate and share knowledge with the wider community. | How we use Discourse |
Fatima Sarah Khalid |
| Meetup | Meetupis an event management platform. | How we use Meetup.com |
 John Coghlan
|
| Zapier | Zapier is an automation application integrating other applications. | How Marketing Ops use Zapier, How Developer Relations use Zapier | |
| Zendesk Community | Monitoring and processing all mentions of GitLab across the Community Relations’ response channels | How we use Zendesk |
John Coghlan
|
Community Operations Tool Stack (deprecated)
This overview is currently being deprecated as we attempt to migrate from
the manually-generated list to one automatically-generated from the
data/tech_stack.yml file.
Please use the automatically-generated table instead
Click to show deprecated table
These are the tools the Developer Relations team is the DRI for:
| Tool Name | Description | How We Use |
|---|---|---|
| Crowdin | Crowdin is the platform for the wider community to collaboratively contribute translations for GitLab | How we use Crowdin |
| Discourse | Discourse is the platform on which the GitLab forum is run. | How we use Discourse |
| Discord | Discord is the instant messaging platform the GitLab community communicates on (in addition to GitLab.com itself) | popular channels are #contribute, #general and the support channels |
| Proxi.id | Proxi.id is the platform we use to automatically qualify applications for our community programs | |
| Zapier | Zapier is an automation tool used to identify mentions and to route them into Zendesk as tickets, and also to Slack in some cases | How we use Zapier |
Tools pending addition to tech stack
The Developer Relations team is also the DRI for these tools which are pending addition to the tech stack:
| Tool | Description | How we use it |
|---|---|---|
| Proxi.id | Proxi.id is the platform we use to automatically qualify applications for our community programs |
Other tools we rely on
These are the tools that are essential to some Community programs, but the Developer Relations team are not the DRI for:
| Tool Name | Description | How We Use |
|---|---|---|
| Customer Portal | CustomersDot - Web portal where customers can manage their subscriptions and account information, generate and manage GitLab licenses. | To help troubleshoot issues with community program applications. To create and manage licenses for community program applications and for GitLab EE contributors |
| Marketo | Marketo | Powers each intake form for our (Education, Open Source, and Startups) programs. It is an integration which inserts the application record into Salesforce. |
| Printfection | Printfection is our swag management platform | How we use Printfection |
| Salesforce | Salesforce is our CRM | We use Salesforce (SFDC) to support the Education and Open Source Programs |
| Canva | Canva is the tool we use to create a lot of our GitLab-branded materials. | Community team members should creat an account using their @gitlab.com email and request access to Canva Enterprise from the Design team. |
Adding a new tool to the Developer Relations tool stack
- Please follow the procurement process as you would for adding any new tool to GitLab’s tech stack.
- Ensure that the
group_ownerfield on the tech stack file entry is set toDeveloper Relations. This will make the tool to be automatically listed on the Developer Relations toolstack.
Code of Conduct Enforcement
Overview The Developer Relations team will contribute to enforce the GitLab Community Code of …
Common Room workflows
Common Room is a community growth platform that helps manage, engage, and grow digital communities …
Community Discord workflow
Overview The GitLab Community Discord server is a place to connect with the wider GitLab community, …
Developer Relations tools: Zapier
Zapier subscription We use Zapier to automate the task of forwarding mentions of GitLab, swag store …
Developer Relations workflow: Team Budgets
Team Budgets We use Allocadia to manage team budgets. Due to a limited number of seats being …
Developer Relations Workflows: Content Review
The Developer Relations team provides ongoing support to a number of stakeholders who create content …
E-mail response workflow
Overview Workflow Respond to e-mails sent to our community@, education@, merch@, opensource@, …
Forum workflow
The GitLab community forum (forum.gitlab.com) is a platform for users to register, ask questions, …
Reddit response workflow
Overview The r/gitlab subreddit is a place for questions, discussion, and support on all things …
Stack Overflow: Tagged Questions and GitLab Collective Overview
Overview Stack Overflow is a place for questions, discussions, and support on all things GitLab. …
Swag: Process & FAQ
Contributor Success team members can award Reward Store credits via the Contributor Platform. …
Twitter response workflow
Overview Handles for social channels TWITTER HANDLE RESPOND FROM GUIDELINES @GitLabStatus Zendesk …
Last modified November 13, 2025: remove Zendesk page (
4caa8d05)
