Maintainers for desktop "critical infrastructure"

In a perfect world we would be able to get Google and Canonical on-board with the rest of the community and then would have plenty of resources to keep all the infrastructure well maintained and up to date with modern hardware. Google AudioFlinger vs. community PulseAudio and Google SurfaceFilinger vs. Canonical Mir vs. community Wayland are held apart not only for technical compatibility reasons but mainly due to (L)GPL license avoidance and ownership desires, Google and Canonical want to "own" their respective technologies and not have shared ownership a-la kernel.org Linux.