-
-
Notifications
You must be signed in to change notification settings - Fork 963
Exclude docs translations from organization repo policy #1690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exclude docs translations from organization repo policy #1690
Conversation
I'd use something like:
For docs translations following PEP 545, it's fine to give a notice on Discourse, no need to wait for consensus. The Steering Council gave a blanket permission for translation repos in <issue>.
StanFromIreland
commented
Nov 17, 2025
it's fine to give a notice on Discourse
This is a bit of a more complex thing since we have yet to decide when exactly we should create/move the repo. In the past it has been done at varying stages of the translation (e.g. at the very start or after a few weeks of consistent contributions in a fork) and there have been varying outcomes (i.e. the newly created repo's being left empty/abandoned).
In the current process we have, posting on Discourse is already a requirement, but that is done at the start of the translation, hence the question arises, should that also be the start of the repository?
I'd like to avoid that discussion for now, and clean up this issue first (i.e. us "breaking" the rules). I will open a SC issue for their bemusement.
Uh oh!
There was an error while loading. Please reload this page.
I will post more on this on Discourse.
π Documentation preview π: https://cpython-devguide--1690.org.readthedocs.build/