|
| 1 | +# Documentation Community Team Meeting (September 2022) |
| 2 | + |
| 3 | +- **Date:** 2022-09-12 |
| 4 | +- **Time:** [21:00 UTC](https://arewemeetingyet.com/UTC/2022-09-12/21:00/Docs%20Meeting) |
| 5 | +- **This HackMD:** https://hackmd.io/@encukou/pydocswg1 |
| 6 | +- **Discourse thread:** https://discuss.python.org/t/18590 |
| 7 | +- **Calendar for future meetings:** (send your e-mail to Mariatta for a calendar invitation) |
| 8 | +- **How to participate:** |
| 9 | + - Go to [Google Meet](https://meet.google.com/dii-qrzf-wkw) and ask to be let in. |
| 10 | + - 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). |
| 11 | + |
| 12 | +By participating in this meeting, you are agreeing to abide by and uphold the [PSF Code of Conduct](https://www.python.org/psf/codeofconduct/). |
| 13 | +Please take a second to read through it! |
| 14 | + |
| 15 | + |
| 16 | +## Roll call |
| 17 | + |
| 18 | +- Petr Viktorin / `@encukou` |
| 19 | +- Ezio Melotti / `@ezio-melotti` |
| 20 | +- Mariatta / `@mariatta` |
| 21 | +- Ned Batchelder / `@nedbat` |
| 22 | +- C.A.M. Gerlach / `@CAM-Gerlach` |
| 23 | + |
| 24 | + |
| 25 | +## Reports and celebrations |
| 26 | + |
| 27 | +- We will be publishing the Workshop videos to YouTube soon. Stay tuned for |
| 28 | + announcement and emails. |
| 29 | + |
| 30 | +- Ee is back, so several things should get unblocked in the coming weeks, |
| 31 | + like the YouTube uploads or docs preview on Netlify |
| 32 | + |
| 33 | +- What's New editing (**CAM**) |
| 34 | + - Major PEP sized items all added except for PEP 670 |
| 35 | + - First set of copyedit PRs waiting on review/merge; please help! |
| 36 | + - Refs from summary to body content will be PRed very soon |
| 37 | + - Remaining items will be submitted as PRs soon(™) |
| 38 | + - See [python/cpython#95913](https://github.com/python/cpython/issues/95913) and [python/cpython#95914](https://github.com/python/cpython/issues/95914) |
| 39 | + |
| 40 | +- "Past Action Item": Try building automation to prevent link breakage using the `.inv` file |
| 41 | + - Moving whole pages could be handled by [sphinxext-rediraffe](https://sphinxext-rediraffe.readthedocs.io/) |
| 42 | + like in the devguide |
| 43 | + - Moving fragments (the `#` part of URLs, like headings and reference entries) |
| 44 | + is not handled well |
| 45 | + - Intersphinx links work well for reference entries, but many external |
| 46 | + links don't come form Sphinx |
| 47 | + - Fixing Sphinx roles might break Intersphinx, depending on how the URL |
| 48 | + is generated |
| 49 | + |
| 50 | +- Fixing bad Sphinx links |
| 51 | + - Big project, but could be good for newer contributors |
| 52 | + - **Petr** might have a GH Actions-based per-document check for PRs |
| 53 | + - Some links, e.g. in old What's New, might need to stay broken. |
| 54 | + Silencing errors with `!` doesn't always work |
| 55 | + |
| 56 | +- Running linkcheck regularly (on devguide?) |
| 57 | + - Seems like a good idea, just needs someone to implement |
| 58 | + (**Ezio**, or **CAM** if needed) |
| 59 | + - See [python/devguide#681](https://github.com/python/devguide/issues/681) and [python/devguide#917](https://github.com/python/devguide/issues/917) |
| 60 | + |
| 61 | +### 'Internal' items |
| 62 | + |
| 63 | +*For and about the Community or Working Group* |
| 64 | + |
| 65 | +- Future meeting schedule |
| 66 | + - Best time seems to be 19:30 - 20:30 UTC, 1.5 hours earlier than current |
| 67 | + - **Petr** will ask on Discord if anyone objects |
| 68 | + |
| 69 | +## Next meeting |
| 70 | + |
| 71 | +The docs team meets on the first Monday of every month. |
| 72 | + |
| 73 | +We have a recurring Google Calendar event for the meeting. |
| 74 | +Let Mariatta know your email address and she can invite you. |
0 commit comments