I am in favour of the principle and certainly wouldn't oppose such legislation. However I think it's worth being aware that publishing and licensing the code on

I am in favour of the principle and certainly wouldn't oppose such legislation. However I think it's worth being aware that publishing and licensing the code only gets you an open-source project in the most narrow sense. To actually get meaningful benefit from it you need to design it with multiple use-cases and deployment models in mind, document it, and build a community around it. If you have a bunch of publicly-funded teams that are desperate to do that work but held back by rules saying their code has to be private then forcing it public is a huge win. But actually I think most such teams are just trying to get their project off the ground or keep it alive. If you make them publish the code they'll do so and then carry on developing an undocumented system that solves their exact usecase and none other, and is tightly coupled to their particular production environment. I think to really get open-source happening successfully you actually need to foster a culture that values and incentivises the extra work it entails. Nonetheless, this would be a great first step. So bravo!