diff --git a/developer-workflow/development-cycle.rst b/developer-workflow/development-cycle.rst index 593d61b951..851cd68f7c 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, 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. + +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 `_, +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 -------------------------