Most of our releases end up on Hacker News. Some of them hit the first page. These Hacker News posts are the top priority for us to answer to. They're both important and urgent.
Every comment should get a response from someone from the company. Feel free to use this template. If you or the expert don't know the answer to a comment/remark please share your thoughts because every remark should have at least one response.
The #hn-mentions Slack channel tracks mentions of GitLab on HackerNews. It is a dedicated one, so that Community Advocates enable channel notifications and can respond to them as soon as possible.
Go through the tickets in Zendesk Hacker News view
See if all comments have received responses
Write the response if necessary, involve an expert for assistance if you don't know the answer
Ping @sytse in the #community-relations Slack channel if you judge his input is required, or in case of doubt
Never submit GitLab content to Hacker News. Submission gets more credibility if a non-GitLab Hacker News community member posts it, we should focus on making our posts interesting instead of on submitting it.
Don't link to any Hacker News submissions to prevent setting off the voting ring detector. Trying to work around the voting ring detector by up-voting from the new page is not reliable, just don't announce nor ask for votes.
Don't make the first comment on a HackerNews post about GitLab, wait for people to leave comments and ask questions.
Avoid using corporate jargon like 'PeopleOps'.
Always address the HackerNews community as peers. Be sure to always be modest and grateful in responses.
If you comment yourself make sure it is interesting and relevant.
Note: You can find the full list of social media guidelines here