4 ms·
Slack is the wrong choice for large community projects for one pragmatic reason: the 10,000 message limit for free teams. I participate in a large developer com
by mshenfield 11y ago
Slack is the wrong choice for large community projects for one pragmatic reason: the 10,000 message limit for free teams. I participate in a large developer community that lives on Slack. Conversations are deleted quickly on less active channels like #lisp or #volleyball, sometimes within a day. This is frustrating when trying to connect to like minded people and also maintain a record and resource for community members. And at $6.67/user/month it really isn't viable to upgrade.
I can't speak to the quality of projects like Mattermost [1] and Zulip [2], though I'm excited by their concepts. IMO trying these, or using a hosted service designed for community projects like Gitter [3] are necessary alternatives.
[1] http://www.mattermost.org/ http://www.mattermost.org/
[2] https://www.zulip.org/ https://www.zulip.org/
[3] https://gitter.im/ https://gitter.im/
- pmontra 11y agoYes, the 10k limit kills it. After that you can still search old messages and find them but you lose the context because you see only a few lines around them. Either your FOSS project has a budget to pay Slack or you're bound to lose any valuable knowledge and decision buried in the archive.