...intend to make the source code for the service available. Doing this earlier rather than later makes it considerably easier. In particular, be aware of separating out configuration from implementation,...
...code from the Alpha so that other people could learn from it and that the team had a clear policy of open by default for the beta code, with a...
...aspects to the code, so effort should be made to code in the open and share as much as possible with the rest of DWP, government community and third parties....
...convincing explanation as to why this can’t be done for specific subsets of the source code). Code from the service has been published and is currently being reused by another...
...see all code open sourced, regardless of usefulness to a wider audience or not. The only exceptions are configuration management code, code that contain sensitive information (e.g. fraud detection components)...
...code, code that contains sensitive information (e.g. fraud detection components) or can pose a security risk if open. Publishing the source code will be a mandatory requirement when the service...
...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.