As I mentioned on python-committers and mirrored here, during the core sprint in Redmond we decided to try out Discourse in earnest due to many problems that we face with mailing lists.
python-committers
I felt like inviting members of python-committers to dive deep and test it out until the end of the year provides both the test volume we need, as well as is great timing (since an elevated volume of discussion will happen due to the governance situation). Most people seem to agree with this as the list of committers here is already 54 strong. So expect much of the discussion that would go to python-committers to actually go here now.
Note that there are a few core developers who reject the Discourse idea, or at least the style in which I communicated it. By their absence here I assume they will stick to using python-committers.
Other mailing lists
Anybody can sign up on Discourse today but I would like the initial test to be done by core developers to make sure the platform fits our needs. In the original announcement I planned for the month of October to be that initial period of identifying any deal breakers.
I thought of inviting python-dev subscribers to move in November, and python-list and -ideas in December.
For python-dev specifically, I did not create a category for that as many of the active core developers are upset with how it turned out (20+ thousand subscribers with drive-by comments, hard to figure out who is who, confused users asking for Python usage help). Discussions that non-committers open on python-dev today would simply happen in Users. If we start seeing too much volume in that bucket, we can create sub-categories, “Open PEP Discussion” being a likely one we’ll want.