This week the Actionhero Community moved from Gitter to Slack.
The move was voted on by the community, and Slack won 4:1. Both tools are free for open source projects, both have web, mobile, and desktop clients, and offer deep integration with the various programming tools we use (GitHub, Travis-ci, etc). For me personally, I had a hard time choosing one over the other.
I’ve been in contact with the Gitter team for some time, and they have been wonderful to work with (and I *think* they might use parts of Actionhero to power Gitter). I wanted to share our reasons for leaving on our first day off of their platform:
You asked me to reach out and explain why the Actionhero community is moving from Gitter to Slack.
Personally, it was a toss-up. I’m a been a happy member of a number of Slack channels/orgs for work, and I’ve also enjoyed my time with Gitter (since 2014!). I’ve had a number of conversations with your team, and you’ve all been very nice and helpful… and made a wonderful (free!) product.
A few folks have been asking to move to Slack for some time, and if you check the last few days of our chat *in* Gitter, I’ve pressed them to explain their reasons. Without any clear feature-differentiation, I think it really came down to "I already need to use Slack for work, I like it, and I don’t want to use more apps". A few folks wanted to have sub-channels (perhaps about a PR or topic), but I don’t know if out community is big enough to use it. However, we put it to a vote, and Slack won… so we are switching.
The Socket.io team has a good paradigm for how to simplify the Slack signup flow for an open source project (which does requite you host a running login service) but they make it simple via Heroku.
All of this said, I believe i’ve offered in the past to help with Gitter if I can, as I think you rely on many of the same technologies as Actionhero… and that offer still stands.
After using Slack for the Actionhero community for a week, I’ve now found some *real* reasons why the platform is working better for the team. I wanted to share them here for other open-source projects which might be considering a similar thing.
Slack simply has more integrations already. Want to add a bot that lets you give kudos to your team? Done. Easy. Want a bot to remind you to do something next week? It exist.
Yes, of course you can connect actionhero to slack as well.
One of the first hurdles was handling signup and registration for the team. This is an open source project, so we want to allow anyone to join without waiting for an administrator to have to approve anything.
Luckily, the socket.io team already handled this for us via Slackin. Slackin is a little app you can run for free on Heroku that creates a simple sign-up page for you team. It take 2 configuration options and can be up-and-running in under 5 minutes.
Slackin also provides Gitter-like chat-badges for your team:
Slack has bridges for both IRC and Jabber. Prefer to use those tools and still interact with the team on Slack? You can!
Only a small amount of the Actionhero team wanted this feature, and I think the utility of these tools is dying off, but it’s nice to know that they are there. Yes, having a wholly open-source stack for your chat is nice, but the "it-just-works" nature of both Slack and Gitter outweighs those concerns for me at this time (for an already open-source project).
In the week since we’ve moved to Slack, the number of chat messages has doubled. This is by far the most important metric. The team is talking more. I bet that this is a combination of 2 things:
While I was skeptical at first, the community was correct: Utility really does increase by using a tool folks already have.
There are a few posts talking about how Slack doesn’t work for large open-source societies, but for now, at Actionhero’s current scale, I think we have found our home.
I write about Technology, Software, and Startups. I use my Product Management, Software Engineering, and Leadership skills to build teams that create world-class digital products.Get in touch