@evan that core maintainers must write more than 0% of the code.
I'm being unnecessarily sassy about it, but I subscribe to a software development lifecycle where writing as little code as possible (but no less) is a virtue.
If a project maintainer _merely_ maintains scope, plans release timelines, manages technical contributors, writes comms and documentation, enforces quality standards... that's plenty of software development.
Or from another perspective, a healthy project should still be viable if they lose core maintainers for whatever reason. If there's only one person who could possibly maintain part of the project that's a red flag.