Document best practices for Q&A on the #community-support Slack

[oleg-nenashev]

As @eygraber wrote on Slack:

I used to be more active here, but lately I've stopped. I've been wondering why, and after thinking about it I think it's because there have been a lot of "wall of text" messages coming in that make it extremely hard to catch up on unread messages (especially on mobile). When I encounter that I usually just close the workspace and move on. The Kotlin Slack has been more vocal about this and pushing the use of threads for those types of messages. Not sure if that would be helpful here, but it is something I noticed. I think this should go into something like a #meta channel, but there isn't one.

To address it, we discussed the following:

• [x] We document recommendations about asking questions in this and other channels:
• [ ] We pin the guidelines in the channel and in the welcome message
• [ ] We point people to the guidelines (which might be automated) and recommend updating for long messages.
• [ ] We reserve the right to edit messages when needed and to delete duplicates

Draft recommendations

• Use threads
• Avoid posting the same question on multiple channels
• In the first message, briefly describe the problem. Put all details/samples/logs in the thread responses
• For short messages, use emojis when convenient: +1/-1/ack
• Do not hesitate to edit an opening message or the context messages based on the discoveries. It is better than reposting the whole message

[oleg-nenashev]

Draft of the text: https://gradle.github.io/community/contributing/community-slack/#best-practices

[oleg-nenashev]

Depends on https://github.com/gradle/community/issues/12 ?