From e7d7a8c98f2065e5e214a80a7cfa22916258b5d7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matija=20=C4=8Cupi=C4=87?= Date: Thu, 28 Sep 2017 07:11:22 +0200 Subject: [PATCH] Refactor the involving experts workflow --- .../developer-relations/community-advocacy/index.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/handbook/marketing/developer-relations/community-advocacy/index.html.md b/source/handbook/marketing/developer-relations/community-advocacy/index.html.md index bd29d673260..2b0ab5b4c67 100644 --- a/source/handbook/marketing/developer-relations/community-advocacy/index.html.md +++ b/source/handbook/marketing/developer-relations/community-advocacy/index.html.md @@ -249,13 +249,13 @@ This gives: * shows that our whole company is comitted to helping people * the expert more feedback from users -Please ping the expert with: +Please ping the expert in the relevant channel (e.g. in `#frontend` if it's a frontend question) with: ```plain @expert_username [LINK TO COMMUNITY COMMENT] https://about.gitlab.com/handbook/marketing/developer-relations/community-advocacy/#can-you-please-respond-to-this? ``` -And add an internal note with the link of the Slack message to the associated Zendesk ticket +And add an internal note with the link of the Slack message to the associated Zendesk ticket. If there is no Zendesk ticket related to the mention (e.g.a HackerNews mention) track it in the `#devrel` channel. ## Can you please respond to this? -- GitLab