|
| 1 | +# Documentation Community Team Meeting (November 2024) |
| 2 | + |
| 3 | +- **Date:** 2024-11-05 |
| 4 | +- **Time:** [20:00 UTC](https://arewemeetingyet.com/UTC/2024-11-05/20:00/Docs%20Meeting) |
| 5 | +- **This HackMD:** <https://hackmd.io/@encukou/pydocswg1> |
| 6 | +- [**Discourse thread**](https://discuss.python.org/t/documentation-community-meeting-tuesday-5th-november-2024/68579) |
| 7 | + (for November) |
| 8 | +- [**Meeting reports**](https://docs-community.readthedocs.io/en/latest/monthly-meeting/) |
| 9 | + (the latest one might be an |
| 10 | + [**unmerged PR**](https://github.com/python/docs-community/pulls)) |
| 11 | +- **Calendar event:** (send your e-mail to Mariatta for an invitation) |
| 12 | +- **How to participate:** |
| 13 | + - Go to [Google Meet](https://meet.google.com/dii-qrzf-wkw) and ask to be let in. |
| 14 | + - To edit notes, click the “pencil” or “split view” button on the |
| 15 | + [HackMD document](https://hackmd.io/@encukou/pydocswg1). You need to log in (e.g. |
| 16 | + with a GitHub account). |
| 17 | + |
| 18 | +By participating in this meeting, you are agreeing to abide by and uphold the |
| 19 | +[PSF Code of Conduct](https://www.python.org/psf/codeofconduct/). Please take a second |
| 20 | +to read through it! |
| 21 | + |
| 22 | +## Roll call |
| 23 | + |
| 24 | +(Name / `@GitHubUsername` _[/ Discord, if different]_) |
| 25 | + |
| 26 | +- Hugo van Kemenade / @hugovk |
| 27 | +- Mariatta |
| 28 | +- Joe |
| 29 | +- Ned Batchelder / `@nedbat` |
| 30 | +- Trey |
| 31 | +- Daniele |
| 32 | +- Ryan / `ryan-duve` |
| 33 | +- Petr / `@encukou` |
| 34 | + |
| 35 | +## Introductions |
| 36 | + |
| 37 | +> If there are any new people, we should do a round of introductions. |
| 38 | +
|
| 39 | +## Discussion |
| 40 | + |
| 41 | +## Discussion |
| 42 | + |
| 43 | +- [Mariatta] Python Translation coordinators and their role within Core Python |
| 44 | + - translation coordinators are separate from core Python development |
| 45 | + - not considered for core sprint/language summit, unlike mypy, packaging, and so on |
| 46 | + - should work more closely with coordinators |
| 47 | + - considered as external group |
| 48 | + - Petr: English often used in Czechia |
| 49 | + - Mariatta: non-English needed outside Europe/North America, like in China |
| 50 | + - Daniele: give spaces/platform for their voices to be heard |
| 51 | + - Ned: was there a discussion about more fine-grained permissions? how many would it |
| 52 | + be that could join core team? |
| 53 | + - Mariatta: perhaps 10 with completed translations. other langs need support, |
| 54 | + motivation from other teams |
| 55 | + - Petr: which is hard; once you've learnt Eng need motivation to translate docs |
| 56 | + - Ned: what would help with motivation? would adding to core team help with |
| 57 | + motivation? |
| 58 | + - Daniele: we need to involve translators in this discussion, do they feel external, |
| 59 | + can we bring them in and ask what they want to do? then answers should just come |
| 60 | + - Daniele & Blaise mentioned Felienne Hermans who recently spoke at PyCon Netherlands |
| 61 | + about translating programming languages. Maybe a subset/niche community like that |
| 62 | + might have folks interested in helping. |
| 63 | + - Petr: there's a role we need to fill, like a coordinator like Julien used to do, |
| 64 | + with guidance, templates to help translate. we don't really know how to do it |
| 65 | + - Blaise: re: recognition, uncertainty around identity of a translator. docs people |
| 66 | + considered as contributors, should translators be part of a SIG? |
| 67 | + - Mariatta: from core team, don't need to wait for them to ask, we need to come up |
| 68 | + with initiative. people don't ask for recognition |
| 69 | + - Hugo: create translator team on GitHub python org? most permissions are prob dealt |
| 70 | + on per-repo basis, but if nothing else, for visibility to show usernames under |
| 71 | + `python/` on GitHub |
| 72 | + - Hugo: [PEP 545](https://peps.python.org/pep-0545/) is the governance general |
| 73 | + process, |
| 74 | + [devguide lists contacts](https://devguide.python.org/documentation/translating/) |
| 75 | + - Joe: no translation FAQ about machine translation, is there a policy? |
| 76 | + - Hugo: some teams use machine translation as first draft, human revises. seems |
| 77 | + reasonable |
| 78 | + - |
| 79 | +- [Hugo] Move `python-docs-theme` under `cpython` PyPI org: |
| 80 | + https://discuss.python.org/t/request-python-organisation-on-pypi/26545/10 |
| 81 | + - Petr: why not `python`? |
| 82 | + - Hugo: because if other projects use the theme, they're |
| 83 | + [borrowing trust and credibility from CPython](https://github.com/python/python-docs-theme). |
| 84 | + but let's bikeshed this elsewhere :) |
| 85 | +- [Petr] Mariatta and Petr are current hosts who can let people into the meeting. Should |
| 86 | + we have more Google Meeting co-hosts to let more in? |
| 87 | + - Mariatta: Or use Discord instead? |
| 88 | + - Group decision: we'll test Discord next month |
| 89 | +- [Carol] History of Dead Batteries page/approach |
| 90 | + https://discuss.python.org/t/history-of-dead-batteries/68934 |
| 91 | + - Hugo: should we have stub pages? |
| 92 | + - Ned: yes, redirect them to a single page with info on replacements. before we got |
| 93 | + 404, now we get redirect to homepage instead of 404, which bit less useful |
| 94 | + - Petr: also keep entries for removed functions/classes. better place for porting |
| 95 | + notes than in cramming in What's New. |
| 96 | +- [Carol] API navigation or tables on long pages: |
| 97 | + https://discuss.python.org/t/summary-tables-as-an-api-overview/68474 |
| 98 | + - [python/cpython#125810](https://github.com/python/cpython/pull/125810) -> |
| 99 | + [docs.python.org/3/library/math.html](https://docs.python.org/3/library/math.html) |
| 100 | + - [python/cpython#126342](https://github.com/python/cpython/pull/126342) -> |
| 101 | + [cpython-previews--126342.org.readthedocs.build/en/126342/library/pathlib.html#summary](https://cpython-previews--126342.org.readthedocs.build/en/126342/library/pathlib.html#summary) |
| 102 | + - ran out of time to cover this time, but please check the PRs! |
| 103 | + |
| 104 | +## Next meeting |
| 105 | + |
| 106 | +The docs team generally meets on the first Tuesday of every month around 20:00-ish UTC. |
| 107 | + |
| 108 | +We have a recurring Google Calendar event for the meeting. Let Mariatta know your email |
| 109 | +address and she can invite you. |
0 commit comments