iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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
This commit is contained in:
Nathaniel J. Smith 2018-11-30 19:23:48 -08:00 committed by Mariatta
parent ad3b078c20
commit 413f7f471c
2 changed files with 26 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
pep-8010.rst
View File

@ -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
==================================

13
pep-8011.rst
View File

@ -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
================================================================