Minutes from January 2025 (#144)

Co-authored-by: Hugo van Kemenade <[email protected]>

docs/monthly-meeting/2025-01.md

@@ -0,0 +1,92 @@
+# Documentation Community Team Meeting (January 2025)
+
+- **Date:** 2025-01-07
+- **Time:** [20:00 UTC](https://arewemeetingyet.com/UTC/2024-11-05/20:00/Docs20Meeting)
+- **This HackMD:** <https://hackmd.io/@encukou/pydocswg1>
+- [**Discourse thread**](https://discuss.python.org/t/documentation-community-meeting-tuesday-7th-january-2025/75975) (for January)
+- [**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))
+- **Calendar event:** (send your e-mail to Mariatta for an invitation)
+- **How to participate:**
+  -  We are using Discord: <https://discord.gg/RxKXyPYV?event=1303462925834522666>
+  -  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).
+
+By participating in this meeting, you are agreeing to abide by and uphold the [PSF Code of Conduct](https://www.python.org/psf/codeofconduct/).
+Please take a second to read through it!
+
+
+## Roll call
+
+(Name / `@GitHubUsername` *[/ Discord, if different]*)
+
+- Adam Turner / `@AA-Turner`
+- Hugo van Kemenade / `@hugovk`
+- Petr Viktorin / `@encukou`
+- Trey Hunner / `@treyhunner`
+- Keith / `@KeithTheEE`
+- Ryan Duve / `@ryan-duve`
+- Sherry
+- Blaise / `@blaisep`
+- Stan Ulbrych / `@StanFromIreland`
+
+
+## Introductions
+
+> If there are any new people, we should do a round of introductions.
+
+This was Sherry's first meeting, introductions were made.
+
+
+## Reports and celebrations
+
+> 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.
+
+> 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.
+
+- 🇵🇱 "Witamy! To jest oficjalna dokumentacja Pythona 3.13.1." The Python docs are now officially available in Polish! 🚀 [docs.python.org/pl/3/](https://docs.python.org/pl/3/)
+
+
+## Discussion
+
+### Translations
+
+- Should we change the translation progress limit for being included in the language switcher?
+  - This is currently the tutorial and the bugs and functions pages.
+  - Brief discussion on this threshold, no strong desire to change.
+- [Adam] Introduce a page for translation progress, like [React's](https://translations.react.dev/), it just needs to be wired up.
+  - There's already [Maciej's page](https://m-aciek.github.io/pydocs-translation-dashboard/)
+  - Issue created: [docs-community#143](https://github.com/python/docs-community/issues/143)
+  - Action: link Maciej's page from the devguide.
+  - Action: Add links to contribute.
+  - Action: Look to move to `https://docs.python.org/translations` (via `docsbuild-scripts`)?
+- [Adam] Fate of the language switcher?
+  - Not very maintainable or good for accessibility. It might be better to have a page for choosing languages.
+  - Other docs are fairly evenly split between a page to choose and a language switcher per page.
+  - Switching to the *current* page in another language might be important.
+  - Seek feedback from those that use the switcher or frequently read non-English documentation.
+
+### Grammar documentation & Sphinx directives
+
+- Petr and Blaise have been working on an improved version of Sphinx's `production-list` directive to represent and document Python's grammar.
+- Petr provided a demonstration of his work.
+- There is an initial PR to add the directives at [python/cpython#127835](https://github.com/python/cpython/pull/127835)
+- This initially adds the directive, grammar snippets (and the surrounding prose) will be converted later, potentially looking to make this automatic.
+
+### Tutorial for beginners
+
+- Can we break up the work so people can contribute in parallel?
+- Is this better on `docs.python.org`, or third parties (O'Reilly, w3schools, etc.)?
+  - Probably better *started* as a third-party effort, so you don't need approvals up-front. (That's also how additions to stdlib should work. Or the translation status page.)
+  - Third parties know their audience better, and can serve more diverse audiences.
+  - Tutorials need to cater to many different audiences (children in schools, scientists in labs, experienced programmers from other languages, those entirely new to programming), this might be better accomplished by third parties.
+- Many people start with the python.org tutorial, and some “bounce off” and go to another tutorial or leave Python entirely.
+  - The existing tutorial is targeted at experienced programmers.
+  - Link to other tutorials (without endorsing)?
+- Mariatta was driving the effort.
+
+
+## Next meeting
+
+The docs team generally meets on the first Tuesday of every month around 20:00-ish UTC.
+
+We have a recurring Google Calendar event for the meeting.
+Let Mariatta know your email address and she can invite you.

docs/monthly-meeting/index.rst

@@ -28,3 +28,4 @@ Monthly reports in chronological order.
    Oct 2024 <2024-10.md>
    Nov 2024 <2024-11.md>
    Dec 2024 <2024-12.md>
+   Jan 2025 <2025-01.md>