Benevolent Dictator For Life引退後のPython（前編）

Pythonの生みの親であるGuido van Rossumが仕様策定から引退するというニュースが流れてしばらくたつが、その後、どうなったのだろう？

2018年9月以前のPEP1は、こう書かれていた。

There are several references in this PEP to the "BDFL". This acronym stands for "Benevolent Dictator for Life" and refers to Guido van Rossum, the original creator of, and the final design authority for, the Python programming language.

2018年10月にGuidoの引退に伴いPEP1が書き換わる。githubのhistoryを追ってみよう。

Remove Guido from list of PEP editors and add note about future gover窶ヲ ツキ python/peps@f6abb96

BDFLはvacant（空席）であるという注釈が付き、どう空席を埋めるかはPEP-8000で提案がされる。

PEP 8000 -- Python Language Governance Proposal Overview

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.

801Xと呼ばれるガバナンスモデルが提示され、投票によって決められることになった。６つのモデルは、こんな感じだ。

PEP 8010 - The Technical Leader Governance ModelThis PEP proposes a continuation of the singular technical project leader model. Also within scope is whether an advisory council aids or supports the BDFL. 

ひとつめの案は単一のリーダーのcontinuation（継続）を提案する。PEP8010を詳細に読むと、ビジョンを推進するには評議会よりリーダーという考えのようだ。

PEP 8011 - Python Governance Model Lead by Trio of PythonistasThis PEP describes a new model of Python governance lead by a Trio of Pythonistas (TOP). It describes the role and responsibilities of the Trio.

ふたつめの案はトリオ、つまり3人を指名しようというもの。

PEP 8012 - The Community Governance ModelThis is a placeholder PEP for a new model of Python governance based on consensus and voting, without the role of a centralized singular leader or a governing council. It describes how, when, and why votes are conducted for decisions affecting the Python language. It also describes the criteria for voting eligibility.

8012はコンセンサスと投票に基づくモデルで単一のリーダーや評議会を持たない。

PEP 8013 - The External Governance ModelThis PEP describes a new model of Python governance based on an external council who are responsible for ensuring good process. Elected by the core development team, this council may reject proposals that are not sufficiently detailed, do not consider all affected users, or are not appropriate for the upcoming release.

PEP8013は外部の評議会を持つモデル。評議会メンバはコア開発者によって選出され、不適切な提案を却下する権限を持つ。

PEP 8014 - The Commons Governance ModelThis PEP describes a new model of Python governance based on a council of elders who are responsible for ensuring a PEP is supported by a sufficient majority of the Python community before being accepted. Unlike some of the other governance PEPs it explicitly does not specify who has voting rights and what a majority vote consists of. In stead this is determined by the council of elders on a case by case basis.

PEP8014はelder（長老）の評議会。

PEP 8015 - Organization of the Python communityThis PEP formalizes the current organization of the Python community and proposes 3 main changes: formalize the existing concept of "Python teams"; give more autonomy to Python teams; replace the BDFL (Guido van Rossum) with a new "Python board" of 3 members which has limited roles, mostly decide how a PEP is approved (or rejected).

8015はPythonチームのコンセプトをformalizeし、BDFLを3人によるPythonボードに置き換える。

PEP 8016 - The Steering Council ModelThis PEP proposes a model of Python governance based around a steering council. The council has broad authority, which they seek to exercise as rarely as possible; instead, they use this power to establish standard processes, like those proposed in the other 801x-series PEPs. This follows the general philosophy that it's better to split up large changes into a series of small changes that can be reviewed independently: instead of trying to do everything in one PEP, we focus on providing a minimal-but-solid foundation for further governance decisions.

PEP8016はsteering council（運営評議会）によるもの。

さて、選ばれたのはどのモデルだろうか。投票の結果は明日に。