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 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.
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 …
Technical Writer on Standards and Assurance, Khidr Suleman attended the cross-government Open Source meetup in London organised by GDS. Here’s a recap of the day’s events...
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 …
We are hosting the second cross-government meetup on Open Source in London on Tuesday 26th September.
Writing about the work they did in March, David and Robin talk about the benefits of coding in the open.
As an Open Source community member, you are responsible for handling any security issues you identify. This post provides an example of a security issue we encountered and resolved by working with the project security team.