[Overload-sig] Issue tracker vs. real-time chat

[Guido van Rossum]

(We accidentally started this discussion on private email. I assume noone
has a problem with me reposting this to the sig.)

I'd like to put in a vote *for* systems or paradigms that behave more or
less like issue trackers (AFAIC even Reddit and StackOverflow fall in this
pattern) and *against* group chat systems (IRC, HipChat, Zulip, Slack,
Skype, Hangouts).

To be sure, I'm fine with the existence of chat systems, but I find
participating in them exhausting, and they tend to have a very high noise
level. They exacerbate the problem that only those who can keep up with the
traffic know what's been discussed already (scrollback features in Slack
etc. notwithstanding). Usually the mute control is too course. AFAIK only
Zulip supports any kind of "topic" selection (Slack is based on group
membership, and groups are relatively static, even though membership is
dynamic).

QUOTE from Kevin:

I think we should definitely be seeing what we can do to improve the
mailing list experience. :) I've not worked with Mailman 3 myself yet but
it sounds like 3.0 is a pretty significant improvement. I was pretty
curious about Posterious particularly, although I didn't manage to find an
example of it online. Is there a good example to look at?

In addition to that, I think we should also be looking at improvements for
our bug trackers and chat software as part of this. Playing with GitHub's
bug tracker may be a good start, and maybe something like Slack or Zulip
for chat would be a nice improvement. I've gotten spoiled by the ability in
Slack to see the conversations that happened while I was offline. I know
Zulip, like Posterious, is a Django-based app, and it would be cool to have
more of our infrastructure built on top of Python so long as it doesn't
become a maintenance burden. Maybe the Zulip team would even be willing to
help out?

-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/overload-sig/attachments/20160621/9d8429d7/attachment.html>