...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...
...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...
...code open and reusable, and the team told us that DVLA as a whole is now proposing to adopt this process. The process will include additional controls, reflecting the organisation’s...
...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...
...was standardised (e.g. 'Epsom & Ewell' was always named 'Epsom and Ewell'), an 'ONS name' table was imported into the database too. This table contained local authority names, ONS codes...
...understand and comment on. We decided to use Jupyter Notebook to document our experiments, because it allows us to write both code and free-form text, and expose the notebook via...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.