From 413f7f471c8fed2b6843faf3f856188375ed5bb2 Mon Sep 17 00:00:00 2001 From: "Nathaniel J. Smith" Date: Fri, 30 Nov 2018 19:23:48 -0800 Subject: [PATCH] PEP 8010, 8011: Clarify authority of GUIDO and Trio (#845) Reference for 8010: https://discuss.python.org/t/straw-poll-which-governance-proposals-do-you-like-best/436/38 Reference for 8011: https://discuss.python.org/t/straw-poll-which-governance-proposals-do-you-like-best/436/28 Summary: https://discuss.python.org/t/straw-poll-which-governance-proposals-do-you-like-best/436/40 Barry requests a PR: https://discuss.python.org/t/straw-poll-which-governance-proposals-do-you-like-best/436/42 --- pep-8010.rst | 22 +++++++++++++--------- pep-8011.rst | 13 +++++++++++++ 2 files changed, 26 insertions(+), 9 deletions(-) diff --git a/pep-8010.rst b/pep-8010.rst index fa802a780..2fe1a810d 100644 --- a/pep-8010.rst +++ b/pep-8010.rst @@ -104,15 +104,15 @@ consensus may not emerge. Either choice is equally valid. In consultation with the CoP, it will be the GUIDO's vision that guides the ultimate decision. -The GUIDO is the ultimate authority for decisions on PEPs, including -whether any particular change is PEP-worthy. As is the case today, -many --in fact perhaps most-- decisions are handled by discussion and -resolution on the issue tracker, merge requests, and discussion -forums, usually with input or lead by experts in the particular field. -Where this operating procedure works perfectly well, it can continue -unchanged. This also helps reduce the workload on the CoP and GUIDO, -leaving only the most important decisions and broadest view of the -landscape to the central authority. +The GUIDO is the ultimate authority for decisions on PEPs and other +issues, including whether any particular change is PEP-worthy. As is +the case today, many --in fact perhaps most-- decisions are handled by +discussion and resolution on the issue tracker, merge requests, and +discussion forums, usually with input or lead by experts in the +particular field. Where this operating procedure works perfectly +well, it can continue unchanged. This also helps reduce the workload +on the CoP and GUIDO, leaving only the most important decisions and +broadest view of the landscape to the central authority. Similarly, should a particular change be deemed to require a PEP, but the GUIDO, in consultation with the CoP, identifies experts that have @@ -128,6 +128,10 @@ the advocates of the change, but with the health and well-being of all community members in mind. A toxic discussion on a dead-end proposal does no one any good, and they can be terminated by fiat. +To sum up: the GUIDO has the authority to make a final pronouncement +on any topic, technical or non-technical, except for changing to the +governance PEP itself. + Authority comes from the community ================================== diff --git a/pep-8011.rst b/pep-8011.rst index ed75c8bbe..a9ae8a028 100644 --- a/pep-8011.rst +++ b/pep-8011.rst @@ -65,6 +65,19 @@ Roles and responsibilities of the leadership trio Just as Python looks at and learn from other communities for inspiration, other communities will look at Python and learn from us. + +Authority of the trio +===================== + +To be clear, in case any dispute arises: the trio has the final +authority to pronounce on PEPs (except for the governance PEP), to +decide whether a particular decision requires a PEP, and to resolve +technical disputes in general. The trio's authority does not include +changing the governance itself, or other non-technical disputes that +may arise; these should be handled through the process described in +PEP 8001. + + What are NOT considered as the role responsibilities of the trio ================================================================