search

hotosm / osm-tasking-manager2

Designed and built for Humanitarian OpenStreetMap Team collaborative emergency/disaster mapping, the OSM Tasking Manager 2.0 divides an area into individual squares that can be rapidly mapped by thousands of volunteers.
http://tasks.hotosm.org
Other
425 stars 156 forks source link

Project creation discussion tools #873

Open cgiovando opened 7 years ago

cgiovando commented 7 years ago

As part of TM v3, I would like to propose the development of coordination tools allowing project managers to discuss and review projects being created. This could be as simple as a discussion board directly displayed for each task to discuss project design, purpose, issues, etc.

bgirardot commented 7 years ago

I am not sure this is right for the TM. I think these discussions already happen in other typical coordination channels. We do not need yet another coordination channel and have to create a comms apparatus in the tm. Feeding from the TM to other comms channels is something we will do. So slack integration or an ircbot or something to feed data from the TM to 3rd part coordination channels.

bgirardot commented 7 years ago

I should also add that tools to visualize projects during project creation is a for sure feature needed. The other text and voice comms part I am less enthused about.

ethan-nelson commented 7 years ago

I'm working on another issue about the overview map, but with functionality I'm adding, we could add display polygons for, say, the most recent 50 projects on top of the project drawing screen (I think that's what you're talking about, Blake).

cgiovando commented 7 years ago

@ethan-nelson that would very helpful! If we can include filtering, even better, so for example when drawing a project in an area where previous ones have been created, the user could see their extent and filter by type or date (e.g. only building-tracing projects within the last year).

@bgirardot - I think contextual communication within the tasking manager is very important and something that we should try to include as part of this new development. I would prioritize communication for the end user (mappers), but even a simple option to comment on backend project creation would be helpful for coordination.

Communication channel fragmentation is definitely a concern, so I would look at options to integrate existing tools (see this example from @smit1678 http://nateasmith.org/map-sidecar/) rather than adding yet another chat platform.