RECOVERY 2.0: THE REPORT…
October 9th, 2005
Following my experience working with Bill Callahan and others in the Emergency Community Computer Center at the Cleveland Covention Center, I’ve been very interested in what would come out of Recovery 2.0 this weekend. Jeff Jarvis has been blogging the hell out of the concept and posts a wrap-up this evening about what was done.
About 45 good people came to our Recovery 2.0 meeting in San Francisco, called there by nothing more than a few blog posts and a desire to find ways to improve the internet”s response to the next disaster.
I didn”t know what, if anything, we could accomplish in an hour and a half. At best, I hoped for a simple list of simple starting points and that”s what we got.
The shopping list that follows is a good one, but the cental piece is the Recovery wiki.
The points flagged at the meeting included:
We need a place online to gather and share information, needs, and solutions.
We need to work on standards and APIs for the tools and data bases people create to help in disasters.
We need to meet face-to-face with government, NGOs, and business to offer help and coordinate.
Jarvis’ third-from-the-last paragraph is, I think, the most important:
Then we spent some time listing key needs and characteristics of recovery 2.0: how we need to be even more concerned about preparedness than recovery; how systems need to be open; how we need to find ways to connect to the unconnected (e.g., the Skype virtual phone room idea); how it needs to connect with authorities; other characteristics: searchable, fluid, matchable, swarmable, transparent, trustworthy, discoverable, accountable, tested… and more. We ended up with many words describing what it needs to be.
The most important of all, of course, is that it needs to be.
My Soundtrack: For A Few Dollars More by Terranova onWOXY.


