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.
Point 8 of the Digital by Default Service Standard that we publish on GOV.UK says that source code for government services should be open and reusable, and our 10th design principle is "Make things open: it makes things better". We …
I’ve been working on a prototype of what a Platform as a Service (PaaS) for government might look like, as we wrote about in a previous post.
At GDS, most of our code is publicly available in our alphagov organisation on GitHub. We call this “Coding in the Open” rather than “Open Source”. As James explained in a previous blog post this is because for most of …
When I started working on vCloud Tools, we had most of our functionality in one repository. There wasn’t a clear separation of concerns – the code was tightly coupled – and it also meant that a user who only wanted …
We recently moved GOV.UK to a new and improved platform. We used vCloud Tools, open source software developed in-house at GDS, to create the virtual machines and networks required as well as configure the firewall, NAT rules and load balancers. Why …
Over the last few months, I’ve been leading a small team building tools to automate creation and configuration of our servers. Tools to automate provisioning Currently, our production environment is hosted with Skyscape, and we manage it using VMware vCloud …
GOV.UK