Postgres community is one example to look at, that I can think of. Linux may be other, but I'm not intimately aware of its inner workings.

https://www.postgresql.org/community/ is a good start to get a feel of all things related to Postgres community.

You need a consensus driven culture with a final decision maker when that culture fails to reach a decision.

In the general case what you say is true. But look at the specific example of PEP 751 (the thread we’re in). Normally you’d designate some person who has to gain consensus and add the feature to python or to the standard library. Even if everyone isn’t on board, they’ll get on board when they upgrade python.

PEP 751 isn’t a python feature, it’s a feature that will be implemented by 3 projects - PDM, pip and uv. Consensus isn’t optional or nice to have, it’s necessary. If any of the 3 maintainers felt their needs weren’t met they wouldn’t have implemented it.

Some projects wait too long for consensus because they prioritise not rushing into a suboptimal solution or hurting people’s feelings. Sometimes it’s ok to just go ahead and implement something. Pep 751 is not one of those projects.

> PEP 751 isn’t a python feature, it’s a feature that will be implemented by 3 projects - PDM, pip and uv.

It's not so much a feature as a standard. And other tools will use it as well. I'm working on one of them. PEP 751 means I don't have to design the thing myself, and I can potentially share data with the tools you mentioned.

And it’s a good thing that they built a standard that has buy-in.

I’m pointing out that if they didn’t have your buy-in, the work would be dead on arrival.

Unlike a python feature like let’s say, typing - there’s no way it can be pushed through without 100% consensus.

Angular turned things around quickly. Corporate sure, but if you know anything about how Angular is used within Google that was a massive job.