It's pretty clear what that means, it means there's no leaders. There are maintainers, but these people do not speak for or override the rest of the core developers. If you're curious how core development actually works there are plenty of how-to articles to help you because it seems you need to start from the beginning.

TY but I know exactly how it works, as you can see changes are aprroved/merged by the maintainers like I said, who have permissions to do so. The fact that you think there are no leaders just because there is a flow chart on how to submit PRs and think they don't have contact with anyone is naive, since there are owners of the repo/project, they also decide who gets what permissions on the repo. People need to get this in their head Core is not a democracy or decentralized. If Core maintainers decide to go against a community decision they can, they can and SHOULD be opinionated on what kind of implementation they want. It would make things clearer for everyone and push others to make their own node implementations, and that is what helps decentralization over node implementations. But back to to your OP check the link i shared.

I don't remember agreeing to increased OP return size, but it's a decentralized team of devs aka I'm not part of it so my vote doesn't matter 🤡.