Translations process: PEP 545 and beyond discussion at next docs community meeting

Documentation
1

There’s been lots of activity over the past 2 months about translations. It’s great that we have strong interest in translation. :tada:

Building on the helpful work of @JulienPalard and others on PEP 545 eight years ago and stewarding translations since then, we discussed briefly at the CPython Language Summit to revisit any process modifications that may be beneficial moving forward. One of the key process changes that the core team found beneficial (some languages are already doing) was to expand the coordinator role from an individual to more than one individual when there is interest.

Here’s a baseline doc to bootstrap discussion at the meeting.

In the interim, I will cross post this on discuss.python.org.

UPDATE: The docs-community issue for the meeting agenda: Add Translations agenda item for the June 2025 docs community meeting · Issue #156 · python/docs-community · GitHub

6 Likes
2

Thank you! Added to the agenda.

1 Like
3

I’m +1 on allowing multiple coordinators, good idea.

1 Like
4

-1 for using Discord, among many thing I don’t like about Discord (to the point I deleted my account a few weeks after creating it) logs are not public, so I feel a bit excluded (which is OK as I don’t have much time nowadays, but there may exist other people not willing to create a Discord account).

+1 for creating a translation category in Discourse.

7 Likes
5

I think once we have a translation category set up here. We can move more discussions here.

While Discord may be low friction for some coordinators, it is less convenient to get the word out and encourage translators at conferences and sprints as well as volunteers.

Thanks @julien. Hope to see you at the Docs Community meeting