<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt"><div><span>Tasking Manager ideas</span></div><div><span><br></span></div><div><span>Chat rooms could be good.</span></div><div><span>As with the polygon areas you've been developing, it does remind me more and more of the tool called "MapCraft" which already exists, and which we *could* already use for HOT stuff in fact. We use it London mapping parties. It's quite neat</span></div><div><span>http://wiki.openstreetmap.org/wiki/MapCraft</span></div><div>It's a shame it's written a different language (php vs python), otherwise we could move for some sort of convergence.</div><div><br></div><div>But anyway we can learn from it. The chat room feature on MapCraft isn't all that useful. It's quite well implemented. Also used as a sort notification panel for things like "user X has taken area number 12". But... we mostly miss
each other, and leave messages for eachother there rather than doing live chat, or we do live chat because we were just live chatting on IRC two seconds earlier (not achieving much). </div><div><br></div><div><span class="Apple-style-span">So I'm thinking a chatroom feature on the tasking manager might be more lively and better used if it was simply a view onto the #hot IRC channel. This would also make the IRC channel </span>more lively and better used<span class="Apple-style-span">. Maybe you were thinking of having a different chatroom per job.</span></div><div><br></div><div>Thinking wider... maybe a chatroom on the tasking manager website is the wrong place for it. How about a chat plugin for JOSM? It maybe fits into ideas of making OSM more sociable in general</div><div><br></div><div><br></div><div>On the topic of editing job instructions. The task manager website could take a feed from the osm wiki. Scrape
fragments from present areas of wiki content, from a URL such as http://wiki.openstreetmap.org/wiki/Task_manager_jobs/9 This would let more people contribute, while saving you re-implementing wiki style auditing of edits.</div><div><br></div><div>For the Padang job I added a screenshot of a completed square http://tasks.hotosm.org/job/9 A picture tells a thousand words. It conveys not only the kind of data that we're expecting, but also what the imagery is supposed to look like when you finally get those fiddly URLs to work. Perhaps example images should either be an explicit field to be filled in, or at least a guideline for those creating job descriptions.</div><div><br></div><div>Harry</div><div><br></div><div><br></div> <div style="font-size: 10pt; font-family: arial, helvetica, sans-serif; "> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <div dir="ltr"> <font size="2" face="Arial">
<hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Pierre Béland <infosbelas-gps@yahoo.fr><br> <b><span style="font-weight: bold;">To:</span></b> hot <hot@openstreetmap.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Wednesday, 30 May 2012, 21:55<br> <b><span style="font-weight: bold;">Subject:</span></b> [HOT] Re : Blog post about last weeks Camp Roberts/RELIEF Mapping<br> </font> </div> <br><meta http-equiv="x-dns-prefetch-control" content="off"><div id="yiv1561207401"><div><div style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255); font-size: 10pt; font-family: arial, helvetica, sans-serif; "><div><span>Kate, <br></span></div><div><br></div><div>This bring us back to the idea of having something like a chat room to exchange. <span>For every task, we are confronted to particularities that emerge while mapping. When we start a project, if we invite mappers to chat, people will be able to
exchange experience, exprress difficulties and propose suggestions such as particular tags, little tricks, plugins, Presets. These discussions should also bring some content to edit the task instructions.</span></div><div> </div><div><span style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;">Pierre </span></div></div></div></div> </div> </div> </div></body></html>