Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork943
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
encukou commentedNov 17, 2025 • edited by hugovk
Loading Uh oh!
There was an error while loading.Please reload this page.
edited by hugovk
Uh oh!
There was an error while loading.Please reload this page.
I'd use something like: For docs translations following PEP 545, it's fine to give anotice on Discourse, no need to wait for consensus. The Steering Council gave a blanket permission for translation repos in |
StanFromIreland commentedNov 17, 2025
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). 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/