Text of peps.python.org › pep-8015 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 8015 – Organization of the Python community | peps.python.org

PEP 8015 – Organization of the Python community PEP 8015 – Organization of the Python community Author : Victor Stinner Status : Rejected Type : Informational Topic : Governance Created : 04-Oct-2018 Table of Contents Abstract PEP Rejection Rationale Common Guidelines Community Organization Python Users Python Contributors Python Teams Python Core Developers Promote a contributor as core developer Python Steering Committee Python Steering Committee Roles Election of Python Steering Committee Members Election Creating the Python Steering Committee Members Special Case: Steering Committee Members And PEPs PSF Code of Conduct Workgroup Charter Special Case: Ban a core developer PEP process Vote on a PEP Lack of Decision Change this PEP Annex: Summary on votes Annex: Examples of Python Teams Packaging Team IDLE Team Mentorship Team Documentation Team Security Team Performance Team Asynchronous Programming Team Type Hints Team Version History Copyright Abstract This 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 Steering Committee” of 5 members which has limited roles: basically decide how decisions are taken, but don’t take decisions.

PEPs are approved by a PEP delegate or by a vote (reserved to core developers, need >= 2/3 majority). PEP Rejection PEP 8015 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. Rationale This PEP describes the organization of the whole Python development community, from Python users to the Python Steering Committee.

Describing all groups and all roles in the same document helps to make the organization more consistent. The number of governance changes is minimized to get a smooth transition from the old BDFL organization to the new Steering Committee organization. One key design of the organization is to avoid decision bottlenecks. Discussions and decisions are distributed into Python teams where experts in each topic can be found.

The expectation is smoother discussions on PEPs: fewer people with better knowledge of the topic. Previously, most decisions have been taken by the Benevolent Dictator For Life (BDFL), Guido van Rossum. The growing popularity of Python increased the pressure on a single person. The proposed organization distributes decisions and responsibilities to reduce the pressure and avoid wearing any individual down. To keep most of the decision power within the hands of the community, the Python Steering Committee has very limited roles.

The idea is to reduce the risk that a group of people or companies “takes over” the Python project through just a couple individuals. The project must remain autonomous and open to everybody. The most sensitives PEPs are decided by democracy: a vote reserved to core developers, see the PEP process section below for the voting method. Common Guidelines The Python community is open to everyone. Members must respect the Python Community Code of Conduct which ensures that discussions remain constructive and that everybody feels welcomed.

Python is and will remain an autonomous project. People with decisions power should reflect the diversity of its users and contributors. Community Organization Right now, there are different group of people involved in the Python project. The more involved you are, the more decisions power you get. It is important that the people acceding to the deepest group are the most trusted ones. This PEP formalizes the following groups: Python Users Python Contributors Python Teams Members Python Core Developers Python Steering Committee Members PSF Code of Conduct Workgroup Python Users This is the largest group: anyone who uses Python.

Python Contributors Once a Python user sends an email to a Python mailing list, comments on the Python bug tracker, proposes or reviews a Python change, they become a Python contributor. Python Teams Python became too big to work as a unique team anymore, people naturally have grouped themselves as teams to work more closely on specific topics, sometimes called “Special Interest Group” (SIG). When enough developers are interested by a specific topic, they can create a new team.

Usually, the main action is to ask the Python postmaster to create a new “SIG” mailing list, but the team can choose to use a different communication channel. Team members are Python contributors and Python core developers. The team is self-organized and is responsible to select who can join the team and how. Team members can get the bug triage permission on the team bug tracker component. The more involved in a team you are, the more decisions power and responsibilities you get.

A team might become allowed to decide on their own PEPs, but only the Python Steering Committee can allow that (and it has the power to revoke it as well). Such a case is exceptional, currently a single team has such permission: the Packaging Team. See Annex: Examples of Python Teams . Python Core Developers One restricted definition of a core developer is the ability to merge a change (anywhere in the code) and have the bug triage permission (on all bug tracker components).

Core developers are developers who are proven to have the required skills to decide if a change can be approved or must be rejected, but also (and this is more important) what changes should not be made. Python has a long history, big constraints on backward compatibility, high quality standards (ex: changes require new tests). For these reasons, becoming a core can take several months or longer. Becoming a core developer means more responsibilities.

For example, if a developer merges a change, they become responsible for regressions and for the maintenance of that modified code. Core developers are expected to be exemplary when it comes to the Code of Conduct. They are encouraged to mentor contributors. Promote a contributor as core developer Once an existing core developer considers that a contributor is ready to join the core group, to become a core developer, that core developer asks the contributor if they would like to become a core developer.

If the contributor is interested in such new responsibilities, a vote is organized. The vote is reserved to core developers, is public, and is open for 1 week. Usually the core developer who proposes the promotion has to describe the work and skills of the candidate in the description of the vote. A contributor is only promoted if two thirds ( >= 2/3 ) of votes approve (“+1”) the promotion. Only “+1” and “-1” votes are accounted; other votes (ex: null, “-0”, “+0.5”) are ignored.

If the candidate is promoted, usually they get a mentor for 1 month to help them to handle new responsibilities. If the candidate is not promoted, a new vote can be organized later, when the candidate gets the missing skills, for example 6 months later. Python Steering Committee The Python Steering Committee is made of the most trusted core developers since it has the most decision power. The roles of this group are strictly limited to ensure that Python keeps its autonomy and remains open.

The Python Steering Committee is composed of 5 members. They are elected for 3 years and 1/3 is replaced every year (first year: 1, second year: 2, third year: 2). This way, a member will stay for one full Python release and the committee composition will be updated frequently. A committee member can be a candidate for the seat they are leaving. There are no term limits. Committee members must be Python core developers.

It is important that the members of the committee reflect the diversity of Python’ users and contributors. A small step to ensure that is to enforce that only 2 members (strictly less than 50% of the 5 members) can work for the same employer

The rest of this page is on the live site.