Crisis Camp Day - Saturday, September 25, 2010

From CrisisCommons
Jump to: navigation, search

This is a past event. A Global CrisisCamp Day which took place September 25, 2010

Objective: Phase I for developing CrisisCamp in a Box, so anyone can be quickly trained up to run their own CrisisCamp!

What: Events: CrisisCamps will be held in in Washington D.C., Toronto, Calgary, Bogotá, Silicon Valley and in London). There will be virtual participation for all camps.

When: All day; see the camp event sites for times and how to join virtually.

More details:: CrisisCamp Day Blog post

CrisisCampDay Twitterstream, Blogs & Media Coverage

Twitter hashtag : #ccday


This section provides a launch point for the crisiscamp day, the basic-camp (and inter-camp)model. This will make the inter-camp and virtual volunteer coordination, as well as status and tracking, easier for all!!


You are either a CAMP or a VIRTUAL VOLUNTEER. Below is how we will roll on camp day.

A.1 For CAMPS (Onsite or Cafes):

  • Have at least one person per camp on irc channel
    • Check in when you start
    • Report out status AT TOP OF HOUR on channel, example, UPDATE_TOR, UPDATE_DC: Started working on Ushahidi tasks X X. 8 people at camp
    • Check out, transition as necessary
  • TRACK YOUR STATUS of who attended and what worked on detail on your CAMP page below

A.2 For VIRTUAL VOLUNTEERS (Wherever you may be)

Playing along at home? With a little basic communication and tracking, we hope to make the virtual volunteer experience more enjoyable. This also helps the camp day coordinators to better connect with and understand and coordinate work among and between volunteers. Thats our story and we're sticking to it:

  • Have you officially pre-registered on eventbrite yet? Virtual Registration
  • Check in on IRC and say hi!!
  • Check in on the day-of-camp virtual volunteer person and camp log: VolunteerLog
  • General CrisisCamp Training (note, some of this is actually being updated because of this camp, but provides a basis for starting)
  • Other information as we think of it
  • All set? Have fun!!

If you need help, ask on IRC or tweet out #ccday @crisiscamp.


Here is some basic information for how we track the camp day tasks and activities, as well as how we communicate and collaborate with each other. Hopefully this 'gets us on the same page'.

B.1 The Central Dispatch Log

B.2 Other Camp Day COMMUNICATION methods

  • B.2.1 Conference Bridge Info:
    • Usage: COLLAB (mostly community calls, and problem-definition working groups)
    • General: Tele_BridgeWiki Page
    • Calls: TBD
    • Calls: TBD
  • B.2.2 IRC - For Chat
    • Usage: (CHAT and COLLAB: Inter-camp leads and others, virtual volunteers, friends-of-crisiscamp).
    • General: Help/Other Info on IRC (like good clients and connection detail): IRC_Info
    • MAIN Channel: #CrisisCamp
    • Other channel: #CrisisCamp_CCIWG (Infrastructure (and website) working group)
    • Other channel
  • B.2.3 Piratepad:
    • Usage: Used for CONTENT-COLLAB, ie, meeting minutes only, topic chats. NOT for ongoing chat. Being setup for general, as well as Work Stream specific tasks.
    • General: Any content-specific pirate pads are usually linked under streams, or in task-spreadsheet
    • Piratepad Global:
    • Piratepad Other TBD:
  • B.4

B.3 Getting ready

  • Setting up your desktop - what should you have open (irc, wiki, etc.)
  • Have you read this? Good stuff to get started: Blog:What to expect on crisiscamp day
  • Conference Bridges and scheduled times (tbd)

Twitter hashtag : #ccday


Dipping your toes in

Work streams of activities

This goes to our goals of creating CrisisCamp in a Box (CCIAB)

Stream 1: Create content and process for CCIAB. #Stream 1 - CrisisCamp in a Box
Stream 2: Open Discussion about Emergency Planning. #Stream 2 - Open Discussion on EME world/World Bank Problem Definitions
Stream 3: FEMA and Emergency Planning Problem Definitions.
Stream 4: Discover other Volunteer Technical Communities - learn their tools and how you can contribute. #Stream 4 - Learning about Volunteer Technical Communities
Stream 5: Infrastructure and Web Stream, for crisiscamp and crisiscommons community. #Stream 5 - Website and Infrastructure
Stream 6: For things not addressed by above, but that forward the objective of CrisisCamp in a box, to be included here. #Stream 6 - The Pot

Work Streams tasks coordination and spreadsheet

This is how we are coordinating and tracking specific tracks of work. If it ain't on here, go ahead and propose it:

