| 1 | '''Status Meeting Notes - 20 January 2010'''[[BR]] |
| 2 | [[BR]] |
| 3 | ''Attending:'' mprutsalis, flavour, bitner, chamindra, lifeeth[[BR]] |
| 4 | [[BR]] |
| 5 | |
| 6 | '''Priorities''' [[BR]] |
| 7 | * '''Rest:''': everyone should get minimum 6 hours per night. Suggest midnight to 6 am or 1 am to 7 am local – we have good round the globe coverage with flavour & nursix in Europe, mprutsalis & bitner in US, timclicks & gavin_t in NZ, chamindra & lifeeth in Sri Lanka/India. We will coordinate handovers and try not to work through the night locally.[[BR]] |
| 8 | * '''RMS''': highest priority application. We have good feeds coming in from Ushahidi (4636 shortcode SMS messages) and twitter (Tweak the Tweet). Next steps are ticketing/tracing and reporting on unfulfilled vs. fulfilled requests, getting aid agencies to use, filtering actionable messages, pushing data back to Ushahidi. Assignments:[[BR]] |
| 9 | * Nicolas Preston (nicopresto) has lead on tech dev. [[BR]] |
| 10 | * gavin_t & nicopresto & bitner to liaise with Ushahidi in sms logistics skype chat. [[BR]] |
| 11 | * mprutsalis has lead on outreach to OCHA, USG, Interaction.[[BR]] |
| 12 | * '''Release Management''': see ReleaseManagement [[BR]] |
| 13 | * '''Org Registry''': also a high priority - we are still struggling to get data in from OCHA PaP from almost 2 days ago (entry taking place now). Assignments: lifeeth looking at csv import issues so can create repeatable process [[BR]] |
| 14 | * '''GIS''': bitner to update on priorities and next steps when available [[BR]] |
| 15 | * '''Migration of Sahana.lk''': we are migrating sahana.lk to a hosted site on godaddy as sahanafoundation.org. Starting with mirroring, we will then migrate to make sf.org the primary site for the foundation and wiki and transfer DNS control to godaddy. Assignments: Dan Zubey (dzubey) & chamindra have lead supported by mprutsalis. |
| 16 | * '''Validating Users''': given personal data contained in RMS feeds and sensitive contact data contained in OR and PR, we need to revalidate all registered users on the production site to ensure that they are from an organization or otherwise should have access to this data. New requests for accounts should not be automatically approved without personal screening if e-mail domains are doubtful (i.e. gmail accounts vs. redcross.org which is obvious). Assignments: mprutsalis to lead; will ask timclicks for assistance.[[BR]] |