Archiving the docs@python.org mailing list in favour of Discourse/GH issues?

Documentation
1

Should we archive the docs@python.org mailing list? This list was used for bug reports for the last few years, however, all mentions of it have now been removed from the docs and replaced with links to GH/this Discourse category (see commits Remove reference to docs mailing list for bug reports (#122323) · python/cpython@33586d6 · GitHub, Add lightweight comments to conf.py and update docs readme (GH-126100) · python/cpython@9effa0f · GitHub, and gh-138843: Clean up downloads page (#138844) · python/cpython@d9cb191 · GitHub a few days ago which removed the final instance).

It did have several mails in the last few months, primarily about issues with the downloaded documentation, but no substantive discussions. In general, most reports never got a reply.

Prior art: Archive python-ideas mailing list in favour of Discourse?, Archiving the translation mailing list in favour of Discourse

1 Like
2

Not all of them, see Dealing with Bugs — Python 3.10.19 documentation

I’d say keep it for a few more years, it should stops getting new posts organically.
Also, before archiving let’s copy recent unanswersed reports to GH issues.

3

I would support dropping the mailing list eventually.

Does it mean once Python 3.10 no longer supported (October 2026), we can retire the mailing list?

In that case, perhaps starting now we can begin making announcements that this list is pending deprecation.

4

Could an exception be made to backport the removal to the security branches?

5

3.12 (2028), if #140202 is merged. Hopefully we’ll get close to no reports by then.

If you think it’s necessary, you can ask the RM. But I don’t see the need to remove the list soon.

1 Like