...source code to be made publicly available. Rather than making a judgement on what source code will be useful and reusable, the default approach should be to publish (sensitive information...
...code open and reusable. Although work is underway to make code from other components of the PAYE service available via a public GitHub it would be good to see code...
...functionality iterated until users can complete the prototype unaided and understand the process. Make source code open Defra owned source code being developed in-house by the service team should be...
...make it quicker to roll out updates and improvements. Point 15 - Make all new source code open and reusable, and publish it under appropriate licences (or give a convincing...
...code open and reusable- point 15 The service team should continue the work to open their source code. Testing the end to end service - Point 17 Ensure the service...
...panel were glad to see that improvements had been made since Alpha. The team have immediate plans to open up validation engine code, to support the external software providers, who...
...and constantly improving the service. A strong commitment to open sourcing the code (with all code being placed on Github), as well as to open data with each page being...
...place to make all new source code (or specific subsets of the source code) open and reusable. The panel expect evidence of this to be demonstrated at the beta assessment....
...code open and reusable The team have a plan to open source the subsets of the code they are able to. We encourage them to do this sooner rather than...
...also not passed point 8 – although there are plans to share code within DVLA, and the team expressed a willingness to make its source code open and reusable, there...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.