#systemhacks #hugesuccess

This brings us to the second part of our policy: When we build our own software or contract with a third party to build it for us, we will share the code with the public at no charge. Exceptions will be made when source code exposes sensitive details that would put the Bureau at risk for security breaches; but we believe that, in general, hiding source code does not make the software safer.

We’re sharing our code for a few reasons:

First, it is the right thing to do: the Bureau will use public dollars to create the source code, so the public should have access to that creation.

Second, it gives the public a window into how a government agency conducts its business. Our job is to protect consumers and to regulate financial institutions, and every citizen deserves to know exactly how we perform those missions.

Third, code sharing makes our products better. By letting the development community propose modifications , our software will become more stable, more secure, and more powerful with less time and expense from our team. Sharing our code positions us to maintain a technological pace that would otherwise be impossible for a government agency.

The CFPB is serious about building great technology. This policy will not necessarily make that an easy job, but it will make the goal achievable.

Luis Carvalho originally shared this post:

#opensource

I had to check a couple times if this was actually in the US… apparently, it is… WOW.

Digital Native Government Agency Embraces The Power Of Open Source | Techdirt

The Consumer Financial Protection Bureau is a young federal agency (founded in July 2011), and as such has a history of getting it when it comes to the digital world. They launched by taking online su…