|
| 1 | +# Documentation Community Team Meeting (May 2024) |
| 2 | + |
| 3 | +- **Date:** 2024-05-07 |
| 4 | +- **Time:** [19:00 UTC](https://arewemeetingyet.com/UTC/2024-05-07/19:00/Docs%20Meeting) |
| 5 | +- **This HackMD:** https://hackmd.io/@encukou/pydocswg1 |
| 6 | +- [**Discourse thread**](https://discuss.python.org/t/documentation-community-meeting-tuesday-7th-may-2024/52404) (for May) |
| 7 | +- [**Meeting reports**](https://docs-community.readthedocs.io/en/latest/monthly-meeting/) (the latest one might be an [**unmerged PR**](https://github.com/python/docs-community/pulls)) |
| 8 | +- **Calendar event:** (send your e-mail to Mariatta for an invitation) |
| 9 | +- **How to participate:** |
| 10 | + - Go to [Google Meet](https://meet.google.com/dii-qrzf-wkw) and ask to be let in. |
| 11 | + - To edit notes, click the “pencil” or “split view” button on the [HackMD document](https://hackmd.io/@encukou/pydocswg1). You need to log in (e.g. with a GitHub account). |
| 12 | + |
| 13 | +By participating in this meeting, you are agreeing to abide by and uphold the [PSF Code of Conduct](https://www.python.org/psf/codeofconduct/). |
| 14 | +Please take a second to read through it! |
| 15 | + |
| 16 | + |
| 17 | +## Roll call |
| 18 | + |
| 19 | +(Name / `@GitHubUsername` *[/ Discord, if different]*) |
| 20 | + |
| 21 | +- Ned Batchelder / `@nedbat` |
| 22 | +- Petr Viktorin / `@encukou` |
| 23 | +- Ryan Duve / `@ryan-duve` |
| 24 | +- Eric |
| 25 | +- Hugo van Kemenade / `@hugovk` |
| 26 | +- CAM / `@CAM-Gerlach` |
| 27 | +- Erlend Aasland / `@erlend-aasland` |
| 28 | + |
| 29 | + |
| 30 | +## Introductions |
| 31 | + |
| 32 | + |
| 33 | +## Reports and celebrations |
| 34 | + |
| 35 | +> 60 second updates on things you have been up to, questions you have, or developments you think people should know about. Please add yourself, and if you do not have an update to share, you can pass. |
| 36 | +
|
| 37 | +> This is a place to make announcements (without a need for discussion). This is also a great place to give shout-outs to contributors! We'll read through these at the beginning of the meeting. |
| 38 | +
|
| 39 | +- Python 3.13 beta happening. |
| 40 | + - Announced in [discuss.python.org](https://discuss.python.org/t/python-3-13-0-beta-1-is-near/52794) |
| 41 | + - [Calendar ical .ics](https://github.com/fedora-python/python-release-schedule-ical) |
| 42 | + |
| 43 | +- Ryan is teaching Python to 5th-graders 🎉 |
| 44 | + |
| 45 | +## Discussion |
| 46 | + |
| 47 | +- [Petr] Found some older PRs that didn't get to Beta |
| 48 | + - Intersphinx in CPython docs -- [python/cpython#117540](https://github.com/python/cpython/pull/117540) |
| 49 | + - Redistributors build docs while offline. This change shouldn't be merged during beta. On May 8th main will be 3.14 alpha, it could be merged then. |
| 50 | + - Would also be good to map urls to local file paths for offline use. Open edX might have something like this to keep tests from breaking as different docs update at different rates. |
| 51 | + - Module page titles starting with a link to themselves -- [python/cpython#117099](https://github.com/python/cpython/pull/117099) |
| 52 | + - Didn't want to ping 29 code owners. |
| 53 | + - But they get pings a lot anyway. |
| 54 | + - A custom Sphinx plugin could prevent links in all section headers instead. |
| 55 | + - The plugin could also take care of links in sections/paragraphs to the sections/paragraphs. |
| 56 | + - This leads to the question of whether a human or an algorithm should make this decision. |
| 57 | + - Practically: merging this would be a good thing |
| 58 | + - Can we have a linter for links in section heads? |
| 59 | + - We could add a rule to [Sphinx Lint](https://pypi.org/project/sphinx-lint/). |
| 60 | + - Merge versionchanged directives for the same version -- [python/cpython#116456](https://github.com/python/cpython/pull/116456) |
| 61 | + - We agree unanimously that the status quo is better; we'll close the PR. |
| 62 | + - Serhyi's other contributions on the issue are great, though! |
| 63 | + |
| 64 | + |
| 65 | +- [Hugo] RTD migration work continuing: [python/docs-community#5](https://github.com/python/docs-community/issues/5), have a WIP version and language selector at [https://cpython-previews.readthedocs.io/en/main/](https://cpython-previews.readthedocs.io/en/main/) |
| 66 | + - Manuel has done a lot of work on this (and Hugo has reviewed it) |
| 67 | + - The goal is to rebuild after every merge. Or a bit less, but more than the current daily builds |
| 68 | + - The plan is to move HTML first, but then look at other formats too. |
| 69 | + |
| 70 | +- [Petr] [`.. versionchanged:: next`](https://discuss.python.org/t/automating-versionadded-changed-markers-in-docs-to-expedite-prs/38423) -- do we want this in 3.14? |
| 71 | + - For changes that languish beyond a version cut |
| 72 | + - Also for backports? |
| 73 | + - Petr says he will build the tooling |
| 74 | + - Hugo is the release manager for 3.14 and 3.15 and will integrate it into the release tooling |
| 75 | + - Maybe in `blurb release`? |
| 76 | + |
| 77 | +- [Ned] - don't forget to [register](https://us.pycon.org/2024/registration/category/4) for the [Documentation Summit at PyCon](https://us.pycon.org/2024/events/hatchery/docs-summit/), if you're interested. |
| 78 | + |
| 79 | +## Next meeting |
| 80 | + |
| 81 | +The docs team generally meets on the first Tuesday of every month around 19:00-ish UTC. |
| 82 | + |
| 83 | +We have a recurring Google Calendar event for the meeting. |
| 84 | +Let Mariatta know your email address and she can invite you. |
0 commit comments