Given the Developer Evangelism team's familiarity with our community and broad knowledge of GitLab, we regularly engage in managing situations that require GitLab to address urgent and important concerns of our community members.
Our team uses the Community response board to organize tasks.
@johncoghlanin a relevant issue or notify the Developer Evangelism team in the #developer-evangelism Slack channel.
@dev-evangelismUser Group in a Slack message in a Slack thread or channel where the situation is being discussed or the #developer-evangelism Slack channel.
Community responselabel to related issues, epics and MRs. Our team owns the label for the gitlab-com and gitlab-org groups. You can use this quick action:
/label ~"dev-evangelism" ~"Community response"to apply the labels.
+ New topicand selects
Staffas category. This is a private category.
Coordinate blog post publishing with forum topic publishing. This has a circular dependency on each other, and needs to be done in the same minutes.
Communityand saves the edit.
cmd+shift+nin Chrome on macOS).
Tip: If the blog post URL is not ready yet, create an empty forum topic, and add the blog URL in the publishing step. Discourse requires text in the post, use
**TODO: Add blog post URL and description**.
We should strive to automate manual tasks for efficiency and to avoid unnecessary stress to individuals in the response team. In many cases, we use Zapier integrations to post mentions of GitLab in a Slack channel.
While we strive for consistency in the process of monitoring the individual community response channels, in some cases it might not be possible due to the nature of the platform (e.g. lack of an API). In cases where automation is not possible, we distribute monitoring tasks amongst that team.
This is a set of general recommendations for automating the monitoring processes on some of the channels the team will be listening to: