# CPython Translations ## Today (8 years after PEP 545 Creation) - Python has seen tremendous growth over the past 8 years. :rocket: - PEP 545 gave us a great foundation for translations during these years. Today, there is strong interest and enthusiasm about translating CPython documentation. :tada: - It's a good time to look at how we can empower more contributors interested in translation projects (existing and new). - At the 2025 PyCon Language Summit, there was a brief discussion on Translations including the good work that has been happening and ways to improve the contributor experience. ## First steps - Unblocking contributors to docs where the coordinator has become inactive or unresponsive. (This is the highest priority.) - Adding Translation discussion items to the Monthly Docs Community Calls - Creating a Translation subcategory under Documentation on discuss.python.org - Continue using Discord #translation channel since it is fostering discussion - We'll be relying on the DevGuide Translating page to provide transparency of how we are working today which may be slightly different than PEP 545. Since there are multiple coordinators for several languages, we're going to lean into allowing multiple coordinators for a language. This allows us to unblock contributors while also reducing the likelihood of single points of failure. ## Next steps - Provide a way through the docs community meeting or a separate translation meeting for people interested in translations to meet and discuss best practices - Through these meetings we will work together to identify what process changes may be helpful to add to PEP 545 which would serve CPython well going forward. ## Resources - [PEP 545 Python Documentation Translations](https://peps.python.org/pep-0545/) - PEP Authors: Julien Palard <julien at palard.fr>, Inada Naoki <songofacandy at gmail.com>, Victor Stinner <vstinner at python.org> - PEP Creation Date: 04-Mar-2017 - [Python DevGuide Translating Page](https://devguide.python.org/documentation/translating/) > Anyone who wants to become coordinator for their native language and shows motivation by translating and building a community will be named coordinator. > In case of concurrency between two persons, no one will sort this out for you. It is up to you two to organize a local election or whatever is needed to sort this out. > If a coordinator becomes inactive or unreachable for a long period of time, someone else can ask for a takeover on the translation mailing list. > Ask on the translation mailing list, or better, make a PR on the devguide. - Dashboard https://python-docs-translations.github.io/dashboard/ - GitHub org for Python Docs Translations: https://github.com/python-docs-translations - 3 open PRs for PEP 545 [4296,4297,4298] https://github.com/python/peps/pull/4296 - [Python Discord announcement on how to contribute to translations](https://discord.com/channels/267624335836053506/723655946672275466/1195122632413171772)