Merge branch 'main' into wasi-build

Author: savannahostrowski

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,7 +1,7 @@
 name: "Bug report"
 description: Create a report to help us improve the Python devguide
 title: "Bug: <title>"
-labels: ["bug"]
+labels: ["type-bug"]
 assignees: []
 
 body:

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,7 +1,7 @@
 name: "Feature request"
 description: Suggest an idea for the Python devguide
 title: "Feature: <title>"
-labels: ["enhancement"]
+labels: ["type-feature"]
 assignees: []
 
 body:

developer-workflow/development-cycle.rst

@@ -232,7 +232,10 @@ This includes, for example:
 Before adding a new repository to the organization, open a discussion to seek consensus
 in the `Committers Discourse category <https://discuss.python.org/c/committers/5>`__.
 Once people are satisfied with that, ask the `Python steering council <https://github.com/python/steering-council>`__
-to grant permission.
+to grant permission. Note that this process is not necessary for
+:ref:`docs translations <translation-repo>` following
+:pep:`PEP 545 <545#repository-for-po-files>`, which can be added at a
+core team member’s discretion.
 
 Note that several repositories remain in the organization for historic reasons,
 and would probably not be appropriate to add today.

documentation/translations/coordinating.rst

@@ -64,6 +64,8 @@ to make your translation easier to find. In the entry you can also include links
 to guides or other resources for translators.
 
 
+.. _translation-repo:
+
 Repository
 ----------