Hi, I have on suggestion. Can someone from the core team can create the slack channel for phpmyadmin. It's the better place to communicate with other Developers compared to IRC. Thanks, Manish Bisht hi@manishbisht.me https://manishbisht.me
Hello Manish Bisht píše v St 01. 03. 2017 v 13:30 +0530:
I have on suggestion. Can someone from the core team can create the slack channel for phpmyadmin. It's the better place to communicate with other Developers compared to IRC.
Can you please elaborate a bit why it is better? I guess most of the team has no experience with it (including myself). -- Michal Čihař | https://cihar.com/ | https://weblate.org/
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-unintentionally-k... https://slack.com/is Thanks, Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me On Wed, Mar 1, 2017 at 1:36 PM, Michal Čihař <michal@cihar.com> wrote:
Hello
Manish Bisht píše v St 01. 03. 2017 v 13:30 +0530:
I have on suggestion. Can someone from the core team can create the slack channel for phpmyadmin. It's the better place to communicate with other Developers compared to IRC.
Can you please elaborate a bit why it is better? I guess most of the team has no experience with it (including myself).
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
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/
Hi A good alternative to Slack would be Gitter [0]. Another would be the Discord app [1]. [0] https://gitter.im/ [1] https://discordapp.com/ Maurício Meneghini Fauth On Thu, Mar 2, 2017 at 11:18 AM, 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
I wouldn’t go Discord on this one, the main feature for Discord is (in my opinion) the voice chat, which I don’t think it’ll help. I’ve been part of the mailing list for years and having Slack would be a great addition, specially for tracking progress and communicating with the GSoC students, I wouldn’t like to replace the mailing list with Slack though. As for the invitation only, we can just place a link to it wherever, that person would be asked for an email address and that’s it. Guillermo. From: Maurício Meneghini Fauth<mailto:mauriciofauth@gmail.com> Sent: Thursday, March 2, 2017 10:16 AM To: Developer discussion for phpMyAdmin<mailto:developers@phpmyadmin.net> Subject: Re: [phpMyAdmin Developers] Slack channel for phpmyadmin Hi A good alternative to Slack would be Gitter [0]. Another would be the Discord app [1]. [0] https://gitter.im/ [1] https://discordapp.com/ Maurício Meneghini Fauth On Thu, Mar 2, 2017 at 11:18 AM, Michal Čihař <michal@cihar.com<mailto: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<mailto:Developers@phpmyadmin.net> https://lists.phpmyadmin.net/mailman/listinfo/developers
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
Hi Manish Bisht píše v Čt 02. 03. 2017 v 21:00 +0530:
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.
Okay, there are some features we don't need, some which were in IRC for ages (bots), but there are certainly some things which could be useful (offline messaging and session persistence). Do you have experience how does Slack compare to Gitter?
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.
Sorry, but I'm not going to workaround platform deficiencies by deploying additional apps unless absolutely necessary - this is something what can easily break and we really don't want to maintain additional infrastructure with small manpower we have.
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.
I find this unacceptable for our usage. Anyway to test the things, I've quickly setup both Slack and Gitter for us: https://phpmya.slack.com/ https://gitter.im/phpmyadmin And at first look Gitter seems way better fit for what we do (keeping away question WHETHER we want to move from IRC to something like this). -- Michal Čihař | https://cihar.com/ | https://weblate.org/
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@cihar.com> wrote:
Hi
Manish Bisht píše v Čt 02. 03. 2017 v 21:00 +0530:
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.
Okay, there are some features we don't need, some which were in IRC for ages (bots), but there are certainly some things which could be useful (offline messaging and session persistence). Do you have experience how does Slack compare to Gitter?
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.
Sorry, but I'm not going to workaround platform deficiencies by deploying additional apps unless absolutely necessary - this is something what can easily break and we really don't want to maintain additional infrastructure with small manpower we have.
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.
I find this unacceptable for our usage.
Anyway to test the things, I've quickly setup both Slack and Gitter for us:
And at first look Gitter seems way better fit for what we do (keeping away question WHETHER we want to move from IRC to something like this).
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
-- -- *Hemant Kumar Singh* e-mail: *Gmail <unizen01@gmail.com> * contact: +919529068585
I have checked the link slack and no one can't login into it till they got invite for it from admin. So to automate that https://github.com/outsideris/ slack-invite-automation this will be required. We have to deploy it only once no need to maintain it. I have no experience with gitter. but it looks like more useful then slack. So we can also try this instead of slack. Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me On Fri, Mar 3, 2017 at 4:45 PM, Hemant Singh <unizen01@gmail.com> wrote:
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@cihar.com> wrote:
Hi
Manish Bisht píše v Čt 02. 03. 2017 v 21:00 +0530:
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.
Okay, there are some features we don't need, some which were in IRC for ages (bots), but there are certainly some things which could be useful (offline messaging and session persistence). Do you have experience how does Slack compare to Gitter?
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.
Sorry, but I'm not going to workaround platform deficiencies by deploying additional apps unless absolutely necessary - this is something what can easily break and we really don't want to maintain additional infrastructure with small manpower we have.
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.
I find this unacceptable for our usage.
Anyway to test the things, I've quickly setup both Slack and Gitter for us:
And at first look Gitter seems way better fit for what we do (keeping away question WHETHER we want to move from IRC to something like this).
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
-- -- *Hemant Kumar Singh* e-mail: *Gmail <unizen01@gmail.com> *
contact: +919529068585
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Manish Bisht píše v Pá 03. 03. 2017 v 21:38 +0530:
I have checked the link slack and no one can't login into it till they got invite for it from admin. So to automate that https://github.com/outsideris/slack-invite-automation this will be required. We have to deploy it only once no need to maintain it.
Yes, this is what I was talking about.
I have no experience with gitter. but it looks like more useful then slack. So we can also try this instead of slack.
At least it doesn't have the ridiculous invite only setup. I have no experience with either of these... -- Michal Čihař | https://cihar.com/ | https://weblate.org/
Hi, On 3/1/17 3:00 AM, Manish Bisht wrote:
Hi,
I have on suggestion. Can someone from the core team can create the slack channel for phpmyadmin. It's the better place to communicate with other Developers compared to IRC.
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
Thanks,
Manish Bisht hi@manishbisht.me <mailto:hi@manishbisht.me> https://manishbisht.me
_______________________________________________ Developers mailing list Developers@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@manishbisht.me Website : https://manishbisht.me On Wed, Mar 1, 2017 at 9:38 PM, Isaac Bennetch <bennetch@gmail.com> wrote:
Hi,
On 3/1/17 3:00 AM, Manish Bisht wrote:
Hi,
I have on suggestion. Can someone from the core team can create the slack channel for phpmyadmin. It's the better place to communicate with other Developers compared to IRC.
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
Thanks,
Manish Bisht hi@manishbisht.me <mailto:hi@manishbisht.me> https://manishbisht.me
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
On 3/1/17 11:19 AM, Manish Bisht wrote:
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.
I'm not sure I really understand their licensing for the free service tier. I was on https://slack.com/pricing which says "For teams wanting to try out Slack" which seems pretty clear that it's for evaluation purposes only. But just now I clicked the "Learn more" link (which I didn't even see at first due to not having hovered directly over the magical area) and the popup says "If you’re happy with our Free plan, please carry on" which definitely sounds like we could use it even past the evaluation phase. I guess I'd have to reach out to them to see what their true intent is since I'm interpreting two different meanings from the text on their site. Isaac
Manish Bisht Email : hi@manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/>
On Wed, Mar 1, 2017 at 9:38 PM, Isaac Bennetch <bennetch@gmail.com <mailto:bennetch@gmail.com>> wrote:
Hi,
On 3/1/17 3:00 AM, Manish Bisht wrote: > Hi, > > I have on suggestion. Can someone from the core team can create the > slack channel for phpmyadmin. It's the better place to communicate with > other Developers compared to IRC.
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
> Thanks, > > Manish Bisht > hi@manishbisht.me <mailto:hi@manishbisht.me> <mailto:hi@manishbisht.me <mailto:hi@manishbisht.me>> > https://manishbisht.me > > > _______________________________________________ > Developers mailing list > Developers@phpmyadmin.net <mailto:Developers@phpmyadmin.net> > https://lists.phpmyadmin.net/mailman/listinfo/developers <https://lists.phpmyadmin.net/mailman/listinfo/developers> >
_______________________________________________ Developers mailing list Developers@phpmyadmin.net <mailto:Developers@phpmyadmin.net> https://lists.phpmyadmin.net/mailman/listinfo/developers <https://lists.phpmyadmin.net/mailman/listinfo/developers>
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
I can guide you for setting up the phpmyadmin slack account. Go to this link https://slack.com/create to create the phpmyadmin slack account and fill the details there to create the account and if it ask for pricing in between select the free one. "For teams wanting to try out Slack" means the teams can create account and try free for unlimited period of time. and if the teams want to use the advance features then they can upgrade the account by paying prices which we don't require. Right now I know many communities that uses the slack free version without any problem like Fossasia, Systers etc. Let me know if you still faces some issues in between. Manish Bisht Email : hi@manishbisht.me Website : https://manishbisht.me On Wed, Mar 1, 2017 at 10:02 PM, Isaac Bennetch <bennetch@gmail.com> wrote:
On 3/1/17 11:19 AM, Manish Bisht wrote:
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.
I'm not sure I really understand their licensing for the free service tier. I was on https://slack.com/pricing which says "For teams wanting to try out Slack" which seems pretty clear that it's for evaluation purposes only. But just now I clicked the "Learn more" link (which I didn't even see at first due to not having hovered directly over the magical area) and the popup says "If you’re happy with our Free plan, please carry on" which definitely sounds like we could use it even past the evaluation phase. I guess I'd have to reach out to them to see what their true intent is since I'm interpreting two different meanings from the text on their site.
Isaac
Manish Bisht Email : hi@manishbisht.me <mailto:hi@manishbisht.me> Website : https://manishbisht.me <https://manishbisht.me/>
On Wed, Mar 1, 2017 at 9:38 PM, Isaac Bennetch <bennetch@gmail.com <mailto:bennetch@gmail.com>> wrote:
Hi,
On 3/1/17 3:00 AM, Manish Bisht wrote: > Hi, > > I have on suggestion. Can someone from the core team can create the > slack channel for phpmyadmin. It's the better place to communicate with > other Developers compared to IRC.
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
> Thanks, > > Manish Bisht > hi@manishbisht.me <mailto:hi@manishbisht.me> <mailto:hi@manishbisht.me <mailto:hi@manishbisht.me>> > https://manishbisht.me > > > _______________________________________________ > Developers mailing list > Developers@phpmyadmin.net <mailto:Developers@phpmyadmin.net> > https://lists.phpmyadmin.net/mailman/listinfo/developers <https://lists.phpmyadmin.net/mailman/listinfo/developers> >
_______________________________________________ Developers mailing list Developers@phpmyadmin.net <mailto:Developers@phpmyadmin.net> https://lists.phpmyadmin.net/mailman/listinfo/developers <https://lists.phpmyadmin.net/mailman/listinfo/developers>
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
_______________________________________________ Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
participants (6)
-
Guillermo Salazar -
Hemant Singh -
Isaac Bennetch -
Manish Bisht -
Maurício Meneghini Fauth -
Michal Čihař