I like slack, mostly because it has been widely accepted for internal company communications. This lets people who have a day job in a place that isn’t going to allow discord to be more active.
Even if we get Slack at the nonprofit 85% off rate, it would cost over $8,000 a month for the amount of users we have today.
1 Like
I disagree with this characterization of Matrix. At least for a technical community, Matrix is more than ready, especially when using Element. A number of other communities are making the switch from IRC to Matrix (most notably, Fedora and openSUSE). I would personally heavily favor us using Matrix from the get-go. We can plumb Matrix rooms back to IRC channels on Freenode for those who prefer IRC, and both sides (Matrix and IRC) see each other as first-class members in a chatroom.
1 Like
+1 it would be a great promo/marketing for Slack to do so. Having so many dev/system admins exposed to Slack when they wouldn’t necessarily use it would/can influence and shape their opinion on Slack and maybe take that experience back to their own workplaces/companies and look at using Slack etc
1 Like
Ah… makes sense then.
I’m not a huge fan of Matrix having run a Matrix server previously because it’s a lot of overhead to ask of users and at least as of the last time I used it, not all common platforms were first class citizens in that ecosystem in terms of client applications. As a community we won’t only be using *nix platforms.
The objection I have to Discord is similar to the one I have regarding Slack: that it isn’t an open-source product that we could run ourselves if something were to happen. With this project we’re already facing the need to have chat archives and should Discord shut down, it would be additional work to make that history available in a useful way.
But in terms of the proverbial “today”, while I like Discord personally as a product, for the Rocky Linux project I’d personally be in favor of options that can be run on our own infrastructure even if we don’t start in that mode. For example if we were to start on Mattermost’s managed option (perhaps as a sponsored option) and eventually move to our own infrastructure.
Given the events that led us all here, I think the option for independence of our software should be a decision-influencing consideration.
With all of that said, I am in a sponsored Slack Workspace and it works very well. I don’t know what all is involved in those licensing agreements but it wouldn’t hurt to reach out and see? @leigh, @hbjy?
We’re going to be going with Mattermost. It meets all the security and auditing requirements, and they have a very price-attractive setup for non profits
6 Likes
To anyone visiting this post in the future:
- is it the year of the linux desktop yet?
- You can find more information about joining our Mattermost server here.
1 Like