The GSA is currently planning forge.gov, which is widely assumed to be based on forge.mil, the much-discussed collaboration platform from the Defense Information Systems Agency, or DISA. forge.mil is a pretty incredible idea: a single destination for testing, certification, and software development in the Defense Department.
Earlier this year, San Francisco Mayor Gavin Newsom ignited an open source movement in government when the city approved the nation’s first open source software policy. Now, another movement — labor may be getting behind this effort. I have been asked to speak with Local 21 of Professional & Technical Engineers (IFPTE/AFL-CIO) today about Gov 2.0 initiatives I helped lead for Newsom and why unions should embrace open source technology.
In a recent post from Coder-in-Chief Clay Johnson, Clay outlines several reasons why developers should run for Congress.
The time has come to build a reliable, open platform that allows local governments to post development requirements and give private developers the ability to respond and build these applications for free.
Going a step further, we need to build a free, open source platform specifically for government, making it easier for government to install and implement and leverage plugins or modules for anything from standard contact forms to 311 citizen requests applications.
For at least that past two years, a tiny yet fast-growing group of folks who call themselves “Gov 2.0 advocates” has worked tirelessly to spread a message that emerging technologies, low-cost communications and digital culture can reshape government to be more collaborative, transparent, efficient and connected to its citizens.
An increasing number of people are starting to suggest that the concept of the “app contest†(where governments challenge developers to build civic applications) is getting a bit long in the tooth.
There have been lots of musings lately about the payoff for governments that hold such contests and the long term viability of individual entries developed for these contests. Even Washington DC – the birthplace of the current government app contest craze – seems the be moving beyond the framework it has employed not once, but twice to engage local developers.
I occasionally post critical comments when government is operating outside my definition of ‘open’ and only do so when I believe it’s important for the community at large to consider it in context of their own actions. By and large, GovFresh posts are positive, educational and, at times, congratulatory pieces that highly offset the critiques.
I love the Open Government Memo, I think it represents some of the most thoughtful and seminal policy strategy I’ve seen in 20 years in government. I don’t know who actually wrote it for the President, but I think that person should get a medal. And whoever reads it and doesn’t find inspiration for technology’s potential role towards advancing the ideals of our democracy is simply missing out.
Ever since Open Government Day – the 120 day deadline in the OGD when agencies had to release Open Government Plans – I’ve been pouring over them hoping to get a better understanding of how openness is going to be implemented. If we are to judge government openness by the barrage of documents we received last Wednesday, then we open government advocates ought to be very happy! But what are these documents made of, anyway? A word cloud illustrates it quite well – all the buzzwords that you would expect: Information, government, data, open, public.
Most western governments have in the last decade developed an accessibility strategy for their websites, often based on WCAG 1.0. At the end of 2008, the WC3 announced the final version of WCAG 2.0 and the public sector is now struggling to keep up. In Canada there was a recent announcement about a revised Common Look and Feel (CLF). In the USA the Section 508 is in its first of six revisions, part of which will be to adapt to the new approach to standards. I’m not sure that most citizens will notice the changes to government websites, however for both people with disabilities and the tax payers, it will be a very big deal.
“Open source and open government are not the same,†I’ve been reading recently. When discussing the role of open standards in open government transparency projects, Bob Caudill at Adobe, is concerned that open source and open standards are being conflated. He likes open standards just fine, but …
As someone who’s been around the block more than once in the technology industry, I’ve had the opportunity to witness a plethora of developments, ideas and concepts, some good, some not so good. One particular debate, or perhaps, a point is confusion, is around the word ‘open’.
While there’s a push for citizen ideas using collaboration tools, the trend towards open analytics should be just as important, because it exposes what information real users want and where the agency should focus more of its attention. This should be standard practice for all Web/IT departments, so making this information public is as simple as posting it to the agency blog.
Someone secure the ideas.gov domain before a squatter does, because Uncle Sam is open for suggestions. While there are great ideas and engagement, there no doubt could be more activity. Whether it’s the White House or a major media firm wanting to do good, a solid PR effort would go a long way in getting more citizen interaction.
Here’s some ideas to get more open government ideas.
While visiting many government Web sites since working on GovFresh, I occasionally see a vendor’s corporate logo. I can understand usage when embedding widgets, especially free ones, or incorporating social media icons to communicate to the public how they can connect with them. What’s not clear to me is the usage related to taxpayer-funded vendor services.
Are there other examples of vendor logos on government sites? Are there regulations around this? Is this appropriate? If so, in what circumstances?
Geoffrey Moore’s classic Crossing the Chasm is Silicon Valley’s manual for getting a tech product to market. Its straightforward subtitle, ‘Marketing and Selling High-Tech Products to Mainstream Customers,’ should compel every Gov 2.0 enthusiast to read it. The movement would be well-served to understand how to better pitch the effort, because it’s the only way the great work being done will resonate with average citizens.
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.
Gov 2.0, vendors, vibe and industry as patriot
sf.govfresh was an incredible event that brought together San Francisco’s finest government technology leaders, local area public servants and citizens sincerely passionate about building effective government. Adobe supported us in making that event happen and received an incredible amount of appreciation from the community.
We’re seeing this happen more. There are a number of new, niche, tech-focused, Gov 2.0 community events and gatherings happening at the local, state and federal level, all offering innovative approaches to bringing leaders and in-the-trenches foot soldiers together to better understand how we can solve our government problems.