Sahana Standards PMCChamindra de Silva

Sahana 2011 Annual Meeting May 7th 2011, Portugal

Why do we need a Standards PMC?

The moment Sahana became more than one autonomous project it was necessary to set a bar on what defines a

“Sahana project” Examples

“Apache Foundation Project” “Ubuntu Maintained Package” “Apple product”

“A Sahana Project”

We want this phrase synonymous with A mature H-FOSS community project NIIMS and ICS compliant project A project that is easy to install and use A dependable security, load and

functionality tested project codebase A project that is easy to integrate with others A project where due diligence on IP is handled A project that empowers relief agencies

The Standards PMC Composition

Sahana Eden Francis Boon Praneeth Bodduluri

Community Dev David Bitner Gavin Threadgold

Sahana Agasti Chad Heuschober Glenn Pearson Mifan Careem Nilushan Silva Nuwan Waidyantha

Board Mark Prutsalis Louiqa Raschid

What defines a Sahana project now?

Right now, just that: An Open Source Works in the area of disaster management

Areas to increase the “Sahana” bar next NIMS and ICS compliance Support for Open Interop Standards Packing and Publishing Standards Quality Assurance Standards

Interop Standards

Objective Bring about effective information exchange

during crisis to prevent siloed repositories that is of less value to response

Mechanisms Agreements on Ontology Agreements on Open Standards Agreements on Consistent User Experience Preparedness: Interop Workshops

Test Cases and validate exchange

Interop Standards Supported so Far

Standard Sahana-Agasti

Krakatoa (0.6 stable branch)

Sahana-Agasti

Vesuvius (trunk

branch)

Sahana-Eden trunk

RSS Y Y Y

EDXL-HAVE Y

XForms Y

CAP Y

PFIF Y [Note 1] Y

EDXL-TEP/TEC [Note 2]

KML Y Y

TMS Y Y

WMS Y Y

GPX Y

GML Y Y

GeoRSS Y Y

MGRS Y

Packing and Publishing Standards

Objective: Improve user experience and ease on

download, installation and configuration of Sahana software

Mechanism (consistency!) Installation software and packages Consistently supported OSs / VMs Website hosting of packages Installation, user and configuration guide

Quality Assurance

Risks of a life saving system Data corruption/integrity, performance issues,

security vulnerabilities, stability/fault tolerance Mechanisms

Scenario/Functionality Test Cases Performance testing Vulnerability testing

Domain Compliance

Objective Improve acceptance by Emergency managers

for adoption and integration of Sahana Mechanims

Identify ICS/NIIMS compliance measures Certify systems for compliance

Standards created so far

Challenge

Commitment to Standards Implementation Example: WIKI Standards

Root cause Volunteer time Standards are not the favorite thing to spend

your spare time on Need the support of the projects for

Enforcement and standards development

Next Steps

Establish Interop Standards WG Ontology, User Experience, Data Interop

Agreements Interop Workshops

PFIF EDXL-HAVE

Establish NIIMS/ICS compliance WG Participation in ISCRAM, OASIS, W3C

Next Event:ISCRAM Interop Workshop

http://www.humanitarian-ict.org/wiki/crisis-interop