What happened
Bounded success. Core developers adopted a successor decision structure and elected its first council. Authority moved from one final decision-maker to an elected body, while the electorate remained the core developer community rather than every Python user.
- Van Rossum’s resignation said he would leave the decision process, remain available as a core developer, and not choose a successor. Transfer of power
- The adopted proposal provided a five-member council, core-team voting and safeguards against one employer dominating the council. PEP 8016: The Steering Council Model
- The first election drew 69 ballots from 96 eligible voters and elected five members, including van Rossum. PEP 8100: January 2019 Steering Council election
What might explain it
Plausible
An established contributor community may be able to redistribute final authority while preserving routine production. Transfer of power PEP 8100: January 2019 Steering Council election
Alternative explanation: Continuity may depend more on pre-existing maintainers and mature technical processes than on the council design.
Plausible
Keeping the founder involved without exclusive final authority may preserve knowledge while reducing dependence on one person. Transfer of power PEP 8100: January 2019 Steering Council election
Alternative explanation: Informal influence might remain concentrated even after formal powers are redistributed; election results do not measure actual deliberative influence.
Questions to take into practice
- Identify which decisions truly depend on the founder before redesigning every role.
- Specify electorate, replacement procedures, and employer conflicts before a vacancy becomes urgent.
What remains uncertain
- The transition settled who formally held final authority. How far informal influence changed, and whether contributors found later decisions better or more satisfactory, require attention to the council’s subsequent practice.