The standards that underpin GOV.UK Verify have always been open but we started coding as a private project. Here’s a recap of our journey to coding in the open.
The Government Digital Service hosted an event for developers as part of the Global Day of Code Retreat. Find out what we did and why we set them an impossible challenge.
The cross-government event covered challenges the public sector needs to think about when considering the use of blockchain, voice assistants and artificial intelligence.
The cross-government open source meetup addressed common barriers to coding in the open, from hacking fears to licensing confusion.
At the Government Digital Service we've stopped using spreadsheets and software-as-a-service tools to manage our rotas and built our own app. We've open sourced the code, so you can use it too.
GitHub plays a major role in the software supply chain at GDS. All our source code is stored in GitHub - mainly in Alphagov - and we work hard to make sure our repositories are secure.
Every digital service designed within government has to meet the Digital Service Standard. One of the requirements of the standard is that new source code should be made open and published under an open source licence.
As part of the GDS commitment to code in the open, we have opened up GOV.UK’s application deployment code. This came with a number of challenges but it increased the development team’s efficiency and collaboration. Find out why we opened …
There are two big concerns government organisations have around making source code open. They want to know which subsets of the code should be kept closed and how to code in the open securely. To address these questions I’ve introduced two pieces of …
As technical writers at GDS we create technical documentation which includes instructions and supporting content for the products we build. We want to make our documentation consistent across all products, but also make it easier to work closely with our …