Releasing safe and useful code for GOV.UK Verify
...to why this cannot be done for specific subsets of the source code). This post is about how we’re going to open up our code. It explains what we’ve opened...
...to why this cannot be done for specific subsets of the source code). This post is about how we’re going to open up our code. It explains what we’ve opened...
...published We made the first small step towards opening up our codebase this year when we published a small module of code. There is a lot more to come in...
...The codebase for GOV.UK Verify is mainly java microservices at the backend. At the frontend we use Jade as our templating language. However, we’re currently rebuilding the frontend of the...
...in our codebase and allow us to deploy new code faster Things we plan to do next Over the Christmas period we have a change freeze and are not deploying...
...app to generate a security code or to receive a security code on your landline phone, rather than waiting for a text to arrive, so you don’t need a mobile...
James Stewart has published a post about how GDS decides when it's ok not to publish source code. The identity assurance programme operates within the approach outlined by James. We...
...look that takes us to live in April 2016, and beyond. Current status Thirteen of the services we listed as starting to use GOV.UK Verify early this year are now...
...added to the list, some have moved to an earlier connection date and some have moved later, as we would expect. Table: updated list of services we expect to start...
...towards the end of last year. Reducing our technical debt There are things we need to do to the GOV.UK Verify codebase to tidy up accumulated impact of having made...
...external bodies, such as the Privacy and Consumer Group (PCAG). When you use GOV.UK Verify, you choose from a list of certified companies. In order to verify that you are...