Cloud Resources for Developer Relations
This page outlines cloud resources and workflows used by the Developer Relations team at GitLab. It …
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. |
![]() |
|
Discord | Community discussion/chat system for Developer Relations and support teams to collaborate and share knowledge with the wider community. |
![]() |
|
Discourse | Community discussion platform for Developer Relations and support teams to collaborate and share knowledge with the wider community. | How we use Discourse |
![]() |
Meetup | Meetupis an event management platform. | How we use Meetup.com |
![]() |
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 |
![]() |
data/tech_stack.yml
file.
Please use the automatically-generated table instead
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 |
SheerId | SheerId is the platform we use to automatically qualify applications to 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 |
Zendesk | Zendesk is the tool Community Ops, EDU & OSS work their program cases and applications | How we use Zendesk |
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 |
---|---|---|
SheerId | SheerId is the platform we use to automatically qualify applications to our community programs |
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, Open Source and Startup 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. |
group_owner
field on the tech stack file entry is set to Developer Relations
. This will make the tool to be automatically listed on the Developer Relations toolstack.5b5a36c1
)