On Saturday, April 21, 2018, James Bennett <ubernostrum@gmail.com> wrote:
Pulling in a sort-of success story from another large project, I like the general way things happen in Django.

For developers proposing an idea or fixing a bug:

* There's IRC (#django-dev) for quick, synchronous-ish discussion, useful for someone to find a sounding board for an idea

#pypa (Freenode manages these)
* There's a dev mailing list where proposals can be discussed a bit more formally

https://mail.python.org/mailman/listinfo/distutils-sig (still not sure who volunteered to manage these)

https://groups.google.com/forum/m/#!forum/pypa-dev (or this)
* There's the public ticket tracker as a place to follow work being done




And for users seeking help or general discussion:

* There's IRC (#django) and a users mailing list

  label: Question

* There's an official-ish subreddit moderated by committers
* And there's the rest of the internet, including Stack Overflow, which we can't moderate but which many experienced people in the community do pay attention to


Thanks to the people who host and handle these questions.

We've avoided using GitHub issues for Django, preferring the workflow tools we get from our own customized Trac instance.

I wonder whether something similar -- a real-time chat for discussion/sounding board/etc., mailing list to bring things to once they've been thought about a bit, public tracker for following work/archival purposes -- would work for packaging.

Should there, in addition to #pypa IRC and gitter, be a zulip topic (?) for pypa?

AFAIU, Zulip started at Dropbox, is written in Python, supports boots, and is functionally similar to Slack, Gitter, and MatterMost?

(I am also wary of too much "process"; Django has a fair bit, and more than I'd ideally like, but my experience has been that process and participation are generally inversely correlated)

Better yet, fork and send a pull request (PR)?