From f36d679281d85943d50409062874bde1e0cf35b0 Mon Sep 17 00:00:00 2001 From: K MacLeod Date: Sat, 27 Jul 2019 15:31:08 -0400 Subject: [PATCH] adds threading best practices md --- community/threading_best_practices.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 community/threading_best_practices.md diff --git a/community/threading_best_practices.md b/community/threading_best_practices.md new file mode 100644 index 0000000..8d513ae --- /dev/null +++ b/community/threading_best_practices.md @@ -0,0 +1,12 @@ +# Operation Code Threading Best Practices + +In the interest of keeping conversation flowing and easy to follow for new members, Operation Code has developed these guidelines for the use of the ‘thread’ feature in Slack. +​ +The following is the only rule moderators will make an effort to enforce: +- Threading conversations in #general will be enforced. Members cannot leave this channel, and this is our main channel for organization announcements. +​ +The following are community agreed-upon best practices for the use of the ‘thread’ feature. +- Please thread off-topic convos (e.g. talking about Game of Thrones in #java). +- Consider threading tangentially related topics that may not be interesting to a wide audience, or have to do with a specific use case. +- Please thread one-off comments and asides. +- If the original poster requests that a conversation is in a thread, please honor this request. \ No newline at end of file