Re: [Distutils] Switch PyPA from IRC to Gitter or similar

On Fri, 10 Jun 2016 at 07:25 Ian Cordasco wrote: > On Fri, Jun 10, 2016 at 8:22 AM, Jason R. Coombs > wrote: > > In #pypa-dev, I raised the possibility of moving our PyPA support > channels from IRC to another hosted solution that enables

Re: [Distutils] Switch PyPA from IRC to Gitter or similar

On Fri, Jun 10, 2016 at 2:53 PM, Glyph wrote: > There might be a useful discussion buried in here about where official > real-time _development_ discussion should go - but then, any weighty > decisions should be discussed on the mailing list anyway to ensure that >

Re: [Distutils] Switch PyPA from IRC to Gitter or similar

On Fri, Jun 10, 2016 at 4:58 PM, Glyph wrote: > > On Jun 10, 2016, at 1:42 PM, Robert Collins > wrote: > > FWIW, I won't be switching to gitter or slack - I find the push > notifications and always-on experience exhausting. It gets in the way >

Re: [Distutils] Switch PyPA from IRC to Gitter or similar

> On Jun 10, 2016, at 1:42 PM, Robert Collins wrote: > > FWIW, I won't be switching to gitter or slack - I find the push > notifications and always-on experience exhausting. It gets in the way > of thinking or doing anything useful. I often leave my phone in >

Re: [Distutils] Switch PyPA from IRC to Gitter or similar

> On Jun 10, 2016, at 6:22 AM, Jason R. Coombs wrote: > > In #pypa-dev, I raised the possibility of moving our PyPA support channels > from IRC to another hosted solution that enables persistence. Opinions about free software vs. federation vs. user experience aside, I

Re: [Distutils] Switch PyPA from IRC to Gitter or similar

On 11 June 2016 at 01:22, Jason R. Coombs wrote: > In #pypa-dev, I raised the possibility of moving our PyPA support channels > from IRC to another hosted solution that enables persistence. Although IRC > has served us well, there are systems now with clear feature

Re: [Distutils] Switch PyPA from IRC to Gitter or similar

On Fri, Jun 10, 2016 at 12:54 PM, Nathaniel Smith wrote: > On Jun 10, 2016 07:25, "Ian Cordasco" wrote: >> > [...] >> I've tried using Gitter several times in the past. Unless they've >> fixed their bugs related to sending me emails every day about

Re: [Distutils] Switch PyPA from IRC to Gitter or similar

Chef is in the process of navigating an IRC->Slack migration. https://github.com/chef/chef-rfc/blob/master/rfc074-community-slack.md is the document I wrote up on the pros and cons of various options. Gitter has a better UX for new users compared to Slack because it was built to be for public

Re: [Distutils] Switch PyPA from IRC to Gitter or similar

On Jun 10, 2016 07:25, "Ian Cordasco" wrote: > [...] > I've tried using Gitter several times in the past. Unless they've > fixed their bugs related to sending me emails every day about activity > in a channel I spoke in once and left, I think they should be >

Re: [Distutils] Switch PyPA from IRC to Gitter or similar

On Fri, 10 Jun 2016, Jason R. Coombs wrote: Personally, the downsides to moving to Gitter (other than enacting the move itself) seem negligible. What do you think? What downsides am I missing? That may be the main issue. Given the responses thus far, it seems like most people are happy with

Re: [Distutils] Switch PyPA from IRC to Gitter or similar

On Fri, Jun 10, 2016 at 10:24 AM, Ian Cordasco wrote: > So here's a question: Why are these crucial to you? You've explained > potential benefits but not why they're crucial to you and should be > crucial to anyone else. For people who want an always-on presence,

Re: [Distutils] Switch PyPA from IRC to Gitter or similar

On Fri, Jun 10, 2016 at 8:22 AM, Jason R. Coombs wrote: > In #pypa-dev, I raised the possibility of moving our PyPA support channels > from IRC to another hosted solution that enables persistence. Although IRC > has served us well, there are systems now with clear feature

Re: [Distutils] Switch PyPA from IRC to Gitter or similar

Other than the fact that we now would need to redirect the 2000 (at any given time) users of #python, and 200 (roughly) users of #pypa to an inherently commercial, and frankly, hard to discover service? It's tantamount to discontinuing chat support, which if that’s what you want to do, so be