[17:48] <waldo323> thats perfectly fine :) i appreciate the responses 
[17:48] <cmaloney> yeah, there's not a lot of great choices
[17:48] <waldo323> it also wasn't a time sensitive question.  
[17:48] <cmaloney> Teams seems to be the one that most folks use because it's included with their live365 stuff
[17:50] <waldo323> yeah i think we may get it by default but maybe we can use something else for most things (or even just my team and the devs, I'd be okay with that)
[17:51] <waldo323> mattermost has been on the top of my short list, rocketchat and tulip also looked okay
[17:56] <greg-g> I wish we (Wikimedia) would have gone with mattermost (or matrix) instead of slack, le sigh
[17:57] <greg-g> (for internal staff comms, not community/volunteer, WHICH IS THE PROBLEM)
[18:10] <waldo323> due to features or other reasons?
[18:10] <greg-g> features/FLOSS ideals (yeah, I'm a grey beard at this point)
[18:11] <greg-g> and the reality that Slack won't be able to ever be an option for volunteers to engage with staff, but mattermost/matrix could have been
[18:12] <waldo323> ah :) yeah o
[18:12] <waldo323> *I like having a floss solution when possible 
[18:37] <cmaloney> Matrix / mattermost is what I'd go with
[18:40] <ben> matrix is hot trash
[18:40] <ben> mattermost is alright