I didn't realized they removed the email piece... seems like a downgrade. Particularly for projects where you have fairly casual participants.
- Achievable
- Searchable
- Linkable
- Asynchronous
- Accessible
I like using Slack and we use it heavily with my team, but I agree it has issues.
Meanwhile, we've been using mailing lists for established open source projects for years for all of these reasons.
There isn't really much else I don't like about it, I never stop being amazed by how great the keyboard navigation is and how much the "river" of messages improves usability.
I'm intrigued by the Guest option. Do you think it's a good way to communicate with the clients during longer projects?
But yeah for groups you need a mailing list with an archive. It's still better than most IM apps IMO.
> It's still better than most IM apps IMO.
Yes, but you are trading one set of limits for another.
It's a bit surprising that at this point we haven't standardized on something better than essentially IRC versus email.
(Ok not surprising, frustrating)
I get you. But also:
- Email doesn't retain context very well. If I dig back through my email I might have all of the emails in a thread, or maybe not.
- Likewise, I can't send someone a link to a previous emailed conversation so it makes for poor documentation. I can forward an individual email, but not the comment in context.
- Email is not easy to index or post up for reference. You can't link it from a wiki or other documentation for example.
An internal mailing list with archiving would solve many of these issues and might be the best option, but it's a slightly different solution.