The Python Docs Editorial Board meets once a month and for transparency and accountability, we publish our meeting notes publicly.
If you have items for discussion by the Editorial Board, please open an issue in our GitHub Repo, we will discuss them in the next meeting. Our November meeting is scheduled on Nov 11, 2025.
I will also add that an archive of Docs community monthly meeting minutes can be found on the website, anyone can participate in the meetings, if you would like to do so more information can be found in this guide!
Thanks @Stanfromireland for the reminders. There’s a lot of great work happening this year in documentation and translation. 
On the wiki topic… you get access to edit by mailing to pydotorg-www - there’s more than MAL that can add editors, though he’s very responsive 
The gate for becoming an editor is not onerous - just say you’d like to edit (it’s just to keep out bots).
The difficulty with maintaining the wiki is there’s lots of pages in it, who gets to make the call that something is outdated and should be removed or reworded? Should there be any kind of review for changes? (some of us watch the change notifications but really only to be able to fix up egregious errors or naughties like reordering the list of books so yours gets top slot and competitors are hard to see). So it’s a community itch-scratching approach, mainly - if it bugs you and you want to add/fix, go ahead. That was supposed to be the power of wikis, but there hasn’t been that much editing for a long time, and I think all of them are suffering even more these days - there was just some news at how badly Wikipedia traffic has fallen off because people just ask AI. Any major revamp efforts should probably take that into account - will the work actually have a worthwhile payoff?