Cloud 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 objectives
For more information on how objectives are set and managed in GitLab today please review the internal only GitLab Operating Model Handbook page. Developer Relations objectives are labeled with the Owner::DevRel-Strategy label in an internal only group.
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
Automations
Communication
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 through the HelpLab Tech Stack Update process:
| 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 when adding any new tool through the HelpLab Tech Stack Update process.
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: Workato
Developer Relations teams use Workato to automate workflows between tools and platforms.
Workato …
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 May 1, 2026: DevRel tools: Migrate Zapier to Workato (
c41b0fed)
