News for hackers. Stuff that matters.
Re:Why Slack is inappropriate for open source communications by freehunter on Tuesday April 11, 2017 @12:12PM (#14089471)
What you're looking for is email. Multi-user chat simulates a real life conversation, and in real conversations it's also awkward to say "hey so going back to what we were talking about 15 minutes ago..." after the conversation has moved on.
Re:Why Slack is inappropriate for open source communications by NateDad on Tuesday April 11, 2017 @12:36PM (#14089750)
No, email is terrible. There's no history. You can't "scroll up" to see what people were talking about. You can't link to another specific email to reference it (yes, there's archive services, but then you have to go dig through an archive to try to find a horridly formatted email to link to, which is completely separate from the normal consumption platform).
Re:Why Slack is inappropriate for open source communications by freehunter on Tuesday April 11, 2017 @12:39PM (#14089785)
I actually argued here recently that email was hard to switch away from because of the history. You can keep your emails forever. I have emails from 2007 sitting in my inbox. And if I want to keep them, I can download them with IMAP or POP. If I send an email to five people and they remember to hit "reply all", well that's a conversation, isn't it? And if I need to show someone an email they weren't party to originally, I can forward it to them.
Re:Why Slack is inappropriate for open source communications by NateDad on Tuesday April 11, 2017 @02:06PM (#14090766)
That puts the onus on every single person to maintain the history of the project. Lots of people delete mail (not me, but lots of people). Also, you can't retain history of what was sent before you joined. Also, emailing individual documents means people can't research by themselves.
Re:Why Slack is inappropriate for open source communications by freehunter on Tuesday April 11, 2017 @05:51PM (#14092829)
I mean, email isn't meant to be a document repository. Slack (or other chat) is great for immediate conversations with many people. Email is great for slower conversations with a more limited number of people. A wiki is great for a very slow conversation. An actual document repository is great to be able to link to when using any of the other conversation methods.

Just because Slack isn't good at slow conversations doesn't mean it's bad. Just because email is bad at including people who joined after the fact doesn't mean it's bad. Those aren't their strengths, and that's fine. They still serve their own purpose just fine.

Re:Why Slack is inappropriate for open source communications by u801e on Saturday April 15, 2017 @08:24PM (#14123652)
You're correct, but Usenet does provide those features and is very similar to email from a user standpoint.
Re:Why Slack is inappropriate for open source communications by snakeanus on Thursday April 13, 2017 @09:34AM (#14106689)
This is just wrong.