@strypey depending on what you mean by AI, it's PLENTY locally practical 馃槉 And if it's not, well, that begs some questions about whether it's appropriate.
@strypey depending on what you mean by AI, it's PLENTY locally practical 馃槉 And if it's not, well, that begs some questions about whether it's appropriate.
Official NZ government code depository
1) set up an onshore code forge service, using a Free Code package like Forgejo or GitLab CE. Require that a copy of all Free Code used in govt systems is lodged in it, and kept up-to-date date with what's in production.
The admin team would be employed as permanent public servants. Kind of like a software ombudsman office.
(2/?)
Official NZ govt public code depository (cont'd)
2) After a transition period (eg 2-5 years), require vendors of proprietary software to put full source code in private repos in the code repository, for all software govt depends on. Any existing vendor who doesn't commit to this when the public code depository is announced needs to be replaced over the transition period.
(3/?)
Official NZ govt public code depository (cont'd)
3) After a further transition period (eg 5-10 years), all repos on the public code depository would be made public, under free licenses. Again, any existing vendor who doesn't commit to this when the public code depository is announced needs to be replaced over the transition period. Deleting their private repos from the depository when they code is no longer used in govt systems.
(4/?)
Other steps that could help us move towards 100% digital sovereignty in government IT systems;
Open Standards
Mandate support for vendor-neutral data exchange standards for all government software;
Again, a deadline needs to be set for this transition to be completed. With a series of steps from the easiest to the hardiest.
Require Export
Mandate that any software used in govt must be able to export all data, in vendor-neutral formats.
(5/?)
Software Commissioning
Mandate all software commissioned by public bodies, or paid for with public money or charitable grants, to be published under a free license. For software that's partially funded by public money, a threshold could be set above which publication of source code is mandatory. Eg more than 50%, or more than 80%.
This policy ought to be retroactive. So it apples to any software that can be shown to have been developed by public employees, or funded by public money.
(6/6)