When responding to community messages, you should always strive to involve a resident GitLab expert on the subject if possible.
Refer to the Product stages, groups, and categories page to locate the appropriate expert/team.
Please mention the expert by name in the relevant Slack channel (e.g. in
#frontend if it's a frontend question) with the following template. If you are unsure of the correct channel, you can ping the experts in the
For expert responses on blog posts, first check if the blog author is a GitLab team member, and reach out to them directly. If the blog author is not a GitLab team member, the content team may be able to help connect you over email.
If you are working on a mention that requires an expert from a particular devops stage, you can find them in the Slack channels named
@expert_username [LINK TO COMMUNITY COMMENT] Hello! I need support from an expert to respond to this. Can you please answer on [name of social platform] using your personal account? Even if you are in a rush, remember - your direct response is a better experience for you and the requestor! If you don't know the answer, could you share your thoughts and ping a specific expert who might? We're trying to make sure every comment gets a response. Thank you! https://about.gitlab.com/handbook/marketing/community-relations/community-advocacy/#can-you-please-respond-to-this
If there is no Zendesk ticket related to the mention (e.g. a HackerNews mention) track it in the
#community-relations Slack channel.
expert-respondedmacro and tag.
expert-respondedtag in the past 30 days. You can also filter the data by view to study usage of the tag in individual Zendesk views.
expert-respondedtag in Zendesk, navigate to the Admin section and choose Tags. Click on the
expert-respondedtag to view all tickets solved with this macro.
When trying to figure out who has expertise on what segment of the product, refer to the "DevOps Stages" section of the Product stages, groups, and categories page in the handbook. The team page can also be useful.