There are some excellent points here. The visibility and searchability, especially for an open source project, should be paramount. Discourse is a great solution, and seeing it in use by any project install boosts their credibility for me.
I still think chat can have a place in a project. Using it for things like build/deployment notifications and minor progress updates has been a boon for me at my current job. It can also be used for user/developer support. Sometimes, I don't want to post some big long thing on a more public forum. I want to talk to someone right away that help with an unusual use case. Stuff like that might get buried on a forum.
Chat has a great place in projects. I think it needs to be a complementary environment, rather than the core one. Slack is weird in that you access this whole different environment just for the chat, so I think it leads you to wanting to do too much with it. Also, Slack as a company doesn't really seem to have an interest in serving this community. Gitter is better in this regard, but still not really a "full solution". Gitter was acquired by GitLab, so it will be interesting to see what they might do with it.
Yeah, Slack seems like overkill for chat, period. We use Atlassian's products at my job, so we're all in on Jira/Bitbucket/HipChat, and the combination of the three is really excellent.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There are some excellent points here. The visibility and searchability, especially for an open source project, should be paramount. Discourse is a great solution, and seeing it in use by any project install boosts their credibility for me.
I still think chat can have a place in a project. Using it for things like build/deployment notifications and minor progress updates has been a boon for me at my current job. It can also be used for user/developer support. Sometimes, I don't want to post some big long thing on a more public forum. I want to talk to someone right away that help with an unusual use case. Stuff like that might get buried on a forum.
Chat has a great place in projects. I think it needs to be a complementary environment, rather than the core one. Slack is weird in that you access this whole different environment just for the chat, so I think it leads you to wanting to do too much with it. Also, Slack as a company doesn't really seem to have an interest in serving this community. Gitter is better in this regard, but still not really a "full solution". Gitter was acquired by GitLab, so it will be interesting to see what they might do with it.
Yeah, Slack seems like overkill for chat, period. We use Atlassian's products at my job, so we're all in on Jira/Bitbucket/HipChat, and the combination of the three is really excellent.