Yikes. Python has become so hugely popular and is used for so many different use cases that I fear the ecosystem is going to really struggle to find consistency and direction without a dictator.
replies(2):
Each community could then form whatever organization they felt necessary to choose who to send to the triumvirate.
As as check on the power of the triumvirate, we could have something like a "Tribune of the Plebs" - a representative elected by open election from the entire community that holds veto authority over changes approved by the triumvirate.
The UN Security Council is somewhat similar in that respect, though comprised of more members. New matters are approved by majority vote, but the five permanent members can veto anything that gets approved.
My proposal is somewhat tongue in cheek, hence the names from the Roman Republic - but I do think the idea is sound.
An alternate, simpler implementation would be to simply require that all changes be unanimous. I like the idea of a Tribune of the Plebs though because it gives a second means of a voice should a sizable minority of members of the sub-communities strongly disagree with the direction of their representatives.
The current governance model is mostly around consensus on the dev list. There's a "technical board" elected every release cycle from among the committers, to act as a tie-breaker when needed, and with veto power over DEPs (Django's equivalent of PEPs) and adding new committers. I don't know of a case where that veto power has ever been exercised, FWIW.