Benevolent dictator for life

Shortly after Van Rossum joined the Corporation for National Research Initiatives, the term appeared in a follow-up mail by Ken Manheimer to a meeting trying to create a semi-formal group that would oversee Python development and workshops; this initial use included an additional joke of naming Van Rossum the "First Interim BDFL". The title was initially coined as "Benevolent Dictator" by Ken Manheimer; later Barry Warsaw suggested it would be "Benevolent Dictator for Life".^[3]

In July 2018, van Rossum announced that he would be stepping down as BDFL of Python without appointing a successor, effectively eliminating the title within the Python community structure.^[4] That remains an unusual move. In 2025, Mastodon developer Eugen Rochko stepped down, transferring ownership to a non-profit structure.^[5]

BDFL should not be confused with the more common term for open-source leaders, "benevolent dictator", which was popularized by Eric S. Raymond's essay "Homesteading the Noosphere" (1999).^{[6][clarification needed]}

Among other topics related to hacker culture, Raymond elaborates on how the nature of open source forces the "dictatorship" to keep itself benevolent, since a strong disagreement can lead to the forking of the project under the rule of new leaders.^{[citation needed]} Most open source software development projects utilize distributed version control systems, in which contributors submit pull requests to the project's maintainer, who may merge or reject the submission. Other distributed copies of the software are then based on that maintainer's repo. The position of BDFL is a consequence of network effect; they become stewards of the overall project on account of being the repo that the rest of the community is subscribed to and submits changes to.

• Design by dictator