SSF : Overlays on the map; project_project controller changes

* Adding hazard, theme, countries to the deployments form
* Permission to anonymous to create task, contributor role
* Deployments, members overlay on the map
* Inline login form
Err - right. That's what I meant with "who's going to maintain all this information?". Starts with investigating it, entering it, reviewing and updating it, and correcting it if the respective organisation wants it changed.

I highly doubt that the user organisations would take responsibility for that - so it's on us, thus we should only do that /if/ it helps /us/ with what we do. 

Surely I can smell the "marketing" argument lurking around the corner? Fancy statistics are good for marketing, especially in picture-form. Remember the gizmodo chart?
http://gizmodo.com/5977989/internet-explorer-vs-murder-rate-will-be-your-favorite-chart-today

I'm sure we could do something similar. I'm also sure we most likely need to be more restrictive with what we spend our resources on. So I see a lot of dead data in the Sunflower database, unmaintained and unused.

Maybe we should abstain for now, and activate once we feel an urgent need to track this and a realistic maintenance process?