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.
Find out how we used the Payment Request API standard and how we managed encryption. We explain why we chose to use Apple’s JavaScript API and not use the Google Pay API.
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 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.
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.
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.
Today we’re handing over the maintenance of our Puppet::Syntax tool to an open source community group.
If you’re interested in jobs in this field, check out all open opportunities on the GDS careers site.