| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
req:releasenaming [2009/12/10 04:30]
dzubey |
req:releasenaming [2010/12/18 17:35] (current)
|
| * Release 1.0 should be named Sahana, Sri Lanka, Colombo or tsunami... later releases can use new names | * Release 1.0 should be named Sahana, Sri Lanka, Colombo or tsunami... later releases can use new names |
| * Named after historical disasters e.g. [[http://en.wikipedia.org/wiki/Mount_Vesuvius#Eruption_of_AD_79|Mt Vesuvius 79AD]], suggest we start with [[http://en.wikipedia.org/wiki/2004_Indian_Ocean_earthquake|Indian Ocean Earthquake 2004]] --- //[[gt@kestrel.co.nz|Gavin Treadgold]] 2009/12/10 03:07// | * Named after historical disasters e.g. [[http://en.wikipedia.org/wiki/Mount_Vesuvius#Eruption_of_AD_79|Mt Vesuvius 79AD]], suggest we start with [[http://en.wikipedia.org/wiki/2004_Indian_Ocean_earthquake|Indian Ocean Earthquake 2004]] --- //[[gt@kestrel.co.nz|Gavin Treadgold]] 2009/12/10 03:07// |
| | * Given temporary name (could be existing numeric or any honorific non-location/non-event name), then, if deployed in a natural disaster, renamed after that location/event. --- //Glenn Pearson 20009/12/10// |
| |
| == Name idea examples == | == Name idea examples == |
| |
| == Comments == | == Comments == |
| From --- //[[gt@kestrel.co.nz|Gavin Treadgold]] 2009/12/10 03:07// | Moved to discussion page. |
| * 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. I think there is more value in educating people about historical events that they are no longer aware of, than events that have just occurred in the past few years, and are still somewhat fresh in peoples minds. | |
| |
| * Question: Would naming the product after an event affect the product's usage in an impacted community? For instance, The September 11th Release. Imagine a death in the family, or personal accident and naming a product after that. Is this relevant? | |
