This is an old revision of the document!


Release Naming Ideas

Insert your ideas on naming conventions for sahana releases.Please keep in mind that this project is used in high-stress situations, so names should be non-offensive across multiple culture-spaces and stress levels.

Since this is a brainstorming area, there are no bad entries, the object is to get ideas down. We'll vote later.

Naming Convention ideas
  • Naming after weather risks (not disasters)
  • Naming after disaster types
  • Naming after influential people
  • Naming after countries or cities that been subject of disasters since Sahana's inception
  • Naming after languages that our group speaks
  • Naming after disaster (place name) location where Sahana has been most recently deployed (i.e. latest release = last deployment).
  • Named “Sahana” translated in local language where Sahana has been deployed.
  • Release 1.0 should be named Sahana, Sri Lanka, Colombo or tsunami… later releases can use new names
  • Named after historical disasters e.g. Mt Vesuvius 79AD, suggest we start with Indian Ocean Earthquake 2004Gavin Treadgold 2009/12/10 03:07
Name idea examples
  • Rain release (weather)
  • Thunderstorm release (weather)
  • Tsunami release (disaster)
  • Earthquake release (disaster)
  • JamesLeeWitt release (people)
  • NelsonMandela release (people)
  • Aceh release (place)
  • Samoa release (place)
  • Sinhalese release (language)
  • Bihar release (deployment)
  • Sahana release (translated)
  • Relief release (translated)
Comments

From — Gavin Treadgold 2009/12/10 03:07

  • Possibly want to avoid location names (specifically countries) as these could be confusing with future country-specific distributions of Sahana. Likewise languages we speak could be an issue if we don't support a translation in that language.
  • Naming after natural hazards/disaster types may send the signal that that release of Sahana includes functionality to help manage that type of event (not a biggy, but we may have to be careful)
  • Influential people just doesn't ring a bell with me :)
  • Not that keen on naming it after recent deployments for actual events, we want to be encouraging deployment in advance of events. It isn't really a good message to send naming a release on the most recent event where they didn't deploy Sahana in advance.
  • My personal preference would be for using historical events and including some information, linkage and statistics on these historical events. We would of course start with the 2004 Indian Ocean Earthquake, but then could move into more historical events such as the Carribean Hurricane of 1780, the Chilean Quake of 1960, Mont Pelée 1902, Great Fire of London, San Francisco Earthquake 1906 etc. I think it is worthwhile to use these historical events to remind countries and regions of the hazards that they are exposed to, what has happened in the past, and what will likely happen again, and that they should install Sahana in advance :) Other than starting with the historical linkage with the 2004 Indian Ocean Earthquake, I would suggest that all events used for this theme should have happened at least 10 or more years ago. The release date should also be tied to the historical date that the event occured.

QR Code
QR Code req:releasenaming (generated for current page)