Documentation Community Team Meeting (October 6, 2026)

Roll call

(Name / @GitHubUsername [/ Discord, if different])

  • Ned Batchelder / @nedbat

  • Ryan Duve / @ryan-duve

  • Velda Kiara / @veldakiara

  • Bhuvansh / @BHUVANSH855

  • Keith / @KeithTheEE

Introductions

New attendees were present, and a round of introductions was made.

Reports and celebrations

  • Python 3.15 is nearly here, and it’s awesome. The frequent releases, upgrade pipeline, and issue management gave us the grace to pause the schedule a touch and validate that the improvements really are improvements for as much of the Python userbase as possible.

Discussion

  • [Bhuvansh] On behalf of our project team, I want to discuss the python-docs-pa project, the Punjabi (India) translation of the Python Documentation. The project is complete according to the core requirements, and we would like to discuss the next steps for getting the translation included in the official Python Documentation. The project has also been approved by Maciek and is now waiting for a core developer to take this forward.

    • [Ryan] I had spoken to Bhuvansh over last month about this and he’s interested in getting this addressed on today’s call. Unstable internet service may affect ability to join by video/voice.

  • [Keith] Pulling from the prior meeting, it’d be nice to cover the process of how to review a PR.

    • [Velda] Are there priority issues, how do you look for something to work on.

      • [Ryan] One way is to look based on activity, if something hasn’t been looked at too often I can ask a clarifying question to move it along

      • [Ned] Three Day Issues: a personal project to help track GitHub items with recent activity.

      • Documentation issues on GitHub.

      • [Ned] With the new eyes you bring, you can point out what confuses you in the guide itself and in related material you come across, which highlights what needs improving.

      • The Docs Community repository was found by a Google search and by searching the Python organisation on GitHub. Could there be a way to add a thing that links to the devguide to direct to a common source of truth. Github lets an organisation create a custom README, the python GitHub organisation does not have one currently.

  • [Velda] Are there interesting issues you’ve reviewed before, so I can read through the comments on a review?

    • [Ryan] Looking at issues. Start by going to issues, then look at label:docs.

      • One thing for me: I don’t know what to respond to, so I often look at issues that don’t have a ton of comments on them.

      • Starting on issue #158681 as an example, I read through it.

      • Then after reading it, I’ll often look at the user’s account. If they’re very new user, I’ll add a welcome comment. If they’re a core team member, it’s possible I’ll not know as much so I might not be able to offer helpful suggestions to their PR/Issue. This helps me select an issue/PR to focus on.

      • Moving on to the Pull Request: I look to see if it is a documentation change. I see if it’s correct, and if it’s helpful. I like to ask leading questions which, if it has an answer, will help increase the chance that the PR is going to be merged.

      • Sometimes if there’s a concern about the person’s interest in the issue, I’ll immediately ask a question. This helps gauge their interest in actually improving their PR.

      • GitHub Views: might help add filters so you can filter for issues/PRs which have specifics you’re interested in, be it issues not submitted by core team, PRs with a keyword, etc.