We've followed a similar strategy recently with the constructor project (plus conda-standalone, conda-pack, menuinst). This led to an increase of maintenance velocity, because expert stakeholders outside of the conda maintainer team were enabled to contribute directly to the bootstrapping/installer story of conda.

conda-build is another pillar in the conda ecosystem that would benefit from more expert practitioners to more actively participate in the maintenance. There needs to be a balance struck between required maintenance ("keeping the lights on") and enabling new features ("building new shiny things").

The people I suggest adding to this team: