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

Update description for PEP 8010

This commit is contained in:
Barry Warsaw 2018-11-05 11:16:21 -08:00
parent 5175b24a04
commit 8be46e7768
No known key found for this signature in database
GPG Key ID: 126EB563A74B06BF
1 changed files with 7 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
pep-8000.rst
View File

@ -35,21 +35,19 @@ governance model.
will have its own spin on governance, rather than directly adopting any of
those surveyed.
PEPs in the 8010s describe the actual proposals for Python governance. It is
PEPs in the 801Xs describe the actual proposals for Python governance. It is
expected that these PEPs will cover the broad scope of governance, and that
differences in details (such as the size of a governing council) will be
covered in the same PEP, rather than in potentially vote-splitting individual
PEPs.
* PEP 8010 - The BDFL Governance Model
* PEP 8010 - The Technical Leader Governance Model
This is a placeholder PEP for the continuation of the `Benevolent Dictator
For Life <https://en.wikipedia.org/wiki/Benevolent_dictator_for_life>`_
model. The name is an homage to Guido's title and does not necessarily
imply that the next BDFL will be required to serve without time limit. Also
within scope is whether an advisory council aids or supports the BDFL. This
PEP does *not* name either the next BDFL, nor members of such an advisory
council. For that, see PEP 13.
This PEP proposes a continuation of the singular technical project
leader model. Also within scope is whether an advisory council aids
or supports the BDFL. This PEP does *not* name either the next
BDFL, nor members of such an advisory council. For that, see PEP
13.
* PEP 8011 - Python Governance Model Lead by Trio of Pythonistas