|
| 1 | +# Documentation Community Team Meeting (March 2023) |
| 2 | + |
| 3 | +:::info |
| 4 | +- **Date:** 2023-03-06 |
| 5 | +- **Time:** [20:00 UTC](https://arewemeetingyet.com/UTC/2023-03-06/20:00/Docs%20Meeting) |
| 6 | +- **This HackMD:** https://hackmd.io/@encukou/pydocswg1 |
| 7 | +- [**Discourse thread**](https://discuss.python.org/t/documentation-community-meeting-march-6-2023/24293) (for March) |
| 8 | +- [**Meeting's reports**](https://docs-community.readthedocs.io/en/latest/monthly-meeting/index.html) (the latest one might be an [**unmerged PR**](https://github.com/python/docs-community/pulls)) |
| 9 | +- **Calendar event:** (send your e-mail to Mariatta for an invitation) |
| 10 | +- **How to participate:** |
| 11 | + - Go to [Google Meet](https://meet.google.com/dii-qrzf-wkw) and ask to be let in. |
| 12 | + - 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). |
| 13 | +::: |
| 14 | + |
| 15 | +By participating in this meeting, you are agreeing to abide by and uphold the [PSF Code of Conduct](https://www.python.org/psf/codeofconduct/). |
| 16 | +Please take a second to read through it! |
| 17 | + |
| 18 | +## Roll call |
| 19 | + |
| 20 | +(Name / `@GitHubUsername`) |
| 21 | + |
| 22 | +- Petr Viktorin / `@encukou` |
| 23 | +- Ezio Melotti / `@ezio-melotti` |
| 24 | +- Ege Akman / `@egeakman` |
| 25 | +- C.A.M. Gerlach / `@CAM-Gerlach` |
| 26 | +- Ryan Duve / `@ryan-duve` |
| 27 | +- Paul Hoffman / `@paulehoffman` |
| 28 | +- Hugo van Kemenade / `@hugovk` |
| 29 | +- Pradyun Gedam / `pradyunsg` |
| 30 | + |
| 31 | +## Introductions |
| 32 | + |
| 33 | +> If there are any new people, we should do a round of introductions. |
| 34 | +
|
| 35 | + |
| 36 | +## Reports and celebrations |
| 37 | + |
| 38 | +> 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. |
| 39 | +> |
| 40 | +
|
| 41 | +> 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. |
| 42 | +
|
| 43 | +* Hugo: Automatically edit PRs with link to RTD preview |
| 44 | + * https://github.com/python/devguide/pull/1061 |
| 45 | + * https://github.com/python/docs-community/pull/74 |
| 46 | + * https://github.com/python/peps/pull/3031 |
| 47 | + * TODO: Hugo to cleanup the Netlify action so we can transfer to https://github.com/python |
| 48 | + |
| 49 | +* Hugo: Append a hash ?digest to CSS files for cache-busting |
| 50 | + * https://github.com/python/devguide/pull/1054 |
| 51 | + * https://github.com/python/python-docs-theme/pull/108 |
| 52 | + |
| 53 | + |
| 54 | + |
| 55 | +## Discussion |
| 56 | + |
| 57 | +* Netlify previews |
| 58 | + |
| 59 | + |
| 60 | +### 'Internal' items |
| 61 | + |
| 62 | +*For and about the Community or Working Group* |
| 63 | + |
| 64 | +- Overhaul Building the Documentation section for clarity |
| 65 | + - [python/devguide#1038](https://github.com/python/devguide/pull/1038) |
| 66 | + - merged |
| 67 | + |
| 68 | +- [python/devguide#1020](https://github.com/python/devguide/issues/1020): Function signatures in docs (positional-only mar
10000
kers, defaults, `[]` syntax) |
| 69 | + - How discoverable is the `[]` syntax to today's devs? |
| 70 | + |
| 71 | + |
| 72 | +### Python Project Documentation |
| 73 | + |
| 74 | +*Relating to `docs.python.org`, `peps.python.org`, `devguide.python.org`, etc.* |
| 75 | + |
| 76 | +* Dark theme for docs.python.org |
| 77 | + * (Hugo) PR looks ready to merge: https://github.com/python/python-docs-theme/pull/44#pullrequestreview-1314475876 |
| 78 | + * Preview: https://python-docs-theme-previews--44.org.readthedocs.build/en/44/ |
| 79 | + * TODO: Hugo open an issue to ask for a release with pending bugfixes, followed by another with dark theme for easy rollback if needed |
| 80 | + |
| 81 | +* [Lutra](https://pradyunsg.me/lutra/)! Improving the bus factor, accessibility and next steps? |
| 82 | + |
| 83 | +* Move [PEP 636 (Structural Pattern Matching: Tutorial)](https://peps.python.org/pep-0636/#composing-patterns) to main docs |
| 84 | + * See [Discourse thread](https://discuss.python.org/t/is-there-a-good-writeup-talk-about-the-implementation-of-pep-634/21987/6) |
| 85 | + |
| 86 | +* [`concurrent.futures`](https://docs.python.org/3.12/library/concurrent.futures.html) reorgantization |
| 87 | + * See [Diataxis website](https://diataxis.fr/) and [Diataxis workshop videos](https://discuss.python.org/t/recordings-available-for-python-docs-diataxis-workshop/19518) for more information on organization |
| 88 | + |
| 89 | +* Sphinx warnings on CI: [hugovk/cpython#43](https://github.com/hugovk/cpython/pull/43) |
| 90 | + * Build on Petr's [python/cpython#21](https://github.com/encukou/cpython/pull/21) |
| 91 | + * show Sphinx warnings in changed files, can't fail |
| 92 | + * show Sphinx warnings in required-list (e.g. What's New in 3.12), can fail |
| 93 | + * TODO: Hugo to PR this upstream |
| 94 | + |
| 95 | + |
| 96 | +### PEPs styling |
| 97 | + |
| 98 | + |
| 99 | +### PEP Workflow |
| 100 | + |
| 101 | +* Final PEPs and the canonical docs banner link: in PR [python/peps#2992](https://github.com/python/peps/pull/2992) |
| 102 | +* [PEP 1 rewrite?](https://discuss.python.org/t/21068/26)* Status for PEP 659 and other obsolete PEPs? |
| 103 | + |
| 104 | +## Next meeting |
| 105 | + |
| 106 | +The docs team generally meets on the first Monday of every month. |
| 107 | + |
| 108 | +We have a recurring Google Calendar event for the meeting. |
| 109 | +Let Mariatta know your email address and she can invite you. |
0 commit comments