No. I'm not being clear.
Hire eg IBM global services to build you the solution. In the contract it states clearly, part of the deliverable is the source code that will be published under xyz license. Whether you hire IBM, Oracle, Accenture etc or do something a lot less moronic you insist on source and insist on being assigned the copyright to it and you publish it. Every time. Always.
That's the step forward I am suggesting. Not the linux kernel model of development. If such a thing arose for particular projects, great. But it's not a requirement nor the goal.
Maybe my interpretation of your idea wouldn't work exactly as you has in mind, but I see your point, that maintaining greater control of the development process would likely lead to a more coherent and predictable product that functions in accordance with carefully designed specs.
Among flies in the ointment is the necessity for such a highly principled and skilled steering group to manage the effort with the requisite wisdom around scheduling releases and titrating the level of community involvement. The level of talent it implies is likely in short supply.
That said, an admiral proposal, distinctly possible, even revolutionary. To quote Spinoza, "all things excellent are as difficult as they are rare".