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...
...services under the new contracts we signed earlier this year. This includes the existing companies that are transitioning on to new contractual terms, and the new companies that will be...
...any new code. Our next release of new code will be in January. Over the next 2 weeks we plan to: prepare our next A/B test of the introduction pages...
...that we operate that help the federation to run smoothly and securely. This is also something that is considered under Point 6 of the Digital by Default Service Standard assessment...
...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...
...lab. The new content introduces the idea that GOV.UK Verify ‘is a new scheme to fight the growing problem of online identity theft’. The change has had a positive impact...
...do publish information about our design, but we don’t publish code that would reveal specifics about our implementation of the design. As James explains, 'we don’t publish information about the...
...reducing our technical debt. Here’s what we’ve been working on since the last update, and what we plan to do next. Increasing adoption of GOV.UK Verify We want departments across...
The GOV.UK Verify technical delivery team recently started building a new version of our frontend application (not the design - that will look the same as it does now). We...
...some objectives that explain what we are aiming to achieve within that timescale. These objectives will define our roadmap for moving from beta to live by April 2016. What ‘live’...