CFPB Accepts First Citizen-Submitted Code on Behalf of Federal Government
“Fix typo.” Not quite “one small step for man,” but a significant first nonetheless. These simple words, typed by an open-source developer operating under the pseudonym “iceeey,” may represent the first collaborative effort between the federal government and the broader open-source community, and surely represents a tangible win for the open-government movement as a whole.
The Consumer Financial Protection Bureau (CFPB) is in a unique position. As the youngest federal agency, they have the opportunity to reimagine many day-to-day business processes for an internet era, and to share that innovation across government. One such process is the means by which federal employees apply for and receive subsidies to offset the cost of public transportation to and from work. Having created an application that alleviated the need to shuttle time-consuming, paper-based forms from building to building within their own agency, the Bureau sought to package up the solution, and publicly release the source code for other federal agencies to use and expand upon. The logic was simple: solve the problem once, solve it everywhere.
But the code was not simply made available for government employees to access. The code was placed on GitHub – a popular source code sharing service – for anyone to download and explore, and within days of CFPB publishing its recently announced Source Code Policy, someone did just that.GitHub user “iceeey” submitted a proposed change – known in developer parlance as “forking the project” and submitting a “pull request” — correcting a misspelling on the form initially presented to new employees (“roundtrip” was accidentally spelled “rountrip”).
Admittedly a minor change (“one small step for grammar?”), but notable for the underlying first that it represents: the opportunity to create efficiencies across government by partnering with the broader community of civically engaged developers.
Open-source software (software for which the underlying source code is made publicly available) as a vehicle for a more open and more efficient government is nothing new. Behind the scenes, countless agencies rely on open-source software for various business functions, and many have even chosen to publicly publish the source code underlying the applications that they themselves have built in-house to tackle unique challenges. But this seemingly innocuous missing “d” and its subsequently submitted fix represents the first time a federal agency has directly collaborated with open-source developers to better its own day-to-day tools.
Iceeey has already submitted his second pull request (“more typos” he joked with an emoticon smiley), and I hope more agencies and more open-source developers will follow suit. Such collaborations empower agencies to do more with less; put better, more robust tools in the hands of federal employees as they carry out agency mission; and undoubtedly represent a giant-leap forward for a more open and more efficient government.
If you enjoyed this post, you might also enjoy:
- Towards a More Agile Government
- Securing the Status Quo
- Why open source
- Twelve tips for growing communities around your open source project
- Five best practices in open source: external engagement
- Everything a government attorney needs to know about open source software licensing
- A White House open source policy written by a geek
- 19 reasons why technologists don't want to work at your government agency
- Eight reasons why government contractors should embrace open source software
- The difference between 18F and USDS
- Open source, not just software anymore
Ben Balter is a Staff Technical Program Manager at GitHub, the world’s largest software development network. Previously, as the Senior Product Manager overseeing the platform’s Trust and Safety efforts, Ben shipped more than 500 features in support of community management, privacy, compliance, content moderation, product security, platform health, and open source workflows to ensure the GitHub community and platform remained safe, secure, and welcoming for all software developers. Before joining GitHub’s Product team, Ben served as GitHub’s Government Evangelist, leading the efforts to encourage more than 2,000 government organizations across 75 countries to adopt open source philosophies for code, data, and policy development. More about the author →