Difference between revisions of "Main Page"

Revision as of 19:40, 2 May 2016

Digital response is an emerging space where we have a chance to apply our social justice brains and hearts in such a way that it bridges gaps in socioeconomic and technology.

ALERT: Due to ongoing spam problems, we have had to disable anonymous editing and self-service account creation. 
We ABSOLUTELY welcome contributions to this wiki; please contact info@aspirationtech.org to request an account. 
We apologize for the hassle!

For a long time, it wasn't possible to include everyone's voice in planning or decision making without generally questionable amounts of time. There was no way to listen, at scale. Aggregation and centralization made some small sense, especially in times of urgency, even with the troubles these tend to cause. But now we have new technologies. We have the ability to listen, in high resolution and in high fidelity. But technology isn't a silver bullet -- we also need the political will, and the personal values to make that happen. And we have an awful lot of momentum related to history to make it easier to not make those shifts. With Aspiration's new digital humanitarian response program, we get to support some of the rad people willing and able to make these changes.

This wiki is a place to hold notes from events, details about projects spawned out of the events, etc.

Join the Conversation

Mailing List

Our mailing list includes updates about digital responder call-ins, upcoming events, and cross-sector collaborative discussion.

Check In Calls

These call-ins / check-ins are at their most basic a way to strengthen the connections across response organizations (traditional, digital, and otherwise), individuals, and projects. Some calls are focused or topical, but are always meant as open spaces for cross-sector and -organizational collaboration. Defined organizations, networks, and other ways of delineating and focusing response are absolutely necessary, but so too is a space external to that for emergent possibilities.

There is a template for how to conduct a digital responder checkin call on the checkin call category page. That page will also give a process for adding your own calls to this wiki.

2016 May 23 : updates on HumTechFest, discussion on the blockchain in response, and questions about international consortium, health site data, the digital response ecosystem map, and urban resilience.
2016 April 12 : updates from Resilience CoLab, JIFX, prosthetic environments, Coordinated Data Scramble, and decision maker's needs.
2015 Nov 27 : updates on Humanitarian Services Data Standards Project, Resilience CoLab, Witness Engines/Crisis Archiving, Secure Web Integration Framework, JIFX, Sahana Eden supply and volunteer management database, and RHoK
2015 Sept 23 : updates on the handbook, ResilienceCoLab, and 2W doc. Also talked about RefugeesWelcome, JIFX, the Earthquake Coordinated Data Scramble, and communication methods (the drafted Code of Conduct for open comms channels, how the call-in platform was working, and how to select other comms platforms).
2015 Aug 06 : the band is back together! A firehose of a call, many folk gave a quick overview of themselves and their organizations. We also did quick indicators of projects we're working on and how we could use help.
2012 Sept 12 : updates about how to get data into and out of FEMA.
2012 Jul 31 : notes from a call while with Geeks Without Bounds with organizational updates from Crisis Commons, Humanity Road, and Standby Task Force about a data commons.

Events

Ever wanted to know about, or work on, disaster and humanitarian response technology from a people-first perspective? Aspiration's #HumTechFest strives to build capacity for humanitarian aid and disaster response efforts through technology and community. These are participatory and community-driven convenings designed for field practitioners, media makers and storytellers, technology developers, information security practitioners, members of affected populations, researchers, and everyone in between. The agenda is co-developed with participants, facilitators, and partners in the time leading up and during the event.

Please check out our Participant Guidelines before the event.

Projects

Digital response ecosystem map : a snapshot of the current state of the digital response ecosystem, as well as some of the things we plug into.
Frontline communities holding responders accountable : response organizations and individuals are vital components in many extreme events -- but who holds them accountable? Are there mechanisms by which those most affected by the extreme event might do so?
Bookmarklet to log projects : a plethora of do-good projects exist across many organizations, spaces, and events. How can we log them in a decentralized way?
Media guide for extreme events : how to act as a reporter in good faith in an affected region, and ways to approach media inquiries from a social justice perspective.
Extreme event preparedness and response for small nonprofits : guide for small non profits and other community groups to prepare for, and respond to, crisis.

Response Groups and Projects Aspiration Works With

Red Cross Red Crescent Climate Centre : on games about citizen reporting, on crowd integration.
Dialling Up Resilience : on accountability mechanisms and local indicators of resilience.
Hirondelle : on visually representing their communications network.

Words on the Subject

The topic on our blog

Follow and comment on topical blog entries.

@@ Line 26: / Line 26: @@
 ==Projects==
+* [[Digital response ecosystem map]] : a snapshot of the current state of the digital response ecosystem, as well as some of the things we plug into.
 * [[Frontline communities holding responders accountable]] : response organizations and individuals are vital components in many extreme events -- but who holds them accountable? Are there mechanisms by which those most affected by the extreme event might do so?
 * [[Bookmarklet to log projects]] : a plethora of do-good projects exist across many organizations, spaces, and events. How can we log them in a decentralized way?