The Camps: Event Planning and Logistics:

Camps coming on board - general help:

Cities participating:

These are the camps. You can use this to connect with and find out what they are doing.

Onsite CrisisCamp:



Stream 1 - CrisisCamp in a Box

PRIME Contacts: Heather Leson, Brian Chick (Toronto)
Noel in DC [1]

Main Problem Definitions

1. What should be in CrisisCamp in a Box? Describe the tools, checklists, templates and materials

-Check online checklist that CrisisCamps need -how to start a camp -how to run a camp -how to handle media outreach/relations etc. -what should be in a press kit

2. Create key requirements for starting CrisisCamp: How does someone activate crisiscamp in a box and collaboration with and other cities? And, the reverse: how do affected regions create crisiscamp need request.

3.Document the Crisis preparedness response for CrisisCommons (see email chain from NZ earthquakes)recognize a Crisis Camp as being part of our community?

4.How can volunteer communities connect with the eme world? -crisiscamp as a response, crisiscamp in steady state


  • Main Pirate Pad:

  • Project Pirate Pads:
  • IRC channels

Stream 2 - World Bank Problem Definitions

  • Prime Lead: unconference call run by Noel Dickover, Andrew Turner (Washington)

Problem Definitions

The World Bank's Global Facility for Disaster Reduction and Recovery Labs will provide the Global CrisisCamp Day with problem definitions for exploration of solutions, recommendations related to the Pakistan Floods. Anyone can participate in providing written recommendations and ideas. Video submissions are also welcome from groups or individuals. Please check back here for updates.

Help in Pakistan tasks here:

1. Open Street Map (Andrew): Mapping roads, towns etc in the Swat & Kabul river valley lowland areas, naming towns/villages, marking towns/villages affected by the floods, and Geocoding. Visit:

2. Ushahidi data entry - verify/translate data input -

