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.
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 …
If you’re interested in jobs in this field, check out all open opportunities on the GDS careers site.