Leaving python-dev behind
It was not all that long ago that Python began its experiment with replacing one of its mailing lists with a forum on its Discourse discussion site. Over time, the Discourse instance has become more and more popular within the Python community. It would seem that another mailing list will soon be subsumed within Discourse as the Python steering council is planning to effectively retire the venerable python-dev mailing list soon.
History
Back in 2018, both Fedora and Python were experimenting with Discourse instances; both
are quite active at this point.
Discourse is an open-source web
forum project that says it aims to "reimagine what a modern Internet
discussion forum should be today, in a world of ubiquitous smartphones,
tablets, Facebook, and Twitter
". But Fedora and Python currently
still have mailing lists
as well.
As part of the experiment for Python, the core-developer-only python-committers mailing list was switched to Discourse for a few months as a test. That was during the upheaval in the Python world that stemmed from Guido van Rossum's resignation as its benevolent dictator for life. The announcement of the experiment was deemed a bit of an overreach at the time, but the discussion of the new governance model for the language did largely happen in the Committers forum on Discourse.
These days, the python-committers list still exists, but it mostly receives announcements and the like; some discussions still take place there, but most, it would seem, are done on the Discourse site. There are plenty of other forums on that site, including two that overlap the main mailing lists where development discussions take place. The Core Development forum overlaps the function of the python-dev mailing list, while the Ideas forum serves the same purpose as the python-ideas mailing list.
Up until recently, there was no real indication that changes might be in
the works, but an April query
about PEP discussion that was posted to python-dev by Victor Stinner may have
been the first real public indication that changes were afoot. He asked
that new PEPs be announced on python-dev since he did not go to Discourse
often and several PEPs of interest had slipped by without notice because
they failed to be posted there. He also noted
that it is "sometimes hard to keep track of everything happening around
Python development
" in part because of all of the different ways the
project's developers communicate:
The discussions are scattered between multiple communication channels:Sometimes, I [am] already confused by the same topic being discussed in two different Discord rooms :-) It's also common that some people discuss on the issue, and other people have a parallel discussion (about the same topic) on the related pull request.
- Issues
- Pull requests
- python-dev
- python-committers
- (private) Discord
- Discourse
- (public) IRC #python-dev
He noted that there are some in-person events, too, that make it even harder
to keep up for those who cannot attend. Petr Viktorin replied
that PEPs should be posted to python-dev, "but not necessarily
right after they're published
". They may be discussed elsewhere
before coming to python-dev, for example.
The intent, Viktorin said,
is that PEPs should only be submitted to the steering council, of
which he is a member, "after
all relevant discussion took place
", which includes python-dev.
Choosing one
Jean Abou Samra noted that the split in the location for discussions is
confusing to him, so he asked
about any plans "to retire either Discourse or the mailing list and use a
unified communication channel
". Gregory P. Smith, who is also a
steering council
member, replied:
We feel it too. We've been finding Discourse more useful from a community moderation and thread management point of view as well as offering markdown text and code rendering. Ideal for PEP discussions. Many of us expect python-dev to wind up obsoleted by Discourse as a result.
That led to some predictable grumbling about Discourse and the problems with following a web-based forum in comparison to a mailing list. That divide comes up whenever changes of this sort are announced or discussed, but newer developers generally seem to be uninterested in learning the "joys" of participating on mailing lists. In part, that is because the relevance of email as a communication mechanism has fallen almost completely off the radar for many. But the writing seems to be on the wall—for Python at least. As Christopher Barker put it:
But if Discourse has been adopted, I guess it's time for us curmudgeons to bite the bullet and start monitoring it -- and frankly, this list (and python-ideas) should probably be retired, or turned into an announcement-only list -- having the current split is the worst option of all.
For discussions on the development of CPython, the python-dev mailing list has been the place to go for two decades or more. The mailing list page has archives going back to April 1999. In fact, one of the earliest messages archived is from Van Rossum asking whether the python-dev archives should be public or private. Obviously, "public" was the decision.
On July 15, Viktorin posted a message that would seem to be bringing that history to a close. On behalf of the council, he said:
The discuss.python.org experiment has been going on for quite a while, and while the platform is not without its issues, we consider it a success. The Core Development category is busier than python-dev. According to staff, discuss.python.org is much easier to moderate.. If you're following python-dev but not discuss.python.org, you're missing out.The Steering Council would like to switch from python-dev to discuss.python.org.
His message recognized that not everyone finds the Discourse forum software
running at discuss.python.org to be easy to follow and use either; it
contained several suggestions for alternate ways to interact with it, including
"mailing-list mode". The message was also soliciting feedback on whether a
permanent switch would "pose an undue burden to anyone
". A final
decision on the switch had not been made, so the council wants to ensure that it
is "aware of all the impact
".
No one has really raised any concrete problems of that nature, though Barry
Warsaw mentioned
the possibility of "accessibility or native language concerns
" for
Discourse. He also noted that he supports moving to Discourse, which
"might seem odd coming from me
"; Warsaw is one of the lead developers of the
GNU Mailman mailing-list
manager system and was a big part of the Mailman 3 effort. "Discourse is not without its issues, but then again, the same can be
said about email.
"
While there were posts with the usual negative opinions of web forums versus email, they were fairly muted. To an extent, it would seem that there is a generational change going on in the Python community; the older developers are either adapting, perhaps via mailing-list mode, or kind of just bowing out. For those looking for more information, mailing-list mode is briefly mentioned in the "Following Python's Development" section of the Python Developer's Guide. But mailing-list mode is not able to disguise one problem that Discourse discussions have: no threading. Ethan Furman said:
I follow each (sub)thread through to it's end, as it keeps a logical flow, but Discourse has everything linear which means that as I read it the conversation keeps jumping around, making it hard to follow.
Warsaw agreed that the lack of threading is problematic, but that feature has fallen by the wayside in today's discussions:
[...] I definitely prefer threaded discussions. Unfortunately though, much like top posting <wink>, I think that horse is out of the barn, what with other forums like GitHub being linear.
As might be guessed, based on the "wink", Warsaw had top-posted his reply. Viktorin noted that he has just had to accept the linear nature of Discourse discussions; things have changed and there is likely no going back:
[...] if python-dev was used by everyone, rather than almost exclusively by people who prefer e-mail (and presumably use threading mail clients), we'd get mangled threading anyway from all the non-threaded clients.I mean, I could grumble about threading and bottom-posting and plain-text messages and IRC all day, but realistically, I'm not likely to convince anyone who's not into those things already.
That's where things stand at this point. It seems likely that a final
decision to switch away from python-dev will be coming soon and that the
venerable mailing list will be reconfigured sometime thereafter, "eventually switching to
auto-reject incoming messages with a pointer to discuss.python.org
".
That will be a sad day for some—and effectively a non-event for (many?)
others. For those of us who cut our teeth on threaded, text-only,
bottom-posted discussions, it is completely mind-boggling that Kids These
Days (tm) do not see the advantages of such ... discourse—but that
seems to be
the way of things.
| Index entries for this article | |
|---|---|
| Python | Development model |