3. Media Monitoring: (Noel) especially Twitter and Facebook, but also add media sources (

4.Sahana: Tasks for volunteers to do: (Maybe Mark)

5.Populate the Pakistan CrisisWiki: Help populate (maybe Andy)


  • Pirate Pads
  • IRC channels
  • Conference bridge times and bridge code
See also Pakistan/2010_Floods

Stream 3 - Emergency Planning Problem Definitions

Prime contact: Heather Blanchard and ______(Maybe Alex Rose if we are very lucky) ^V^

Problem Definitions

1. How can FEMA, and other Government Bodies, support connectivity between volunteer technology communities and local emergency response agencies? (Policy? Grant Process?)

2. How can technology be used to better prepare communities for crisis? For citizens, private sector, schools, persons with special needs?


  • Pirate Pads

Pirate Pad

  • IRC channels
  • Conference bridge times and bridge code

Stream 4 - Learning about Volunteer Technical Communities (VTCs)

Prime: Melanie Gorka/Heather Leson (We would love your help as a project lead. let us know.(Toronto)

Problem Definitions
Note: This section is more about research and providing links to the VTC training materials.

Start here:


Pirate Pads:

Training Materials Inventory for VTCs:
Help us create an inventory of resources and connect folks to videos, content etc for the other volunteer technical communities.

  • IRC channels

Stream 5 - Website and Infrastructure

Stream Leads: Deborah Shaddon (virtual-deborahCHI), Chad Catacchio (virtual)
IRC: #crisiscamp_cciwg

What are the Infrastructure Tasks?

The Infrastructure tasks include some analysis and definition of some tools, some analysis of some infrastructure problem statements, some 'fixing' of stuff (for camp and commons sustainability) and some work for generating some of the crisis-camp-in-a-box content.

This stream of work will be executed as a continuation and enhancement of work started under the CrisisCommons Infrastructure Working Group (CCIWG). If you want to start with some background/context, please see the CCIWG main page, as well as google groups. Website activities are also tracked here.

Detail Infrastructure Working Page/Deliverables Launch for CrisisCampDay: *CCIWG:CrisisCampDay Problem-Task-Deliverable space
Note: These map to tasks in googledocs, but contain elaborated out problem definition starting points. For wish list, include below

Website tasks and Infrastructure Tasks

There are two tabs, one for website and one for infrastructure:

Stream 6 - The Pot

For things not addressed by above, but that forward the objective of CrisisCamp in a box, to be included here.



September 24, 2010 - Prep Conference call
Advance number estimates: 100 people signed up for CCDay

  • Silicon Valley 11
  • Washington 50
  • Toronto 25
  • Calgary 5-10
  • London 5-10
  • Virtuals 50

Our problem definition brain storm:

Below is being kept for historical purposes, and should seek to be informative only for the actual 'CrisisCamp day execution', we are not running tasks or plan from the items below. But you can see our humble beginnings.

  • In support of National Preparedness Month - CrisisCommons is a Coalition Partner - to sign up visit Ready America.
  • a deliverable from the CrisisCongress Unconference
  • In addition, a few key CrisisCamp members: Anna Curran, Luis Hernando Aguilar and our friends from Instedd (Exercise 24) also had a number of ideas on a Learning day.
  • The Community Working Group was tasked to build a Day of Learning within 30 to 90 days.
  • The brainstorm notes CrisisCamp Toronto-Draft Event Plan (August 4, 2010)

CrisisCamp Global Day of Learning Project Plan [2]

Maybe Prezi to collaborate screencasts

Objective: Engage, Taste, Learn, Create and Replicate

  1. Engage: We want to create a Crisis Camp in a Box and this is a great way to test out what we’ve already been doing in a Global Day of Learning
  2. Taste: It is a tasting menu of all the unique ways that CrisisCamp and their open source partners can learn, share and activate change.
  3. Learn: Be Interactive. Mentor and Share by providing folks a chance to do a deeper dive into the topics of open source aid and collaboration. Use existing learning tools provided by partners and provide expert resources where ever possible.
  4. Create: Create an inventory of all the existing learning materials. f there are any missing learning materials, either create or document it as an action.
  5. Replicate: This is part of a 4 stage process to create content for any CrisisCamp. Stage 1 to create CrisisCamp in a Box; September 25, 2010, Stage 2/3- October xx, Nov xx, Stage 4: Full Launch of CrisisCamp in a Box - January 15, 2011


  1. CrisisCamp Day of Learning: DATE: Saturday, September 25, 2010
  2. Global feel/vibe (naming our "rooms" by country/location of the various open source tools - recognizing the history)
  3. To collect an inventory of existing training tools for the various open source tools.
  4. To develop training materials and to build tutorials, kits
  5. To learn about current projects with experts from: Ushahidi, Swift River, OpenStreetMap, Sahana, Crisis response experts.
  6. Identify any gaps that we may need to create for Crisis Camp in a Box
  7. Mentor, learn, share collaboration, hand off across cities and countries.
  8. This year we are not ready for a Crisis Simulation. Next year, we can model after simulations like the one done in Columbia (Luis) or (Luke)

Optional Schedule

Morning Session:Learning

Sessions will be a crash course aka speedgeeking in each area given by an expert on the subject.

  1. Ushahidi
  2. Swift River/Crowdmap
  3. wiki/CrisisWiki
  4. OpenStreetMap
  5. Sahana
  6. Understanding Crisis Response
  7. Training and Content (for people who may already be experts in the above)
  8. Infrastructure and web boot-camp (for Deborah - CCIWG?)

--Deborahshaddon 18:06, 12 August 2010 (UTC)START0812: Agree, this is good idea. However, won't be open ended, need to get to specific tasks and objectives. So, as in previous camps, infrastructure (or each of these really) needs a 'named' point person or manager END0812--Deborahshaddon 18:06, 12 August 2010 (UTC)


  1. collect inventory of available resources by open source / topical area
  2. Heather L and Heather B to conduct outreach with partners to see if they would like to present, video stream etc.
  3. make it interactive, not pure presentation. Gunner magic sauce

--Deborahshaddon 18:06, 12 August 2010 (UTC)Start0812

  • For each domain area above, I say we assign someone within CC to be central-point to drive down that content and be focal point for partnership communications, etc., and develop sub-teams,and project plans to get us prepared to move toward 09-25 camp day
  • Thing I've learned about 'camps' is that it helps to have some distributed model setup ahead of time to make the execution of it easier, takes pressure off a single-camp lead to coordinate, particularly where the camp-models are not as hardened. So, one idea might be that if someone in Chicago, for instance, is interested in helping coordinate content for 'swiftriver' ahead of time (I have someone who is interested in this topic), then they can work with the central point person.

--Deborahshaddon 18:06, 12 August 2010 (UTC)END0812

Afternoon Session: Doing

  1. Ushahidi
  2. Swift River
  3. wiki/CrisisWiki
  4. OpenStreetMap
  5. Sahana
  6. Understanding Crisis Response
  7. Training and Content Development (for people who may already be experts in the above)

In the afternoon, the previous sections are still themes and we can run an unconference where the rooms are still set up with the same project and people can work on tasks that have been pre determined- ie. creating training materials on the subject, improving our infrastructure and all the necessary elements to create our “CrisisCamp in a Box”.


Our audience is teachers, organizers, librarians, graphic designers, usability(UI/UX), documentation specialists, content development, videographers, elearning, developers, knowledge workers, social media folks.

We have many types of volunteers:

  • New Media - Bloggers, vloggers, videographers, podcasters, photographers, social media trainers, social media users, collaborators, crowdsourcers
  • Organizational - Organizers, open source community planners, project managers, emergency response planners, crisis communicators
  • Other - Researchers, lawyers, trainers, technical writers, event planners, translators, innovators, entrepreneurs, anyone with a laptop
  • Technical - Software developers (Python, PHP, Ruby, etc), web developers, web designers, user experience/user interface experts, geocoders, geo mappers, GIS experts, technologists, beta testers

You don't need a title to volunteer! If you know a language in a crisis region, you can translate. If you've volunteered at a couple of crisis camps, you can train new people.

*Note: This event is to learn about CrisisCamp and our various partners. We don't expect project management or coding at this event. Stay Tuned though. There are more events coming up.

--START0812: Deborahshaddon 19:05, 12 August 2010 (UTC)Start0812:


--Deborahshaddon 17:55, 12 August 2010 (UTC)Start0812: My comments

  • Exciting!! Tangible and useful and meaninful, love it!!
  • CCIAB needs to include all the hardened content of operating camps too (the not sexy part) not just the content to present or how to present it. Since a lot of this is already done, can we harden it before the Sept 25th, for instance, by engaging London model and what they are doing now in trying to get a camp going in support of Pakistan?
  • The deeper dive into 'open source' sounds too open ended. This isn't really an excercise in open source, I think we banty that term around too much. The focus is on particular 'tools and capabilities' for disaster management or crisis response or crisis information, some of which happen to be open source (which is great), for which we've established partnerships. Introducing someone to 'crisisWiki' is really less an excercise in 'open source' as it is in 'gathering and viewing and using content in support of a disaster',and the crowdsource partnering to do so. Sahana, and Ushahidi also happen to be open source. The tool/capability is the 'most' important part. If we want to introduce folks with development-bent to the open-sourceness of these tools (which likely code wouldn't be changed in a disaster, but someone could join that community),I consider this a completely different objective to the introduction and information sharing of the tool, and how these tools support crowdsourcing of information (which in and upon itself isn't an open source-esqe activity). I can be overruled here too.
  • So, to get to the 'now what do we do with this knowledge, we need to also harden the position as well on CrisisCommons 'Crisis Engagement model' (ie, how/when/what we do to engage in response and support of a crisis itself'). At least by time we get to CCIAB. Therefore, developing this too provides context to the folks that are wondering what they might do with this information if ever inclined to help in a disaster. This will build over time, but important to at least address this somehow.

--Deborahshaddon 17:55, 12 August 2010 (UTC)End0812

Just using this section to start collecting ideas and tasks we can drive through the infrastructure team (with community and communications) for crisis camp day. Once ideas are generated, we can add to a project plan and divy up work:

* The basics: Getting it ready:

    • website:
      • - Pending
    • wiki:
      • determine camp day page global
      • determine camp day page city (define structure)
      • determine camp day page per project (define structure)
    • event registration structure: by city or global? (eventbrite)
    • various social media usual suspects:
      • twitter, facebook, linkedin, etc
    • Supporting infra:
      • piratepad, ustream, etc. (for global camp, per project?)
      • googlegroup?
    • Multi-media:
      • camp youtube, camp flikr, etc.

*Next Level: Supporting the 5 (or so) subject-area tracks: BTW, totally reusuable!!

    • Where to collect content? - Vote: Wiki
      • CampDay Info/Project Page for Ushahidi content aggregation/sharing launch (info/link) and work tasks (project)
      • CampDay Info/Project Page for SwiftRiver/crowdmap content aggregation/sharing launch (info/links)and work tasks (project)
      • CampDay Info/Project Page for Shahana content aggregation/sharing launch (info/links)and work tasks (project)
      • CampDay Info/Project Page for crisisWiki content aggregating/sharring launch (info/links) and work tasks (project)
      • CampDay Info/Project Page for OSM content aggregating/sharing launch (info/links) and work tasks (project)
      • CampDay Info/Project Page for General Purpose "Intro to crisis response and disaster management", etc.

--END: Deborahshaddon 19:05, 12 August 2010 (UTC)END0812:

Contribution from Paris :