...open source reusable code you should: ensure that code is opened as first priority when a new developer starts; if the repo is not public from the start there is...
...for this project to be coded in the open, with all code published on github.com in open repositories. Where this is not possible there should be a convincing explanation as...
...reflect the high data protection requirement. The source code was peer reviewed by GDS before being finalised by the supplier. At present security requirements are too entangled with the general...
...sensible manner. It is good that the team has pulled out ‘form-monkey’, a library for creating forms, from the core code base with plans to open source it. The panel...
...supplier would essentially mean starting from scratch, rather than having a code base that they own and can have someone else improve. The assessment panel recommends that the entire team...
...opening up the code they have developed. The use of widely adopted open source tools limit locking, and allow for future reuse/repurposing. The plans, agreed by the relevant BIS staff...
...publishing platform, which concerned the panel before confirming that the team are capable of making their own amendments to the codebase should GOV.UK’s roadmap change. Security is being considered well...
...with them to ensure that their non-repudiation requirements will be met. Coding in the Open The team are committed to open sourcing the code for the service from the outset....
...developers, the team cannot have confidence that the code delivered to web browsers works for service users on the devices and browsers they use, or in a way that is...
...target to meet, and will explore promotion of the digital service through key identified community groups in order to meet this target. Recommendations Research and user needs While the team...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.