|
| 1 | +--- |
| 2 | +author:["Mariatta"] |
| 3 | +title:"Meeting Minutes: Sep 9, 2025" |
| 4 | +date:"2025-09-09T17:49:01-05:00" |
| 5 | +description:"Meeting Minutes from Python Docs Editorial Board: Sep 9, 2025" |
| 6 | +summary:"Meeting Minutes from Python Docs Editorial Board: Sep 9, 2025" |
| 7 | +tags:["minutes"] |
| 8 | +categories:["minutes"] |
| 9 | +series:["Meeting Minutes"] |
| 10 | +ShowToc:false |
| 11 | +TocOpen:false |
| 12 | +members:["Guido van Rossum", "Joanna Jablonski", "Mariatta", "Ned Batchelder"] |
| 13 | +--- |
| 14 | + |
| 15 | + |
| 16 | + |
| 17 | +###Notes |
| 18 | + |
| 19 | +* We’re a bit disorganized in tracking action items |
| 20 | +* We'll go through the action items and todos from the last meeting |
| 21 | +* TODO: find out where they are coordinating online (mariatta) |
| 22 | +* Who are the Edu & Outreach? Kattni, Keith the ee, Nicholas Tollervey, Jeff Jacobson, Sheena |
| 23 | +* What is the purpose? To learn what they’re doing, what we’re doing, what’s the overlap. |
| 24 | +* TODO: find out from the translators what happens when the source docs change |
| 25 | +* Are we still needed here? |
| 26 | +* There is inconsistency with the different translations groups. Do they need to be consistent? |
| 27 | +* We now get Transifex funded through the PSF core devs fund. |
| 28 | +* But there are other competing options. |
| 29 | +* Do we want to remain in the business of translations? Can we delegate to another group? |
| 30 | +* Should we be explicit in saying we want a sub WG? What do we want this group to be? |
| 31 | +* To coordinate and to support the translations effort |
| 32 | +* Example: Adam Turner led the work about Transifex |
| 33 | +* What is involved in all of this? |
| 34 | +* Translation teams are often well meaning volunteers, who haven’t thought about the tools they need and the amount of work involved. |
| 35 | +* Being added to python-docs-somelanguage requires some vetting and giving access. There needs to be an institutional owner. |
| 36 | +* People who want to translate may not be the ones who want to be coordinating. |
| 37 | +* We want them to form a WG (not a person). |
| 38 | +* Python SC has a formal process for creating new WG (eg the way we create this Board through a PEP) |
| 39 | +* We can also create our own WG and have the WG report to us. |
| 40 | +* We can ask in the translations if they want to form a group. |
| 41 | +* TODO: Ned will follow up with updates from devguide and ask the translations team (this is done:https://discord.com/channels/935215565872693329/1102686540007747586/1415080055796666378) |
| 42 | +* Ned has PRs to the CPython docs |
| 43 | +* Sorting the glossary:<https://discuss.python.org/t/101778/2>: sounds like a great idea |