18F/18f.gsa.gov

---
title: Open source for good government
date: '2015-01-16'
layout: post
image: /assets/blog/join-us/18f_govuk.png
hero: false
tags:
- open source
- gov.uk
- how we work

authors:
- 18F

description: 'Organizations like 18F and the U.K.’s Government Digital Service (GDS) fully embrace open source, and their combined commitment to openness and transparency is transforming the delivery of government digital services in both countries.'

excerpt: 'Organizations like 18F and the U.K.’s Government Digital Service (GDS) fully embrace open source, and their combined commitment to openness and transparency is transforming the delivery of government digital services in both countries.'
---
<img src="{{ site.baseurl }}/assets/blog/join-us/18f_govuk.png" alt="18F and GDS logos">

A common misconception of open source is that it is just a licence for using software. For individuals and organizations involved with open source projects, it is a philosophy of openness and collaboration embedded in the project from idea to launch. Whether it’s designing an interface, or deploying an application, open source is fundamental to everything we do. Organizations like 18F and the U.K.’s Government Digital Service (GDS) fully embrace open source, and this commitment to openness and transparency is transforming the delivery of government digital services in both countries.

GDS [set the standard](https://www.gov.uk/service-manual/making-software/open-standards-and-licensing.html) for this. By implementing open standards for software interoperability, data and document formats, government is:

* improving adaptability and the ability for government to provide services based on users’ needs – avoiding digital exclusion based on the technology choices made;
* putting in place a level playing field for open source and proprietary software, giving government the ability to move between different technologies without the risk of lock-in;
* making it easier to share appropriate data across and beyond government boundaries, providing efficient services for users and delivery partners;
* making the cost of government’s digital services more sustainable by making things simpler and encouraging reuse.

We then built upon it as part of [our own open source policy](https://18f.gsa.gov/2014/07/29/18f-an-open-source-team/):

1. Use Free and Open Source Software (FOSS) in our projects and to contribute back to the open source community;
2. Create an environment where any project can be developed in the open; and
3. Publish all source code created or modified by 18F publicly.

Earlier this week, we [shared a tool](https://18f.gsa.gov/2015/01/13/an-open-source-tool-for-easier-database-testing/) built by an 18F team member that helps developers test their products with a small portion of their own datasets. Open source projects allow developers like Catherine to share solutions rather than re-solve the same problem over and over. Our readers were excited at the prospects:

<center><blockquote class="twitter-tweet" lang="en"><p><a href="https://twitter.com/18F">@18F</a>  Cool - I hand-wrote something like this at my previous job, but generalized OSS is much better! <a href="https://twitter.com/acdha">@acdha</a> <a href="https://twitter.com/catherinedevlin">@catherinedevlin</a></p>&mdash; Jamie McCarthy (@jamiemccarthy) <a href="https://twitter.com/jamiemccarthy/status/555498540466593793">January 14, 2015</a></blockquote>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script></center>

Since our launch in March, we have had a number of informal conversations with our counterparts at GDS on a host of issues – technical, policy, and operational – further strengthening our relationship and fostering our open collaboration.

Both teams believe that transparency in our operations [from day one](https://18f.gsa.gov/2014/07/31/working-in-public-from-day-1/) is key to creating the best possible products, and we look forward to future collaboration with GDS, other government organizations, and the public.