On Sat, Mar 31, 2018, 02:42 Antoine Pitrou, <solip...@pitrou.net> wrote:

> On Fri, 30 Mar 2018 16:25:34 +0000
> Brett Cannon <br...@python.org> wrote:
> >
> > Consider the fact that a standard answer to a lack of email threading on
> > any of the major email providers is to use gmane's NNTP gateway.
>
> The main problem with gmane is that it isn't really maintained
> anymore.  In particular you can't register new mailing-lists to the
> gateway :-(
>
> > I don't think people realize that anyone who post-dates the '90s has no
> clue what
> > that acronym represents and thus poses the same barriers as setting up
> IRC.
>
> I'm curious about "barriers".  You just have to set up a piece of
> software...  Python requires some kind of text editor or IDE to become
> productive.  Is it a barrier to have to set up a text editor?
>

I don't want to dwell on this too much since I think we've collectively
agreed to focus on the real-time collaboration case. But to answer the
question, any piece of software we basically ask people to set up to be
productive is a barrier. In North America there's is the phrase "death by a
thousand paper cuts" and asking people to install yet more software and do
more to get set up does have a cost where people have a personal limit how
how many little things they are willing to put up with.

As for this specific case, as a developer there is a much greater chance I
will install an editor for all of my development needs while installing an
email client has a higher chance tonne just for this specific case if
people in school these days aren't heavy email users.

-Brett


> > So for me, the first question is are we just considering alternatives to
> > the "IRC problem" or are we trying to solve the "new contributors who
> were
> > born in the 2000s problem" (for which the latter subsumes the former)?
>
> Well... I think the main question is whether IRC is important at all.
> I'd be willing to guess that most of our contributors don't use IRC on
> a regular basis, and they're not missing on anything.


Missing out? No. Would like to occasionally have real-time collaboration?
Yes, at least for me (I mean I could give every core dev my number toessage
me on Signal or WhatsApp, but I don't think that scales 😉).

Which isn't a
> reason not to improve things, but makes it quite low-priority IMHO.
>

Yes, this isn't critical, hence why I don't think anyone has tried to do
anything beyond discussing it so far. We will have to wait and see if
anyone writes up a proposal as to why we should consider the overhead of
asking people to sign up for Zulip and give it a try.

-Brett


> Regards
>
> Antoine.
>
> _______________________________________________
> core-workflow mailing list -- core-workflow@python.org
> To unsubscribe send an email to core-workflow-le...@python.org
> https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>
_______________________________________________
core-workflow mailing list -- core-workflow@python.org
To unsubscribe send an email to core-workflow-le...@python.org
https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/
This list is governed by the PSF Code of Conduct: 
https://www.python.org/psf/codeofconduct

Reply via email to