Text of peps.python.org › pep-8012 as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

PEP 8012 – The Community Governance Model | peps.python.org

PEP 8012 – The Community Governance Model PEP 8012 – The Community Governance Model Author : Łukasz Langa <lukasz at python.org> Status : Rejected Type : Informational Topic : Governance Created : 03-Oct-2018 Table of Contents PEP Rejection Abstract Rejected Models Let’s have another BDFL Challenge: There is no other Guido Risk: Malevolent Dictator For Life Observation: We don’t actually need a Dictator Risk: The warm and fuzzy feeling of a vague proposal Let’s have a Council Risk: Dilution and confusion Risk: Internal Conflict Motivation Rationale Specification Key people and their functions The core team Experts Moderators Regular decision process Controversial decision process PEP, Enhanced Very controversial PEPs Revisiting deferred and rejected PEPs Other Voting Situations Nominating a new core developer Votes of no confidence Voting Mechanics Omissions Acknowledgements Copyright PEP Rejection PEP 8012 was rejected by a core developer vote described in PEP 8001 on Monday, December 17, 2018.

PEP 8016 and the governance model it describes were chosen instead. Abstract This PEP proposes a new model of Python governance based on consensus and voting by the Python community. This model relies on workgroups to carry out the governance of the Python language. This governance model works 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. Should this model be adopted, it will be codified in PEP 13 . This model can be affectionately called “The Least Worst Governance Model” by its property that while far from ideal, it’s still the most robust one compared to the others. Since avoiding issues inherent to the other models is a paramount feature of the Community Governance Model, we start the discussion a bit unusually: by rejecting the other models.

Rejected Models Let’s have another BDFL This seems like a very attractive idea because it’s a model we know. One Dictator to rule us all. Challenge: There is no other Guido There is no other single person with the unique skillset of Guido van Rossum. Such a person would need to have the technical, communication, and organizational experience to lead the project successfully. Specifically, the person would need to: set and articulate a cohesive long-term vision for the project; possess deep technical understanding of the runtime, the standard library, and the wider third-party library context; negotiate and resolve contentious issues in ways acceptable to all parties involved; have free time and possess the energy to sustain continuous involvement over periods of years.

Risk: Malevolent Dictator For Life What if we got somebody who is not as well suited for the position as our first Dictator? There are possible scenarios in which this could lead to severe consequences. The Dictator could gather insufficient trust due to missing technical depth, a “close” election, inconsistent vision, poor ability to deal with conflict or burnout, and so on. Given a controversial decision decided by the Dictator in a specific way, a Dictator with insufficient trust may cause a split within the project.

The Dictator setup invites lobbying concentrated on a single person. Unless that person is immune to leverage due to wealth, health, and a stable life situation, this poses risk of malicious actors steering the project from behind the curtain. Finally, the Dictator coming from a particular part of the community may put more weight on the needs and interests of that particular part of the user base, alienating others. Observation: We don’t actually need a Dictator The irony of the Dictator model is that it requires an election.

Better yet, we need an election to even decide on which governance model to use. If we are already able solve two problems of this gravity via the community process, why not keep using it for all subsequent decisions? Risk: The warm and fuzzy feeling of a vague proposal One last thing worth mentioning is that when a BDFL model is suggested, it’s easy to bypass the criticism above by not mentioning who the BDFL should be.

That way the hopeful reader can project their best expectations and wants onto the abstract BDFL, making the idea appear more attractive. This is a mistake. Without naming the BDFL in the model proposal we are not talking about a concrete model. We can avoid asking and answering the hard questions. We can imagine our best-case scenario, a candidate we’d like to serve the role. Omitting a name for the BDFL also puts the Community Model at an unfair disadvantage.

We already know the good, the bad, and the ugly of our core developer group. It’s no platonic ideal, no perfect sphere with no friction. In fact, we expect there to be a fair amount of friction and imperfections. Thus, to fairly assess the BDFL model proposal, dear reader, you should imagine the worst possible person within our team as that BDFL. A concrete human being. Imagine it’s me. Conclusion While this has been our history, without Guido, this model does not serve the best interests of the language into the future.

Let’s have a Council This group of people roughly shares the responsibilities of a Dictator. The group can also be called a Triumvirate, a Quorum, Elders, Steering Committee, and so on. Risk: Dilution and confusion This model favors a small group, between three and five people. That way it shares most of the criticism with the Dictator model, amplified. Having not one but, say, three people in position of power dilutes responsibility while still providing high risk of lobbying, insufficient trust, or alienating parts of the community.

Risk: Internal Conflict Additionally, having multiple people share the responsibility of governance creates ample opportunity for internal conflict, inconsistent long-term vision of the project, and multiplies the required continuous time involvement by its members (it’s no Quorum if they can’t “reach quorum” due to other time commitments). Just like with a frictionless spherical BDFL, reject ideas of Councils without considering how would it work for you if that Council consisted of three people you find inadequate for the role.

Imagine if I had two friends. Most importantly, just like with a Dictator, we don’t need a Council. By the time we had one, we would have already had two successful elections. Why not keep voting? Conclusion This model has similar risks like a Dictator, only worse. Motivation Now that we rejected the basics of other governance models, let’s talk why we even need a governance model on top of a loosely defined group of committers.

Stability and Reliability We want to prevent single committers from making wide-reaching changes that impact the future of the language or its usability. Coherent vision and backwards compatibility are important in any programming language, but they are doubly important for Python which is very dynamic (e.g. has very complex backwards compatibility implications). Diverse Uses of Python Moreover, Python is used by a diverse group of users, from school children through scientists to corporations with multi-million line codebases.

We want to include all our varied audiences. Vitality We want to avoid stagnation. Python is a mature project but it needs to keep evolving to stay relevant, both the runtime and the programming language. To do that, people interested in improving a particular part of the project should be able to do so without needless friction. But for substantial changes, we want some discourse and reflection to ensure the changes are wise.

Rationale Inclusive The Community Model is the most inclusive model. No single person or a small group of people is in a distinguished position of power over others. Contributors and any workgroups in this model are self-selecting. Pragmatic This model ensures no user gr

The rest of this page is on the live site.