Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dep:home [2007/11/13 10:56]
chamindra
dep:home [2009/07/06 20:36] (current)
Line 30: Line 30:
 //Justification// - It is important to spend sufficient time upfront to clearly understand the requirements and to document them should further clarification be required later. Always communicate this documentation to the target org before you begin to set expectations and schedules. It is better for the team doing the customization to meet the members from the target org onsite rather than doing this remotely. //Justification// - It is important to spend sufficient time upfront to clearly understand the requirements and to document them should further clarification be required later. Always communicate this documentation to the target org before you begin to set expectations and schedules. It is better for the team doing the customization to meet the members from the target org onsite rather than doing this remotely.
  
-== Understand the problem first and if Sahana is a match and not visa versa ==+== Understand the problem first and if Sahana is a match and not vice versa ==
  
 //Justification// - Understand the real problem being faced by the target org and match/customize Sahana to that, rather than use Sahana like a hammer looking for a nail. It is better not to deploy Sahana, than to deploy a solution that does not match the coordination problem. //Justification// - Understand the real problem being faced by the target org and match/customize Sahana to that, rather than use Sahana like a hammer looking for a nail. It is better not to deploy Sahana, than to deploy a solution that does not match the coordination problem.
Line 47: Line 47:
 == Have the beneficiaries been helped? Use the Red Cross Code of Conduct as your baseline == == Have the beneficiaries been helped? Use the Red Cross Code of Conduct as your baseline ==
  
-//Justification// - As Sahana address the humanitarian response domain always ask the question to yourself irrespective of what the target org need, if the beneficiaries have indeed been help by the customization. It will keep your leadership on the customization well grounded. The [[http://en.wikipedia.org/wiki/Code_of_Conduct_for_the_International_Red_Cross_and_Red_Crescent_Movement_and_NGOs_in_Disaster_Relief | Red Cross Code of Conduct]] provides a good base line for all of us to measure against.+//Justification// - As Sahana addresses the humanitarian response domain always ask the question to yourself irrespective of what the target org need, if the beneficiaries have indeed been helped by the customization. It will keep your leadership on the customization well grounded. The [[http://en.wikipedia.org/wiki/Code_of_Conduct_for_the_International_Red_Cross_and_Red_Crescent_Movement_and_NGOs_in_Disaster_Relief | Red Cross Code of Conduct]] provides a good base line for all of us to measure against.
  
 == Deploy Sahana on an environment comfortable to the target organization == == Deploy Sahana on an environment comfortable to the target organization ==
  
-//Justification// - There have been many instances where the Linux OS has not matched the target organizations ability/capacity maintain the system. In this instance we recommend you install Sahana on an OS familiar to the target organization (usually windows) or all issues including non-Sahana ones will be propagated back to you. Sahana is available to be installed on windows as a WAMP package or the portable App version.+//Justification// - There have been many instances where the Linux OS has not matched the target organization'ability/capacity to maintain the system. In this instance we recommend you install Sahana on an OS familiar to the target organization (usually Windows) or all issues including non-Sahana ones will be propagated back to you. Sahana is available to be installed on Windows as a WAMP package or the portable App version.
  
  
Line 63: Line 63:
 == Use bug trackers, capture change requests to prioritize and schedule tasks == == Use bug trackers, capture change requests to prioritize and schedule tasks ==
  
-//Justification// - Bugs will prop up as you customize Sahana for the target org. Ensure you have a quality process in place to track & fix bugs. Also you can expect a lot of changes from the target org especially during a disaster, so be ready to track them effectively such that none are missed and schedule them effectively based on priority. At the top end you can use a project management tool such as dotproject to schedule the team. It is better to have a dedicated team assigned to ensure delivery and deadlines.+//Justification// - Bugs will pop up as you customize Sahana for the target org. Ensure you have a quality process in place to track & fix bugs. Also you can expect a lot of changes from the target org especially during a disaster, so be ready to track them effectively such that none are missed and schedule them effectively based on priority. At the top end you can use a project management tool such as dotproject to schedule the team. It is better to have a dedicated team assigned to ensure delivery and deadlines.
  
 == Clearly understand maintenance and training needs and ensure it is covered by someone == == Clearly understand maintenance and training needs and ensure it is covered by someone ==
