What the Open Government Directive Means for Open Source
On the heels of the Open Government Memo of January 21st, 2009, the Obama Administration has issued the Open Government Directive. The Directive tells agencies what they must do to meet the expectations set by the Memo. The directive names many deadlines for agency compliance, most of them around reducing FOIA backlogs and increasing the amount of agency data released to the public. This isnâ€™t surprising, since the Memo names transparency, collaboration, and participation as the guiding principles. Transparency is the easiest to articulate and implement â€” just get the data out there in a useful form. Josh Taubererâ€™s Open Data is Civic Capital: Best Practices for â€œOpen Government Dataâ€ is an excellent handbook for doing this. If you want to track agenciesâ€™ progress, the Sunlight Labs folks have produced the outstanding Open Watcher.
Whatâ€™s most interesting to me, and my friends at Open Source for America, though, are the more ambiguous orders. Although the Directive does not use the phrase â€˜open source softwareâ€™ at all, many of the principles and methodologies described are obvious references to open source. Many of these orders stand out as opportunities for open source developers, in the public and private sector, to demonstrate how our development model can help the Administration also make good on the last two principles: collaboration and participation. As Macon Phillips, the White House New Media Director said, â€œOpen Source isâ€¦ the best form of civic participation.â€
Letâ€™s take a look at the deadlines, helpfully produced by Daniel Schuman at the Sunlight Foundation.
45 days â€” January 22, 2010
â€œEach agency shall identify and publish online in an open format at least three high-value data sets and register those data sets via Data.govâ€ (p.2)
This is a wonderful opportunity for open source developers to demonstrate the power of citizen participation through software. The Administration has taken a great risk by pushing this data to the public. There are all kinds of reasons to not do it: privacy concerns, security issues, and the risk-averse culture in most of these organizations. Despite the instructions to be careful with citizensâ€™ privacy, and the reminder to be sensitive to security issues, thereâ€™s still a chance that something could go wrong â€” plenty of reason to not follow through with this exercise. We need to help the Administration prove that this was a worthwhile cause. Just as we showed the power of citizen programmers in Apps for Democracy and Apps for America, we need to take these data sets and make them useful to the American public.
â€œThe Deputy Director for Management at OMB, the Federal Chief Information Officer, and the Federal Chief Technology Officer will establish a working group that focuses on transparency, accountability, participation, and collaboration within the Federal Government. This group, with senior level representation from program and management offices throughout the Government, will serve several critical functions, including:
- Providing a forum to share best practices on innovative ideas to promote transparency, including system and process solutions for information collection, aggregation, validation, and dissemination;
- Coordinating efforts to implement existing mandates for Federal spending transparency, including the Federal Funding Accountability Transparency Act and the American Reinvestment and Recovery Act; and
- Providing a forum to share best practices on innovative ideas to promote participation and collaboration, including how to experiment with new technologies, take advantage of the expertise and insight of people both inside and outside the Federal Government, and form high-impact collaborations with researchers, the private sector, and civil society.â€ (p.5)
Now hereâ€™s a working group I would like to speak with very much. If you read the language of the third subsection, itâ€™s amazing how many words you have to use to not say the words â€œopen sourceâ€: experiment with new technologies, using expertise inside and outside the government, high-impact collaborations with many communities of useâ€¦ theyâ€™re all but begging to create open source software projects to support the release of this government data.
In this â€œforum for best practicesâ€ on open data initiatives, you can imagine how useful a recommendation of open source software might be. You can even imagine the working group recommending government open source projects to help handle data that may be in strange government-specific formats.
60 days â€” February 6, 2010
â€œEach agency shall create an Open Government Webpage located at http://www.[agency].gov/open to serve as the gateway for agency activities related to the Open Government Directiveâ€ (p.2)
â€œThe Federal Chief Information Officer and the Federal Chief Technology Officer shall create an Open Government Dashboard on www.whitehouse.gov/open. The Open Government Dashboard will make available each agencyâ€™s Open Government Plan, together with aggregate statistics and visualizations designed to provide an assessment of the state of open government in the Executive Branch and progress over time toward meeting the deadlines for action outlined in this Directive.â€ (p.5)
Of course, if an agency is writing new software to support these new â€œ/openâ€ areas, Iâ€™d like to see that software made available under a open license. If there are any clever data analysis or visualization tools, those should be licensed as open source software, as well. That way, citizens would have the opportunity to help the agency with their own disclosures, and agencies could more easily share tools with each other.
90 days â€” March 8, 2010
â€œThe Deputy Director for Management at OMB will issue, through separate guidance or as part of any planned comprehensive management guidance, a framework for how agencies can use challenges, prizes, and other incentive-backed strategies to find innovative or cost-effective solutions to improving open government.â€ (p.5)
This is a strangely oblique reference to Vivek Kundraâ€™s Apps for Democracy project when he was CTO in Washington, DC, and the national-scale follow-on, Apps for America. Both of these contests asked that submissions be provided under OSI-approved licenses. This is important to keep these projects going. If contestantâ€™s software is under a proprietary license, there is no momentum behind the contest, since nobody can contribute to it after the fact. You might as well hold no contest at all, and instead just bid the work out to a contractor.
120 days â€” April 7, 2010
â€œEach agency shall develop and publish on its Open Government Webpage an Open Government Plan that will describe how it will improve transparency and integrate public participation and collaboration into its activities. Additional details on the required content of this plan are attached. Each agencyâ€™s plan shall be updated every two years.â€ (p.4)
I would hope very much that these plans for additional public participation and collaboration include invitations to open source developers who would like to help an agency build tools that make them function more transparently and efficiently.
â€œThe Administrator of the Office of Information and Regulatory Affairs (OIRA), in consultation with the Federal Chief Information Officer and the Federal Chief Technology Officer, will review existing OMB policies, such as Paperwork Reduction Act guidance and privacy guidance, to identify impediments to open government and to the use of new technologies and, where necessary, issue clarifying guidance and/or propose revisions to such policies, to promote greater openness in government.â€ (p.6)
I hope that this review would include an examination of FACA implementation guidelines, which is understood by many to prevent open source developers from directly participating with some Federal agencies, for fear of having offered the explicitly prohibited â€œvolunteer help.” We believe this isnâ€™t the case, and it would be great if OIRA published some clarifying language. If they were to provide an interpretation of OMB Circular 130-A that ensured it was safe for agencies to create open source software without running afoul of procurement regulations, that would be wonderful.
So hereâ€™s a tremendous opportunity for the open source community. We have been given an early Christmas gift: a pretty clear path for more open source software and (perhaps more importantly) more government-sponsored open source projects inside each agency. If you want to help take advantage of this opportunity, you can sign up at Open Source for America and join a working group. Youâ€™ll be glad you did.
A hearty thanks the Heather West of CDT and Melanie Chernoff of Red Hat for their invaluable comments.
Every day I get to engage with entrepreneurs, public sector innovators and journalists on re-imagining and re-energizing how government works, what it means to be “civic,” and this year has been an incredible one for many friends and colleagues.
I’m always inspired talking and working with entrepreneurs trying to solve big civic problems, especially those who realize much of the challenge lies within modernizing and empowering internal government operations, so it was great to finally meet with Govtech Fund Founder and Managing Partner Ron Bouganim this week.
The 18F Delivery team released a “Partnership Playbook” that aims to help federal agencies understand what to expect when working with 18F, and the gem within is play number two, “We work with an empowered product owner.”
Citizens simply glaze over when they are confronted by a sea of large numbers with many zeros. These figures need to be relatable to the person reading the data. Otherwise, open data is just more data that dies on the vine.
The U.S. Department of Veterans Affairs released a beta version of Vets.gov, and it’s the future of federal government digital development.
The Welsh Government released a report of its findings on how local government in Wales can better leverage digital technologies and realize significant savings while still providing quality, scalable citizen services.
A California bipartisan oversight committee, the Little Hoover Commission, has issued recommendations on how the state can bring a more customer-centric government to residents and visitors.
Seneca Systems CEO Chris Maddox shares the inspiration behind the new constituent relationship management system, Romulus.
“No ugly, old IT” jumped out at me when I first reviewed DataSF’s strategic plan, “Data in San Francisco: Meeting supply, spurring demand,” and it still sticks, mostly because someone inside government was so bold as to make this a priority and openly communicate it and also because this should be a mantra for everyone building civic technology.
Enabling internal government tech shops to quickly stand up applications in a secure testing environment is fundamental to quick prototyping, and 18F’s new Cloud.gov is a major step in realizing ultimate IT flexibility.