...the design and design changes (as a result of feedback/data analysis) can be delivered quickly. 2. Implement plan to separate secret code separate from platform and publish non-sensitive code as...
...take-up of the service properly extrapolated. 16. Make all new source code open and reuseable, and publish it under appropriate licences (or provide a convincing explanation as to why this...
...the online service independently. The service team must give early consideration to how they will open the source code for the Service to ensure that any small parts of code...
...etc. Open Source Code The panel were encouraged to hear HMRC are making progress in this area, but we are still yet to see any service code published. Publishing source...
...overall cost per apprenticeship filled, or a similar metric would be a useful additional key performance indicator for the service. The service is in two parts (finding apprenticeships and applying...
...have yet to make all new source code open and reusable, and publish it under appropriate licences. This needs to happen or the team need to provide a suitable explanation...
...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...
...All new source code is open, re-useable and published under an appropriate licence wherever possible. Recommendations Service design & GOV.UK style The team needs to address front-end development style; services...
...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...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.