On Tue, Feb 12, 2019 at 10:59 PM Antoine Pitrou <anto...@python.org> wrote:
> > Le 11/02/2019 à 20:00, Barry Warsaw a écrit : > > On Feb 11, 2019, at 09:48, Victor Stinner <vstin...@redhat.com> wrote: > >> > >> tl; dr How can we decide if we should stop using mailing list or if we > >> should stop using discuss.python.org? > > > > Point of order: I think we need a PEP for this decision. Such a PEP > would organize and consolidate the arguments both pro and con of the three > choices. It should also cover whether the current Discourse experiment > translates to larger mailing lists like python-dev, -ideas, and -list (for > which I personally have uncertainty about). > > Same uncertainty here. I don't think Discourse works well for long > threads. > > Here is a 161-message Discourse thread (at the time of this writing): > https://discuss.python.org/t/pep-517-backend-bootstrapping/789 > > I know I can browse easily through a 161-message mailing-list or > newsgroup thread using a traditional threaded view, read what I want, > come back later to read the rest, etc. But Discourse's linear > presentation pretty much kills that ability. It doesn't even allow > *seeing* the structure of the discussion. > What bothers me about medium/long threads (say > 20 messages) is an "expand all" button, showing the full conversation (upon which I may then want to use CTRL+F). The only way to do that is by scrolling the page all the way up or down, and in a long discussion like that one it takes a long time. If you start at the middle of the discussion, say here: https://discuss.python.org/t/pep-517-backend-bootstrapping/789/80 ...you have to do both (scroll up, reach the top, scroll down, reach the bottom - only then you'll have the full thread). -- Giampaolo - http://grodola.blogspot.com
_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
