3 ms·

This seems like a very simple problem to solve - the issue owner should move important discussions to somewhere that isn't Slack. Writing a summary (or just cut

This seems like a very simple problem to solve - the issue owner should move important discussions to somewhere that isn't Slack. Writing a summary (or just cut and paste from the Slack messages) into a Jira or Github issue comment isn't much effort, and reading a summary of a problem is a lot easier for new people. This actually highlights a problem of Slack. Reading an old Slack conversation is massively inefficient, especially if people have chimed in with irrevelevant stuff. Taking what you learn from a Slack conversation and using it to update proper docs or an issue is far better for anyone who isn't part of that conversation at the time.

OskarS 5y ago
The problem here isn’t Slack. Clearly the participants prefer discussing things like this in Slack over doing it in issues or Jira or whatever (which I understand, it’s a much nicer medium for discussion, IMHO), otherwise they would already be doing that. Your suggestion is essentially “just subvert the IT/legal policies by discussing it elsewhere, in a less efficient way”. Clearly the problem here is the policy.
quietbritishjim 5y ago
> move important discussions to somewhere that isn't Slack At first I read this as having the discussion on a different medium in the first place, which seems a bit extreme. But from the rest of your comment I think mean just copy the discussion rather than move it, by copying and pasting (or manually re-summarising) elsewhere. I definitely agree with that. As you say at the end, that's a good idea even if Slack messages aren't auto-destroyed. (But there are definitely cases where it seems like you'll never need some scrap of information again and then it turns out you do.)