If you are missing any of those 3 things, then you can't get the block size increase in Core. At the moment, this is stalled at the convincing Wladimir J. van der Laan step. It isn't clear how many miners would adopt the version if Wladimir J. van der Laan approved it.
No it isn't, you're deliberately misconstruing the real situation. A blocksize increase has already been committed to the codebase, and it's not just Wladimir who has commit access.
So, Wladimir isn't preventing blocksize increases, and does not hold the sole veto, as you present it. Your presentation is inaccurate propaganda to bash Core.
To get an increase in some other implementation, you need:
- A developer to code the change
- Enough miners to run that implementation
If you are missing either of those 2 things, then you can't get the block size increase in other implementations. At the moment, this is stalled at getting enough miners to run the implementation. It's not clear how badly Core would need to fail before miners will abandon the Core code for some other implementation.
Explain to us about the way(s) in which Core is failing.