You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: communications/slack-culture.rst
+12-11
Original file line number
Diff line number
Diff line change
@@ -88,25 +88,25 @@ You can save space, time, and distractions to others by using commonly understoo
88
88
Direct messages
89
89
---------------
90
90
91
-
Please keep direct messaging to a user or a set of users to minimum.
91
+
Please keep direct messaging to a user or a set of users to a minimum.
92
92
Direct messages should be avoided for any technical discussions or asking for support, even if you are sure that you have involved all those who are interested or who can contribute.
93
-
Instead, such discussions should be in a thread in an appropriate :ref:`discussion channel<slack-discussion-channels>`.
94
-
Direct messages shoul be reserved for conversations on topics such as code review requests, logistics, or on other topics not directly related to work.
93
+
Instead, such discussions should be in a thread in an appropriate :ref:`discussion channel<slack-discussion-channels>` and support questions must be asked in an appropriate :ref:`support channel<slack-support-channels>`.
94
+
Direct messages should be reserved for conversations on topics such as code review requests, logistics, or on other topics not directly related to work.
95
95
See this `community post`_ for why direct messages are considered harmful.
Slack has a feature that allows a user to edit a message sent by that user.
105
-
This feature must be used for typographical or grammatical errors that the user wishes to correct, or if the message is accidentally sent before it is fully typed out.
106
-
While Slack is less formal than email, messages should be coherent and in multiple sentences if required, instead of multiple single-line messages in short bursts. This is so that it is easy to link to them elsewhere in the future.
107
-
In place of amending a message, it is preferable to use strikethrough to retract an idea or statement that If you post something you recognize as wrong.
108
-
A corrected statement can be added next to it.
109
-
A message should be deleted only if posted in a wrong channel, or if it is not appropriate in a social forum.
105
+
106
+
- This edit feature is ideal to correct typographical or grammatical errors, or if the message is accidentally sent before it is fully typed out.
107
+
- In order to easily link them elsewhere, messages should be coherent and in multiple sentences if required, instead of multiple single-line messages in short bursts.
108
+
- In place of amending a message, it is preferable to use strikethrough ``~text~`` to retract an idea or statement that if you post something you recognize as wrong. A corrected statement can be added next to it. This prevents surprises of seeing a notification and not finding that message on Slack. Moreover, this indicates the thought process undergone and avoids somebody else posting the same point again.
109
+
- A message should be deleted only if posted in a wrong channel, or if it is not appropriate in a social forum.
110
110
111
111
.. _slack-snippets:
112
112
@@ -217,7 +217,8 @@ If you need to have a group created because you have a routine need to @-mention
217
217
@-mentioning a particular user notifies that user and adds the message to their "Mentions & reactions" list.
218
218
Be aware of the person's timezone before @-mentioning them.
219
219
If you need to @-mention them outside normal hours, you may want to schedule the message to be posted later (using the ``/send`` or more sophisticated ``/schedule`` shortcuts from `Timy`_).
220
-
Sometimes @-mentioning a user can be helpful to disambiguate replies in a multi-person conversation, but if you find yourself prefixing every message you send with an @-mention, consider whether it is implied by context or whether the whole conversation might be better in a thread.
220
+
Sometimes @-mentioning a user can be helpful to disambiguate replies in a multi-person conversation, but if you find yourself prefixing every message you send with an @-mention, consider whether it is implied by context or whether the whole conversation might be better in a thread or in direct messages to that user if the issue at hand is unique to the user.
221
+
An example where it is acceptable to move to direct messaging would be to help out unexpected login issues faced by the user.
0 commit comments