InaSAFE Workshop September 2014 - mf4dl1/jaksafe GitHub Wiki
Concept
A 'all hands' workshop for technical stakeholders (those involved in development, design, implementation, training and deployment of InaSAFE) to meet to collaborate and find ways to strengthen our cooperation, planning and effectiveness.
Venue
It is proposed to hold the event at the AIFDR offices in Jakarta (subject to availability).
Dates
Our proposed dates are:
- Session 1: High level strategic planning and roadmap session
- Session 2: Architecture and Impact Function design session
- Session 3: Coding and proof of concept session
- Session 4: Wrap-up session
Sessions:
Session 1: High level strategic planning
Date: Mon 22 September, 2014
Goal: This is a one day workshop. The goal will be to address issues of project governance, intra and inter-organisational collaboration, strategic funding / resource allocation towards shared initiatives, removal of impediments and the sharing of organisational visions with regards to InaSAFE.
Target audience: project managers and decision makers (with open participation from all team members).
Detail: The goal here should be to produce a matrix of what the role player's plans are in terms of InaSAFE programs and software development so that we can ‘work smart’ by sharing the workload and not duplicating effort or derailing each other’s activities.
So each participant should be thinking in terms of:
- What activities are we undertaking that others in the room can benefit from (e.g. plans for a new impact function, user interface, training materials etc.)
- Who in the room is doing things that we can use and benefit from? What input can we give them from our experiences to make their activities more useful to us.
- What resources (financial, HR, knowledge, tools and materials) can we contribute to the collective in order to make InaSAFE more effective.
You should come to the workshop ‘bringing something to the table’ - the aim is to improve the software and the programme through strategic planning to make it more effective and useful.
Architecture and Impact Function design
Date: Tue 23, Wed 24, Thur 25 September, 2014
Goal: This three day session will be dedicated to defining the architecture of InaSAFE for the next year of development in terms of 'big ticket' items. These will include (but not limited to):
This session is for developers and ‘power users’ who want to have a hand in shaping the development of InaSAFE. You do not need to be a programmer, but you should not be afraid to roll up your sleeves and dig into the technical details of the InaSAFE project.
We will be using an 'unconference' format (see http://en.wikipedia.org/wiki/Unconference ). A number of 'spaces' will be available and a board outside each space will list ‘birds of a feather (BOF)’ sessions to be held in that space. On the start of each day we will have a group session (space 1) and then break out to BOF sessions. Spaces can be block booked (to e.g. occupy the whole afternoon or day) as needed.
On the first day the group session will be used to layout the key architectural plans and requirements and to ‘recruit’ participants into the various BOF sessions. On the second and third day the first session will be a review session where convenors of the previous day’s BOF’s will report back on the work they have been doing and ask for feedback, help etc.
The purpose of this workshop is to develop a number of RFC’s which describe in detail how various aspects of the InaSAFE project should be developed. For reference you may wish to look at our RFC writer’s guide (https://github.com/aifdr/inasafe/wiki/How-to-write-an-RFC). Session II is product oriented - that means you should attend the workshop with the expectation of actively contributing to the creation of one or more RFC’s. Please note that the RFC process is for ‘big picture items’ which means we do not typically want to hold a workshop on, for example, how a particular widget on a form behaves (just file an issue for that). More appropriate would be e.g. a proposal for a new impact function, or a proposal to change the structure of our documentation to make it easier to use. Below you will find a list of the suggested topics for RFC creation (but more may arise through the needs expressed from participants).
BOF Sessions:
Tuesday:
| Session | Space 1 | Space 2 | Space 3 | Space 4 | Space 5 |
|---|---|---|---|---|---|
| 1 | Landcover | Population | Philippines | ||
| 2 | Unification of Hazard data to polygons | Reporting | WebSAFE |
Wednesday:
| Session | Space 1 | Space 2 | Space 3 | Space 4 | Space 5 |
|---|---|---|---|---|---|
| 1 | Documentation | Categorical hazards ESSC notes | |||
| 2 | InaSAFE as a service | landslide and new IF | people in buildings | ||
| 3 | network analysis linking | documentation |
Thursday:
| Session | Space 1 | Space 2 | Space 3 | Space 4 | Space 5 |
|---|---|---|---|---|---|
| 1 | InaSAFE SCRUM and Release Management | ||||
| 2 | DaLA | ||||
| 3 | Metadata Basics |
Friday:
| Session | Space 1 | Space 2 | Space 3 | Space 4 | Space 5 |
|---|---|---|---|---|---|
| 1 | To rasterise or interpolate, categorical & continuous data |
Some ideas for BOF’s:
- Standardisation and improvement of metadata in InaSAFE
- Refactoring the safe package
- Proposal to disband the use of gettext
- Proposed new architecture for InaSAFE Realtime platform
- The InaSAFE user map
- How will we model people in buildings?
- Integration of InaSAFE with InaWARE/PDC - Wednesday pm
- How will we model land cover and what will the actions be?
- How can we make actions more useful, localised (e.g. for a given country) and data driven?
- Unification of hazard data as polygons (https://github.com/AIFDR/inasafe/issues/949)
- What's wrong with raster resampling and what will we do to fix it?
- What should a generic impact function do and how will we express it’s actions?
- What are the requirements for network analysis linking affected people and IDP’s?
- wholesale adoption of QGIS libraries for GIS computational work to build a new 'slim core' package
- Requirements for new impact functions
- Determination of standardised Impact Function behaviours (e.g. buildings as proxies for people)
- Clipping, sampling and pre-processing of input data
- DaLA (Assefa to lead discussion)
- IF for flood hazard with categorical values (#1105, #1091)
- Ways to integrate InaSAFE to PH LGU disaster preparedness journal
- Data format translation (raster to vector, resampling, etc.)
- land cover data
- Categorical data
Spaces
Each space will have a space form printed up and posted outside it for each day. Participants to fill in their names. If no / not enough participants register, the session will be cancelled. If more register than the room can handle, an attempt should be made to swap out with a larger space.
Example Space form:
Space Form: __________ September 2014 : Space __ Only space 1 will be used in the morning 1 slot - it will be used for the group session.
| Time slot | Topic | Participants (convenor underlined) |
|---|---|---|
| Morning 1 | Group session | Only space 1 is used for morning 1 |
| Morning 2 | ||
| Afternoon 1 | ||
| Afternoon 2 |
Target audience: Software developers and domain specialists (with open participation)
Coding and proof of concept
Dates: Fri 26 September, Sat 27 (public session), Mon 29, Tue 30, 2014
Goal: This session will be a 'hands on coding' session, with a particular goal to create a proof of concept minimalist core library that utilises QGIS processing libraries and is deployable in both desktop and web contexts.
The session will also serve as a platform for deeper technical discussions about implementation and coding matters.
The open session on Sat 27 September will be an open / public workshop for the Jakarta python developer community to build on the technical coding session held and hosted by AIFDR in June 2014 as well as the Code for Resilience event on InaSAFE held in May 2014 at BPBD and supported by GFDRR and the World Bank and AIFDR. The goal of this workshop will be to further the incubation of in-country knowledge and expertise in QGIS plugin development (with the intent of fostering future InaSAFE developers from the local community).
Target audience: Software developers (with open participation)
Wrap-up session
Dates: Tuesday 30th (either morning or afternoon)
Goal: The session goal is to summarize what was done during the work shop and highlights some of the decisions and upcoming features that will be available in InaSAFE.
Target audience: Project managers and decision makers (with open participation from all team members).
List of Workshop Attendees
Note: If you do not have write permissions for this table, please contact [email protected] or [email protected] and request to be added to the table below (supplying details as needed).
Column key:
- 1: Session 1
- 2: Session 2
- 3: Session 3
- 4: Session 4
- I: Invite needed - enter Y here if you need an official invite for visa etc. purposes.
| # | Name | 1 | 2 | 3 | 4 | Comments | I | |
|---|---|---|---|---|---|---|---|---|
| 1 | Tim Sutton | [email protected] | Y | Y | Y | none | ? | |
| 2 | Charlotte Morgan | [email protected] | Y | Y | Y | none | ? | |
| 3 | Kate Chapman | [email protected] | Y | Y | Y | none | ? | |
| 4 | Akbar Gumbira | [email protected] | Y | Y | Y | Not available for weekend | ? | |
| 5 | Yantisa Akhadi | [email protected] | Y | Y | N | none | ? | |
| 6 | Harry Mahardhika Machmud | [email protected] | Y | Y | N | none | ? | |
| 7 | Wulansari Khairunisa | [email protected] | N | Y | N | none | ? | |
| 8 | Dewi Sulistioningrum | [email protected] | N | Y | N | none | ? | |
| 9 | Ranie Dwi Anugrah | [email protected] | N | Y | Y | none | ? | |
| 10 | Adityo Dwijananto | [email protected] | Y | Y | Y | none | ? | |
| 11 | Vasanthi Hargyono | [email protected] | Y | Y | N | none | ? | |
| 12 | Ariel Nunez | [email protected] | Y | Y | Y | none | ? | |
| 13 | Yewondwossen Assefa | [email protected] | Y | Y | Y | none | ? | |
| 14 | Ismail Sunni | [email protected] | Y | Y | Y | none | ? | |
| 15 | Whisnu Yonar | [email protected] | Y | Y | Y | none | ? | |
| 16 | Noel Pitoy | [email protected] | Y | Y | Y | Not available for weekend | ? | |
| 17 | Elida Nurrohmah | [email protected] | Y | Y | N | none | ? | |
| 18 | Marco Bernasocchi | [email protected] | N | Y | Y | TBC | ? | |
| 19 | Mahardika Fadmastuti | [email protected] | Y | Y | N | none | ? | |
| 20 | Maning Sambale | [email protected], [email protected] | Y | Y | Y | none | Y | |
| 21 | Dianne Bencito | [email protected] | N | Y | Y | none | Y | |
| 22 | Jen Alconis | [email protected] | Y | Y | N | none | ||
| 23 | Noelyn Morales | [email protected] (NOAH) | N | Y | Y | none | ||
| 24 | Yerola Sipayung | [email protected] | Y | Y | Y | none | ? | |
| 25 | Hendry Yang | [email protected] | Y | Y | Y | none | ? | |
| 26 | Emir Hartato | [email protected] | N | Y | N | will attend from 24th Sept | ? | |
| 27 | Faizal Thamrin | [email protected] | Y | Y | Y | none | ? | |
| 28 | Dian Oktiari | [email protected] | Y | ? | ? | none | ? | |
| 29 | Intan Pujawati | [email protected] | N | Y | N | none | ? |