Line 76: Line 76:
  
 //Justification// - As the system gets used by the target organizations there will be change requests that will involve changes to the code. Ensure you have a staging server to test new patches and a fault-tolerant mechanism to update the production server once the tests are complete on staging. //Justification// - As the system gets used by the target organizations there will be change requests that will involve changes to the code. Ensure you have a staging server to test new patches and a fault-tolerant mechanism to update the production server once the tests are complete on staging.
 +
  
  
Line 82: Line 83:
 == Use the Red Cross Code of conduct as your baseline set of principles when working in this domain == == Use the Red Cross Code of conduct as your baseline set of principles when working in this domain ==
  
-//Justification// - The [[http://www.icrc.org/web/eng/siteeng0.nsf/htmlall/57JMNB#a3|Red Cross Code of Conduct]] has been formulated by many years of experience operating in the Humanitarian Response domain and it is advisable that you keep to these principles when working in this domain such that you do not get into political issues or other related problems. We have elaborated on the Red Cross Code of Conduct with respect to Sahana [[Sahana Code of Conduct | here]]+//Justification// - The [[http://www.icrc.org/web/eng/siteeng0.nsf/htmlall/57JMNB#a3|Red Cross Code of Conduct]] has been formulated by many years of experience operating in the Humanitarian Response domain and it is advisable that you keep to these principles when working in this domain such that you do not get into political issues or other related problems. We have elaborated on the Red Cross Code of Conduct with respect to Sahana [[dep:code_of_conduct | here]]
  
 == Read through the Sphere Handbook to understand standards in Disaster Response == == Read through the Sphere Handbook to understand standards in Disaster Response ==
Line 100: Line 101:
   * [[dep:role:Public Community Portal]] - For public collaboration between spontaneous volunteers   * [[dep:role:Public Community Portal]] - For public collaboration between spontaneous volunteers
   * [[dep:role:NGO operations]] - An NGO management tool including volunteer coordination   * [[dep:role:NGO operations]] - An NGO management tool including volunteer coordination
 +
  
  
Line 112: Line 114:
   * [[dep:type:Pandemic]]   * [[dep:type:Pandemic]]
   * [[dep:type:Conflict]]   * [[dep:type:Conflict]]
 +  * [[dep:type:Floods]]
 +
 +
 +====== Customizations =====
 +
 +  * [[dep:china-gov | Chinese Government ]]
 +  * [[dep:NLM-BHEPP | U.S. National Library of Medicine, Bethesda, Maryland, for the Bethesda Hospitals Emergency Preparedness Partnership]]
 +
 +
 +
 +
 +====== Community Integrated Deployment ======
 +
 +__Best Practices__
 +
 +  * Someone to join the sahana-user list and to facilitate bringing in deployers (for example the IBM China team) into the sahana-user and sahana-maindev communities as appropriate early in future emergency/deployment processes.  The following issues can then be supported and addressed:
 +
 +  * [[dep:Bugs found]] : Bugs found should be reported by the deployment team through the sahana-user and sahana-maindev lists - someone from our core team can then take responsibility for getting them added to Tracker. Patches can then be provided by the community back to the deployers.
 +
 +  * [[dep:Bugs fixed]] : Process TBD to get bug fixes made by deployment teams back into the main codebase.  These could similarly be reported back directly to the sahana-maindev list and the patches to be incorporated into future release candidates. 
 +
 +  * [[dep:New modules]] : Often new modules are developed for a specific deployment - for example, the situation reporting module completed for the Bangladesh deployment.  This code should be returned to the community for consideration by the PMC of being merged into the main codebase.
 +
 +  * [[dep:New features]] : Similarly, enhancements to existing functionality is often made during deployments to meet the specific need of the operational situation - such as the financial disbursement tracking that was linked to the DVR for the Peru deployment.  Again, this code should be returned to the community for consideration by the PMC of being merged into the main codebase.
  
  

Navigation
QR Code
QR Code dep:home (generated for current page)