steering-council icon indicating copy to clipboard operation
steering-council copied to clipboard

Requesting exclusion for future PEP 545 repositories from our organization repo policy

Open StanFromIreland opened this issue 3 months ago • 0 comments

Since PEP 545's acceptance, new docs translation repos (i.e. python-docs-*, e.g. python-docs-pl), have been in practice excluded from the discussion and SC submission process. I would like to formalise this exception to ensure the security of the new translation process.

However, the new translation process also has a few points we have yet to settle on, one of those being when exactly the repository under python is to be created.

In the past, it has been created at the very start of the translation (even before, in some instances), and in other cases the translators worked on a fork for a while, and then it was moved under the organisation. This however, is a separate (and long) discussion and has been previously debated a few times on various PR's, but to no avail. (I had to leave the section quite vague.)

As such, in the proposed text I have left it up to a core team member's discretion (essentially the current practice). But, I hope that in the future we can settle on a concrete and quantifiable guideline, so I would also like to request that once we decide on it (and possibly ultimately the @python/editorial-board), that we be allowed to update (in essence, make stricter) the policy with it.

The actual text is not particularly important here, I will happily modify it to whatever is requested, but I have one proposed in https://github.com/python/devguide/pull/1690. Note that I also posted a similar message on Discourse yesterday (https://discuss.python.org/t/17376/45).

StanFromIreland avatar Nov 17 '25 17:11 StanFromIreland