I think this is a great change, one I've been looking forward to myself. For authors of PEPs and discussion topics, Discourse provides better authoring experience, allowing for typo fixes and small edits. For moderators, Discourse also provides the toolings to make their jobs easier, which is definitely lacking in mailing list. For the readers, we get the choice of receiving emails via mailing list mode, or via rss, or by actually going to the site.
I think it's great that you've considered what's best for the different types of users here. So thank you Petr and SC for this decision. On Fri, Jul 15, 2022 at 4:26 AM Petr Viktorin <encu...@gmail.com> wrote: > Hello, > Currently development discussions are split between multiple > communication channels, for example: > - python-dev and discuss.python.org for design discussions, > - GitHub Issues and Pull Requests for specific changes, > - IRC, Discord and private chats for real-time discussions, > - Topic-specific channels like typing-sig. > > While most of these serve different needs, there is too much overlap > between python-dev and discuss.python.org. It seems that for most > people, this situation is worse than sticking to either one platform – > even if we don't go with that person's favorite. > > 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. > Practically, this means: > - Moving the required PEP announcements to discuss.python.org > - Moving discuss.python.org up in the devguide communications page > (https://devguide.python.org/communication/) > - And that's it? > > I imagine that the mailing list will stay around for continuing past > discussion threads and for announcements, eventually switching to > auto-reject incoming messages with a pointer to discuss.python.org. > > To be clear, discuss.python.org allows editing posts, which is frankly > handy for typos and clarifications. Editing alone should not be used for > adding new info -- we should cultivate a culture of being friendly to > mail users & notification watchers. This probably bears repeating in a > few places. > > We're aware not everyone wants to use the discuss.python.org website, > but there are some ways to avoid it: > > - For new PEPs, you can point your RSS client to > https://www.python.org/dev/peps/peps.rss – it's not e-mail, but many > email clients have RSS support. You can also watch the Steering Council > issues on GitHub (https://github.com/python/steering-council/issues/) > for important questions and discussions. > > - You can use discuss.python.org's “mailing list mode” (which subscribes > you to all new posts), possibly with filtering and/or categorizing > messages locally. > > However, we would like to know if this will pose an undue burden to > anyone, if there are workflows or usage problems that we are not aware > of. As mentioned, this is something the Steering Council thinks is a > good idea, but we want to make sure we're aware of all the impact when > we make the final decision. > > > > – Petr, on behalf of the Steering Council > _______________________________________________ > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/VHFLDK43DSSLHACT67X4QA3UZU73WYYJ/ > Code of Conduct: http://python.org/psf/codeofconduct/ >
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/RFH25FOFAVYN6WB7RYW3APCVCLAVDHK5/ Code of Conduct: http://python.org/psf/codeofconduct/
