Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

Draft
StanFromIreland wants to merge1 commit intopython:main
base:main
Choose a base branch
Loading
fromStanFromIreland:translation/repopolicy

Conversation

@StanFromIreland
Copy link
Member

@StanFromIrelandStanFromIreland commentedNov 15, 2025
edited by github-actionsbot
Loading

I will post more on this on Discourse.


📚 Documentation preview 📚:https://cpython-devguide--1690.org.readthedocs.build/

@StanFromIrelandStanFromIreland changed the titleExclude docs translations from new repo policyExclude docs translations from organization repo policyNov 15, 2025
@encukou
Copy link
Member

encukou commentedNov 17, 2025
edited by hugovk
Loading

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<issue>.

@StanFromIreland
Copy link
MemberAuthor

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 isalready 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.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@encukouencukouAwaiting requested review from encukou

Assignees

No one assigned

Labels

None yet

Projects

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@StanFromIreland@encukou

[8]ページ先頭

©2009-2025 Movatter.jp