“Please don’t use Slack for FOSS projects” is a compelling case for why you shouldn’t use Slack for Free and Open Source Software projects. Make sure to read the discussion in the comments as well. (By the way, many of the arguments apply to HipChat too).
The suggested alternative is IRC, which I agree with. My only minor disagreement in regards to IRC is using it for companies as well. Companies are much more fragile and sensitive than Open Source community, so it doesn’t work all that well in some places. I think Slack/HipChat work great for company communications, but if you want to have full control over your chat system, then try out Rocket.Chat, which I blogged about earlier this year.
Franz is a free messaging app which currently supports Slack, WhatsApp, WeChat, HipChat, Facebook Messenger, Telegram, Google Hangouts, GroupMe, Skype and many more. Download is available for Mac, Windows, and Linux.
Chat is becoming more and more important for team communication and collaboration (what is ChatOps?). Old school applications like Skype are being replaced with modern, web-based chat platforms, that provide group/room and one-on-one chats, file uploads, screen sharing, voice and video communications, API integration and more. There are plenty of solutions to choose from too.
Traditionally, self-hosted solutions were difficult to setup and maintain, and were lacking in integration options. So many teams choose to go for the third-party hosted approach. This is not very exciting for companies that deal with sensitive data though.
As mentioned before, at work, we are using HipChat. It’s nice, it’s free, and it integrates nicely. Lately, there has been a lot of hype about Slack, which I tried, but didn’t particularly like.
You can try the live demo, or deploy it to your infrastructure via a gadzillion different methods, or read the beautiful documentation. And there’s a rumor of HipChat and Slack import tool, so you won’t have to start from scratch…
Let me know what you think.