It might cause those committing the code, building the tests, and writing the doco for other ASF projects to question whether their project is being justly managed. I only watch one ASF project, Apache Groovy, and it has a similar imbalance between fluff managers and grunt workers.

Although all 9 members of its PMC are committers, only 4 of them have ever committed code since Groovy joined the ASF via its incubator 18 months ago. The other 5 (i.e. chairperson Guillaume Laforge, Jim Jagielski, Roman Shaposhnik, Konstantin Boudnik, and Andrew Bayer) are all committers but have never committed any code in that time. I can't find any other technical contributions from them either. All 5 are also ASF members, whereas only 2 of the other 4 PMC members who do grunt work are ASF members.

There's 10 other committers in Groovy, most of whom are more active contributors than those 5 I named, and in my view have far more merit to be on the PMC than them. OCI, the company doing Grails consulting, a few weeks ago enlisted an active PMC member (Paul King) as an OCI consultant "to coordinate contributions to Groovy". If Groovy's governance at ASF doesn't radically change fast to give PMC voices to the people doing the actual work instead of those ASF politicians, OCI might tap into the discontent and "take over" in similar style to DataStax, or even fork it like LibreOffice.