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:
• [x] We pin the guidelines in the channel and in the welcome message
• [x] We point people to the guidelines (which might be automated) and recommend updating for long messages.
• [x] 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 ?

[oleg-nenashev]

@Vampire I recently added a Canvas with the links and the summary. Arguably it does not help too much given today's events, but this ticket seems to be mostly done. WDYT?

[Vampire]

Even if you establish a system where one can neither read anything not write anything unless they click "I have read the rules", most people just click it away without having read them.

When did you last actually read ToS you accepted? :-D

But yeah, I've seen the Canvas. Many people tend to not even read channel names and if they do then most often not channel topics. I don't expect too many people looking at the Canvas, or even noticing it, especially if they are new to Slack. But it's good to have it there, so that you can point with a finger at it. :-)

[oleg-nenashev]

When did you last actually read ToS you accepted? :-D

On Saturday :P But yeah I get the point. For us it is a reference when taking action, not something we expect users to read or remember

I don't expect too many people looking at the Canvas, or even noticing it, especially if they are new to Slack.

One step at a time. Normally I would do a welcome bot, but we are out of integration slots for the free Slack

Many people tend to not even read channel names and if they do then most often not channel topics.

Sadly, no "move" feature in Slack. I miss that a lot