The slack is more better for team discussions then IRC/mailing list.

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

The slack is more better for team discussions then IRC/mailing list.

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

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.

Sorry to be devil's advocate here. I have good enough experience with IRC and Slack (used it at places I have worked at). I would suggest to stay away from Slack. The reason Slack became popular is because of very low learning curve else it works on nearly the same principles as of IRC (sometimes we call it IRC with better UI). Yes it is filled with features, actually it is crowded with features, and that is what makes it evil in the long run. People will start doing stuff which they don't even need, just because it is easy to do (mostly one click) and then there will be garbage all around, broken flows, useless integrations because everyone will have their own ideas. People like the offline feature but it is another evil. In Slack, when you come online after a small break, you will find plethora of messages flowing in sometimes, because no one cares whether you are online or offline. This develops into shortcut habits of sending messages to people now and then. The loop of offline messages created this kind of momentum for slack, and made it a user habit forming product. This gave it the ability to leverage on the FOMO of people. For a new user many things are hard to on IRC, and actually it is good, because then they are done only when there is a strong need. This keeps noise low. The list of things I see mentioned above in favour of slack, are features it has in comparison. Unless lack of such features is creating a critical failure in communication and collaboration, it's better to delay the idea till a pressing need comes. Slack doesn't makes you more productive as compared to IRC, it only makes everyone *feel* more connected. On Fri, Mar 3, 2017 at 1:19 PM, Michal Čihař <michal(a)cihar.com> wrote: -- -- *Hemant Kumar Singh* e-mail: *Gmail <unizen01(a)gmail.com> * contact: +919529068585 _______________________________________________ Developers mailing list Developers(a)phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers

Yes, I also like the feature to send the message to user even when the user is offline. I think we can go with free version. No need to get its paid version. Why you think for the paid version ? Is there any specific feature that you want by going to paid version.

Manish Bisht Email : hi(a)manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/> On Wed, Mar 1, 2017 at 9:38 PM, Isaac Bennetch &lt;bennetch(a)gmail.com <mailto:bennetch@gmail.com>> wrote: Hi, On 3/1/17 3:00 AM, Manish Bisht wrote: This is definitely something I've thought about. Slack is very much the go-to solution for team collaboration right now and has a lot of features that would help us out. However, there are a few downsides. One is the pricing; especially for GSoC hopefuls who would like to participate in discussion it would be an unfair burden to require them to pay the Slack fee and likewise, I don't think the project is interested in funding such an expense either. I do like the ability to catch up on chat conversations that occurred while a user was offline, but aside from that I don't see a big advantage over the mailing list and IRC for occasional realtime chats. This is just my opinion, Isaac <mailto:hi@manishbisht.me <mailto:hi@manishbisht.me>> <https://lists.phpmyadmin.net/mailman/listinfo/developers> _______________________________________________ Developers mailing list Developers(a)phpmyadmin.net <mailto:Developers@phpmyadmin.net> https://lists.phpmyadmin.net/mailman/listinfo/developers <https://lists.phpmyadmin.net/mailman/listinfo/developers> _______________________________________________ Developers mailing list Developers(a)phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers