|
| 1 | +# Documentation Community Team Meeting (October 6, 2026) |
| 2 | + |
| 3 | +## Roll call |
| 4 | + |
| 5 | +(Name / `@GitHubUsername` *[/ Discord, if different]*) |
| 6 | + |
| 7 | +- Ned Batchelder / `@nedbat` |
| 8 | +- Ryan Duve / `@ryan-duve` |
| 9 | +- Velda Kiara / `@veldakiara` |
| 10 | +- Bhuvansh / `@BHUVANSH855` |
| 11 | +- Keith / `@KeithTheEE` |
| 12 | + |
| 13 | +## Introductions |
| 14 | + |
| 15 | +New attendees were present, and a round of introductions was made. |
| 16 | + |
| 17 | +## Reports and celebrations |
| 18 | + |
| 19 | +- [Python 3.15](https://docs.python.org/3.15/) is nearly here, and it's awesome. |
| 20 | + The frequent releases, upgrade pipeline, and issue management gave us the grace |
| 21 | + to pause the schedule a touch and validate that the improvements really are |
| 22 | + improvements for as much of the Python userbase as possible. |
| 23 | + |
| 24 | +## Discussion |
| 25 | + |
| 26 | +- [Bhuvansh] On behalf of our project team, I want to discuss |
| 27 | + the [python-docs-pa](https://github.com/BHUVANSH855/python-docs-pa) project, |
| 28 | + the Punjabi (India) translation of the Python Documentation. The project is |
| 29 | + complete according to the core requirements, and we would like to discuss the |
| 30 | + next steps for getting the translation included in the official Python |
| 31 | + Documentation. The project has also been approved by Maciek and is now waiting |
| 32 | + for a core developer to take this forward. |
| 33 | + - [Ryan] I had spoken to Bhuvansh over last month about this and he's |
| 34 | + interested in getting this addressed on today's call. Unstable internet |
| 35 | + service may affect ability to join by video/voice. |
| 36 | + |
| 37 | +- [Keith] Pulling from the prior meeting, it'd be nice to cover the process of |
| 38 | + how to review a PR. |
| 39 | + - [Velda] Are there priority issues, how do you look for something to work on. |
| 40 | + - [Ryan] One way is to look based on activity, if something hasn't been |
| 41 | + looked at too often I can ask a clarifying question to move it along |
| 42 | + - [Ned] [Three Day Issues](https://nedbat.github.io/nedbat_dinghy/3day-docs.html): |
| 43 | + a personal project to help track GitHub items with recent activity. |
| 44 | + - [Documentation issues on GitHub.](https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+label%3Adocs) |
| 45 | + - [Ned] With the new eyes you bring, you can point out what confuses you in |
| 46 | + the guide itself and in related material you come across, which highlights |
| 47 | + what needs improving. |
| 48 | + - The [Docs Community](https://github.com/python/docs-community) repository |
| 49 | + was found by a Google search and by searching the Python organisation on |
| 50 | + GitHub. Could there be a way to add a thing that links to the devguide to |
| 51 | + direct to a common source of truth. Github lets an organisation create a |
| 52 | + custom README, the `python` GitHub organisation does not have one |
| 53 | + currently. |
| 54 | + |
| 55 | +- [Velda] Are there interesting issues you've reviewed before, so I can read |
| 56 | + through the comments on a review? |
| 57 | + - [Ryan] Looking at issues. Start by going to issues, then look at |
| 58 | + [`label:docs`](https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+label%3Adocs). |
| 59 | + - One thing for me: I don't know what to respond to, so I often look at issues |
| 60 | + that don't have a ton of comments on them. |
| 61 | + - Starting on issue [#158681](https://github.com/python/cpython/issues/158681) |
| 62 | + as an example, I read through it. |
| 63 | + - Then after reading it, I'll often look at the user's account. If they're |
| 64 | + very new user, I'll add a welcome comment. If they're a core team member, |
| 65 | + it's possible I'll not know as much so I might not be able to offer helpful |
| 66 | + suggestions to their PR/Issue. This helps me select an issue/PR to focus on. |
| 67 | + - Moving on to the Pull Request: I look to see if it is a documentation |
| 68 | + change. I see if it's correct, and if it's helpful. I like to ask leading |
| 69 | + questions which, if it has an answer, will help increase the chance that the |
| 70 | + PR is going to be merged. |
| 71 | + - Sometimes if there's a concern about the person's interest in the issue, |
| 72 | + I'll immediately ask a question. This helps gauge their interest in actually |
| 73 | + improving their PR. |
| 74 | + - GitHub Views: might help add filters so you can filter for issues/PRs which |
| 75 | + have specifics you're interested in, be it issues not submitted by core |
| 76 | + team, PRs with a keyword, etc. |
0 commit comments