Python Gets a New Governance Model
Jake Edge (via Hacker News):
There were six Python Enhancement Proposals (PEPs) under consideration that would be ranked by voters in a two-week period ending December 1; instant-runoff voting would be used to determine the winner. In the interim, though, much of that changed; the voting period, winner-determination mechanism, and number of PEPs under consideration are all different. But the voting concluded on December 16 and a winner has been declared; PEP 8016 (“The Steering Council Model”), which was added to the mix in early November, came out on top.
[…]
As with most of the other proposals, PEP 8016 creates a council. Various sizes were proposed in the other PEPs, but the steering council of PEP 8016 consists of five people elected by the core team. The definition of the core team is somewhat different than today’s core developers or committers. The PEP explicitly states that roles other than “developer” could qualify for the core team. Becoming a member of the team simply requires a two-thirds majority vote of the existing members—and no veto by the steering council.
Previously: Guido van Rossum Steps Down as Python BDFL.
2 Comments RSS · Twitter
> In exceptional circumstances, it may be necessary to remove someone from the core team against their will. (For example: egregious and ongoing code of conduct violations.)
Big open source projects have been using CoCs to enforce political correctness and purge contributors. Python's CoC doesn't appear to be like the cancerous one making the rounds, but who controls the wording of that document?
