I am a new community member and extremely eager to contribute. I am just adding my two cents here. Apart from the core-mentorship list, I have not found any other list useful. Discourse is impactful and has a quite low turnaround time. I have been answering questions in the forum and from what I can tell, people find it easy to post formatted code snippets and other media. Regards, Abdullah LinkedIn <https://www.linkedin.com/in/abdnafees/>. On Wed, Dec 7, 2022 at 4:04 PM Petr Viktorin <encukou@gmail.com> wrote:
On 06. 12. 22 11:16, Baptiste Carvello wrote:
Hi,
Le 05/12/2022 à 14:50, Stephen J. Turnbull a écrit :
I'd be sad, but I get the feeling that the only people left reading it are "here for the community", not to develop code, …
I think this is indeed true, but that's nothing to be sad about: "being here for the community" is not wrong or shameful.
Since forever, python-dev has attracted a large following of enthusiast Python users, who want to understand the design choices of their preferred language. This widely shared concern for writing idiomatic code is a distinguishing trait of the Python community (the whole culture of "pythonic" code).
Now maybe this is a place where the mailman devs could help and make a real difference: what if this list would become, not archive-only, but a *read-only mirror* of those parts of Discourse that are relevant for core development? That would mean setting up a pipeline starting with Discourse's so-called "mailing-list mode", going through the kind of filter stack that some core developers have been setting up for their personal use, and feeding into this mailing list. The last part can only be done with the powers of the mailman admins.
Being read-only would not be a problem in practice: non core-devs here read much more than they post (as they should). Being forced to log into a specific website is an acceptable roadblock once in a while for posting, just not every day for simply following the discussions.
Turning this list into a relevant mirror of Discourse is the nicest course of action for the hundreds of silent readers python-dev has gathered over the years. All those people *won't* switch to routinely visiting the Discourse website, no matter how much pushing and wishful thinking the Steering Council puts into it.
I'd like to point out that the SC decision was *reactive*, after most discussions moved to Discourse without SC pushing.
I liked the list myself! But as soon as most of the posts were mandatory PEP and release notices, it stopped being useful.
Shutting down the list means kicking them away, more or less overtly.
Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@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/XRNL7OJP... Code of Conduct: http://python.org/psf/codeofconduct/