We’re currently working to add a new point on sustainability to the Technology Code of Practice. We’re adopting a user-led and iterative approach to policy to ensure the new point is as useful and effective as possible.
The Government Digital Service (GDS) recently hosted a remote GraphQL workshop for around 70 people from across government. Here are the main talking points from the event.
The Cyber Security team at GDS discovered it was using a vulnerable container. Here’s how the team fixed the issue and made its clean container publicly available.
The Government Digital Service (GDS) has created an API catalogue on GitHub to increase transparency across government, start conversations and improve data sharing.
The GDS Reliability Engineering team had to find some inventive workarounds to get the Alertmanager open source software package working on a managed container service. Here’s a detailed look at how we did it.
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 …