What’s Missing from CFPB’s Awesome New Source Code Policy
TL;DR: The Consumer Financial Protection Bureau’s (CFPB) new open source policy is a great start, but should go further
Most often, when we talk about open source in government, it’s talked about in one of two ways: either it’s the pitfalls of the federal IT procurement model that can’t seem to comprehend a world in which open-source is an option, much less potentially a superior choice (“acquisition as a roadblock”), or it’s reiterating the same open-source talking points that haven’t seemed to give open source much parity with the wall of organizational inertia proprietary software seems to have gained over the years (“open source as an alternative”).
The Consumer Financial Protection Bureau (CFPB), however, is in a unique position. As the newest kid on the block, it’s one of the few government agencies to have been born in a digital era, and more importantly, without the bureaucratic baggage that all too often stymies innovation. They have a chance to “do it right” from the start… and they’re doing just that.
An Agency Born of the internet Generation
Yesterday, CFPB announced a bureau-wide preference for open source in its shiny new Source Code Policy, by my crude research, a first for any government agency. There are two watershed shifts here: first, that the agency not only should, but must evaluate open source software on equal footing to its proprietary counterparts, a comparison which I believe will increasingly fall in open source’s favor, and second, that unless there’s an overriding security or similar concern not to, public code must be public. There’s nothing new here. All it says is that we should use the best software for the job (a no-brainier), and that the software, the public’s property, should belong to the public.
So why is this news? Plenty of government entities have released source code, or encouraged theuse of open-source software. But no one has come out and plainly stated that they were an “open-source agency”, that open source is the new default, and that absent an affirmative step by some naysayer, that the public will have access to their code. That’s huge. It’s flipping the burden, and it’s the way things should be from the start.
But Where’s the Beef
That said, there’s one thing the source code policy is noticeably silent on: the ecosystem. Posting code is great and it’s great that they’ve done the legal legwork so other agencies can follow suit, but that’s just the 1.0. The true power of open source comes not from simply publishing code, but from being a member of a broader coding community. Can a CFPB employee contribute a patch to an existing open source project on CFPB time? 1 What about contributing to a CFPB project once he or she’s left? What happens to my rights when I fork a CFPB project on GitHub and send the agency a pull request? 2 Can the agency even accept my code legally? 3 There’s a lot of legal ambiguity there, and it’s just the kind of legal ambiguity a well-intentioned government attorney can seize upon to gum up the very gears that are driving this incredible move.
We’ve seen the same progression in the open data world. The 1.0 is posting 10 XML files at a gigabyte each — an arms-length relationship with developers — arguably open data simply for open data’s sake. The secret sauce lies in the relationship, in publishing APIs and web services rather than static data, to build an ecosystem around the agency’s work.
An Innovation Ecosystem
Imagine if government agencies served as the catalyst for a joint public-private effort to drive tomorrow’s innovation. We saw this during the space race, and see it today in terms of government-funded research, but by-and-large, open-source coders have yet to be included. Sure we’ve seen the “let’s have some open-source developers build this for us for free” type challenges, but that’s about it. There’s no ecosystem, no community, no push-pull or give-and-take, and I’m worried that as CFPB’s efforts federate across government, this nuance may not federate along with it.
The agency’s already got it’s first public-generated code contribution, and can expect at least one more on their gist of the policy (Ed. note: does CFPB not own a Blue Book?!), but the possibility of such a relationship with the citizenry doesn’t seem contemplated by the policy, let alone included as integrally as it should.
I’d love to see the next iteration of the policy have a third section, “III. Membership in the Open-Source Community” on not just publishing code they’ve developed in house — don’t get me wrong, that’s huge — but actually contributing meaningful code to the broader ecosystem, and working directly with the open-source community to foster an active partnership that delivers the best citizen services possible. It’s a dialog, not a code dump. There needs to be a conversation there.
Procure, Publish, Participate
It’s the realization that when you use open-source software, you’re not a customer. You’re a member of a community. You’re invited to a pot-luck dinner. There’s not the same sense of entitlement you have with proprietary software. It’s not that they owe you a given feature. There’s no financial transaction there. It’s that the feature hasn’t been developed yet, but can be, the same way every other feature has evolved, through community contributions. There’s an entirely different philosophy driving the relationship.
For open source in government to work, it’s got to move beyond procuring community contributed open-source projects on the one hand, and releasing open-source code developed in house distinctly on the other. It’s about feeling a sense of belonging. It’s about the agency taking on a sense of ownership in the broader project. It’s about participation. 4
I think CFPB gets it in a big way, and the fact that this is memorialized in writing is a major step in the right direction. They’ve got the basic mechanics down — procure open–source projects, publish open-source code — but the missing secret sauce that would really drive the policy home? Participate in the open-source community as a matter of policy.
+1 CFPB, +1. Welcome to the community.
In simple terms, the core of open-source projects (as distinct from community-contributed plugins or modules) are primarily fueled by “patches” (small code change sets) in response to bugs or feature requests, that get committed to the project’s codebase and released in subsequent versions. ↩
If the project is licensed as government work, are my code contributions now government work? Are the government employee lines of code under a broader license, while mine are under a more restrictive license like GPL or Apache? ↩
Is this considered a donation for Federal ethics purposes thus requiring disclosure? ↩
This can manifest itself in lots of different ways, but most tangibly: going to local meetups and conferences (or hosting them); contributing to the project’s core by introducing new features, documentation, or posting to support forums; abstracting business logic from the start to be more broadly applicable to other developers; outreach and evangelism; and fostering relationships with key stakeholders within the community ↩
If you enjoyed this post, you might also enjoy:
- Why open source
- Five best practices in open source: external engagement
- Everything a government attorney needs to know about open source software licensing
- Twelve tips for growing communities around your open source project
- 19 reasons why technologists don't want to work at your government agency
- Everything an open source maintainer might need to know about open source licensing
- The difference between 18F and USDS
- Why you probably shouldn't add a CLA to your open source project
- A White House open source policy written by a geek
- 15 rules for communicating at GitHub
- Why you shouldn't write your own open source license
Ben Balter is the Director of Engineering Operations and Culture at GitHub, the world’s largest software development platform. Previously, as Chief of Staff for Security, he managed the office of the Chief Security Officer, improving overall business effectiveness of the Security organization through portfolio management, strategy, planning, culture, and values. As a Staff Technical Program manager for Enterprise and Compliance, Ben managed GitHub’s on-premises and SaaS enterprise offerings, and 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 →