I moderate a few of the Python mailing lists. After the deployment of Mailman 3.0, we've only migrated 6 lists to 3.0: see https://mail.python.org/mailman3/lists/ for the list.
Admittedly those are some of the more important and active lists like python-dev, Distutils-SIG, and core-workflow. But we should continue the process of moving lists; compare the very long list in MM 2.0 at https://mail.python.org/mailman/listinfo/ .
(This was sparked by getting re-subscribed to psf-announce today, …
[View More]and noticing that it's still on MM2.)
Many of these lists are for local user groups, and we should probably let them know before changing anything, so let's set them aside for now. The PSF can migrate its own lists when staff is comfortable with that, e.g. psf-* and some of the pycon-* lists. What's the process for doing this?
While we're at it, we could also remove inactive SIGs, e.g. compiler-sig, python-legal-sig, etc. and just leave the archives up.
--amk
[View Less]
