From 9b9b78b65598b8ea465603e7e93ad366740f330c Mon Sep 17 00:00:00 2001 From: "Gregory P. Smith [Google]" Date: Mon, 23 Jan 2023 08:05:48 +0000 Subject: [PATCH 1/6] Update the Org Repository Policy per the 2022 PSC. This is a result of the discussion started by the 2022 Python Steering Council on https://discuss.python.org/t/new-python-organization-repository-policy/17376 and https://mail.python.org/archives/list/python-dev@python.org/message/FAASOMUNQZDJBCOTZK6I2KH55SDOONF6/. Petr's text from the discuss thread is used, omitting any mention of the PSF Contributor Agreement (CLA) as discussion revealed that it may not make sense for all repos (see thread). It also adopts a suggestion from Joannah to have people discuss additions in our Committers forum before bringing an addition to the Python Steering Council. --- developer-workflow/development-cycle.rst | 45 +++++++++++++++++++----- 1 file changed, 36 insertions(+), 9 deletions(-) diff --git a/developer-workflow/development-cycle.rst b/developer-workflow/development-cycle.rst index 593d61b951..8f38053cad 100644 --- a/developer-workflow/development-cycle.rst +++ b/developer-workflow/development-cycle.rst @@ -216,16 +216,43 @@ The source code is currently hosted on `GitHub Organization Repository Policy ------------------------------ -Within the `Python organization `_, repositories are expected to fall within these general categories: +Within the `Github Python organization `_, +repositories are expected to relate to the Python language, the CPython +reference implementation, their documentation and their development workflow. +This includes, for example: + +* The reference implementation of Python and related repositories (i.e. `CPython `_) +* Tooling and support around CPython development (e.g. `pyperformance `_, `Bedevere `_) +* Helpers and backports for Python/CPython features (e.g. `typing-extensions `_, `typeshed `_, `tzdata `_, `pythoncapi-compat `_) +* Organization-related repositories (e.g. the `Code of Conduct `_, `.github `_) +* Documentation and websites for all the above (e.g. `python.org repository `_, `PEPs `_, `Devguide `_, docs translations) +* Infrastructure for all the above (e.g. `docsbuild-scripts `_, `buildmaster-config `_) +* Discussions and notes around official development-related processes and events (e.g. `steering-council `_, `core-sprint `_) + +Before adding a new repository to the organization, have discussion to seeking +consensus in our `Committers forum `_. +Once people are satisfied with that, ask the `Python steering council `_ +to grant permission. + +Note that several repositories remain in the organization for historic reasons, +and would probably not be appropriate to add today. + +Generally, new repositories should start their life under personal GitHub +accounts or other GitHub orgs. It is relatively easy to move a repository to +the organization once it is mature. For example, this would now apply to +experimental features like `asyncio `_, +`exceptiongroups `_, or +`typed_ast `_, and drafts of new guides +and other documentation (e.g. `redistributor-guide `_). + +General-use tools and libraries (e.g. `mypy `_ +or `black `_) should also be developed outside +the python organization, unless core devs (as represented by the SC) +specifically want to “bless” one implementation (as with e.g. +`typeshed `_, +`tzdata `_, or +`pythoncapi-compat `_). -1. The reference implementation of Python and related repositories (i.e. `CPython `_) -2. Reference implementations of PEPs (e.g. `mypy `_) -3. Tooling and support around CPython and the language (e.g. `python.org repository `_) -4. PSF-related repositories (e.g. the `Code of Conduct `_) -5. PSF Infrastructure repositories (e.g. the `PSF Infrastructure Salt configurations `_) - -For any repository which does not explicitly and clearly fall under one of these categories, permission should be sought -from the `Python steering council `_. Organization Owner Policy ------------------------- From f0a161730fed76dd756743d49935e0a784fe9ef2 Mon Sep 17 00:00:00 2001 From: "Gregory P. Smith [Google]" Date: Mon, 23 Jan 2023 08:34:07 +0000 Subject: [PATCH 2/6] _ not - in typing_extensions --- developer-workflow/development-cycle.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developer-workflow/development-cycle.rst b/developer-workflow/development-cycle.rst index 8f38053cad..6922eaddf8 100644 --- a/developer-workflow/development-cycle.rst +++ b/developer-workflow/development-cycle.rst @@ -223,7 +223,7 @@ This includes, for example: * The reference implementation of Python and related repositories (i.e. `CPython `_) * Tooling and support around CPython development (e.g. `pyperformance `_, `Bedevere `_) -* Helpers and backports for Python/CPython features (e.g. `typing-extensions `_, `typeshed `_, `tzdata `_, `pythoncapi-compat `_) +* Helpers and backports for Python/CPython features (e.g. `typing_extensions `_, `typeshed `_, `tzdata `_, `pythoncapi-compat `_) * Organization-related repositories (e.g. the `Code of Conduct `_, `.github `_) * Documentation and websites for all the above (e.g. `python.org repository `_, `PEPs `_, `Devguide `_, docs translations) * Infrastructure for all the above (e.g. `docsbuild-scripts `_, `buildmaster-config `_) From b213210fe032ab153fef114414180c31464a59b4 Mon Sep 17 00:00:00 2001 From: "Gregory P. Smith" Date: Mon, 23 Jan 2023 21:22:31 -0800 Subject: [PATCH 3/6] Update developer-workflow/development-cycle.rst Co-authored-by: Hugo van Kemenade --- developer-workflow/development-cycle.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developer-workflow/development-cycle.rst b/developer-workflow/development-cycle.rst index 6922eaddf8..c9cabead82 100644 --- a/developer-workflow/development-cycle.rst +++ b/developer-workflow/development-cycle.rst @@ -216,7 +216,7 @@ The source code is currently hosted on `GitHub Organization Repository Policy ------------------------------ -Within the `Github Python organization `_, +Within the `GitHub Python organization `_, repositories are expected to relate to the Python language, the CPython reference implementation, their documentation and their development workflow. This includes, for example: From fae53d87f516d358cec2d82fe0c215a8d92a1573 Mon Sep 17 00:00:00 2001 From: "Gregory P. Smith" Date: Mon, 23 Jan 2023 21:23:35 -0800 Subject: [PATCH 4/6] Update developer-workflow/development-cycle.rst Co-authored-by: C.A.M. Gerlach --- developer-workflow/development-cycle.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/developer-workflow/development-cycle.rst b/developer-workflow/development-cycle.rst index c9cabead82..ea83ce212f 100644 --- a/developer-workflow/development-cycle.rst +++ b/developer-workflow/development-cycle.rst @@ -229,8 +229,8 @@ This includes, for example: * Infrastructure for all the above (e.g. `docsbuild-scripts `_, `buildmaster-config `_) * Discussions and notes around official development-related processes and events (e.g. `steering-council `_, `core-sprint `_) -Before adding a new repository to the organization, have discussion to seeking -consensus in our `Committers forum `_. +Before adding a new repository to the organization, open a discussion to seek consensus +in the `Committers Discourse category `_. Once people are satisfied with that, ask the `Python steering council `_ to grant permission. From 30cc9f283fda9776ff87b426be6f5d18bc20841a Mon Sep 17 00:00:00 2001 From: "Gregory P. Smith" Date: Mon, 23 Jan 2023 21:23:59 -0800 Subject: [PATCH 5/6] Update developer-workflow/development-cycle.rst Co-authored-by: C.A.M. Gerlach --- developer-workflow/development-cycle.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/developer-workflow/development-cycle.rst b/developer-workflow/development-cycle.rst index ea83ce212f..708eaa01e7 100644 --- a/developer-workflow/development-cycle.rst +++ b/developer-workflow/development-cycle.rst @@ -246,8 +246,8 @@ experimental features like `asyncio `_, and other documentation (e.g. `redistributor-guide `_). General-use tools and libraries (e.g. `mypy `_ -or `black `_) should also be developed outside -the python organization, unless core devs (as represented by the SC) +or `Black `_) should also be developed outside +the ``python`` organization, unless core devs (as represented by the SC) specifically want to “bless” one implementation (as with e.g. `typeshed `_, `tzdata `_, or From a08291c47cdd38b943d1183da4fc4dec284d870b Mon Sep 17 00:00:00 2001 From: "Gregory P. Smith" Date: Mon, 23 Jan 2023 21:26:14 -0800 Subject: [PATCH 6/6] remove typed_ast mention --- developer-workflow/development-cycle.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/developer-workflow/development-cycle.rst b/developer-workflow/development-cycle.rst index 708eaa01e7..851cd68f7c 100644 --- a/developer-workflow/development-cycle.rst +++ b/developer-workflow/development-cycle.rst @@ -241,9 +241,9 @@ Generally, new repositories should start their life under personal GitHub accounts or other GitHub orgs. It is relatively easy to move a repository to the organization once it is mature. For example, this would now apply to experimental features like `asyncio `_, -`exceptiongroups `_, or -`typed_ast `_, and drafts of new guides -and other documentation (e.g. `redistributor-guide `_). +`exceptiongroups `_, +and drafts of new guides and other documentation (e.g. `redistributor-guide +`_). General-use tools and libraries (e.g. `mypy `_ or `Black `_) should also be developed outside