Its better for us as:
1. Able to message members even when they are not online.
2. Integrate Google hangout for calls and video conferencing https://slack.com/apps/A0F7YS351-google-hangouts
3. Apps Integrations : https://slack.com/apps
4. Code snippets: Slack has built-in support for them. On IRC you’re just asked to use a pastebin like Gist.
5. File transfers: Slack does them. IRC also does them through XDCC, but this can be difficult to get working.
6. Persistent sessions: Slack makes it so that you can see what you missed when you return. With IRC, you don’t have this. If you want it, you can set up an IRC bouncer like ZNC.
5. Integrations: with things like build bots.
Some of them were mentioned on the same link that you have written.

Yes, By default it is invite only. But I have seen that the other organisations have automated it using code. So that the process become similar to subscribing to mailing list. Here is the code and deploying steps available.
1. https://github.com/outsideris/slack-invite-automation
2. https://github.com/rauchg/slackin
First one will be better to use and deploy to Heroku.
I can also help in setting it up.

No need for guest account. as we can now add members to slack same as that of how members are added in mailing list.

We can't make archives publicly available but they are only for the users who are members of the channel.

Thanks,

Manish Bisht
Email : hi@manishbisht.me
Website : https://manishbisht.me

On Thu, Mar 2, 2017 at 7:48 PM, Michal Čihař <michal@cihar.com> wrote:
Hi

Manish Bisht píše v St 01. 03. 2017 v 16:20 +0530:
> The slack is more better for team discussions then IRC/mailing list.

Why exactly is it better?

I've just quickly tried that. What surprised me most is that it's
invite only. Is there some way to allow people to join without inviting
them first? This really sounds ridiculous for free software project...

There seems to be something what they call "Guest Accounts". I have no
clue how that works, but that is available only in paid plans.

Also is there way to make the archives publicly available?

> For the starting phase we can take gsoc and prefer to make gsoc
> conversions there. Then the phpmyadmin team can see the results and
> if most of the people agree then we can move to slack. Here are the
> links which tells the slack features and why it is better over IRC.
> https://thenextweb.com/insider/2015/03/24/slack-is-quietly-unintentio
> nally-killing-irc/#.tnw_iDkdSVCS
> https://slack.com/is

I can also find some links:

http://sircmpwn.github.io/2015/11/01/Please-stop-using-slack.html

--
        Michal Čihař | https://cihar.com/ | https://weblate.org/

_______________________________________________
Developers mailing list
Developers@phpmyadmin.net
https://lists.phpmyadmin.net/mailman/listinfo/developers