Hey, TLDR: slack +1, IRC -0
My reasoning: Slack is commonly and easily available from the web, an android/iphone/ubuntu touch app, desktop apps and such. It is much easier for anyone to use, with configurable notifications across all devices, silent notifications during certain hours etc. Basically it is much harder to miss something important coming from slack than coming from IRC. Most of the 'build' related projects are also on slack. IRC: IRC is a pain to keep synced with settings accross multiple devices. Some third party systems exist to do that for you but are either paying, or limited in capabilities, (Not to see regularly down). Ben ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, 10 July 2020 10:20, Tristan Daniël Maat <[email protected]> wrote: > Hi, > > > Just a quick +1 to IRC, -1 to Slack. My reasoning is based on my experience > > with the build team slack, which I found difficult to join due to the only > > ingress > > My two cents, I also found this more difficult than necessary. > > > competent users than I may have an easier time of it. > > Though I doubt it's that, I simply think Slack isn't designed with > public chats in mind. An "invite" shouldn't be necessary, and a link > to it shouldn't expire. > > I'd also oppose a suggestion to use Discord for the same reasons, > which has unfortunately also been gaining traction in open source > projects... > > Since this has been a very one-sided conversation so far, I wonder > what the advantages of switching to Slack would be. Is this simply > being suggested because we want a pretty chat client, or is there more > to it? > > Some of the benefits would include better moderation capabilities, I > believe, but I don't currently see a need for that. > > The suggestion to use Slack might be more welcome if current > contributors aren't simply asked if they want to switch with no > apparent benefits ;) > > Tristan Maat
