<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Yes, if you ask me, changeset comments are (and will stay) the #1 place to discuss mapping issues. If a mapper continues to do questionable edits, the public channels like this mailing list are a good place to go to. <div class=""><br class=""></div><div class="">To look at recent changeset comments, I use Pascal Neis’s tool. If you haven’t seen that yet you should definitely check it out: <a href="http://resultmaps.neis-one.org/osm-discussions?c=Canada#5/48.805/-99.802" class="">http://resultmaps.neis-one.org/osm-discussions?c=Canada#5/48.805/-99.802</a> </div><div class=""><br class=""></div><div class="">So like I said in my other response just now, GitHub issues are secondary to that, more like a convenient way for us to track and for mappers to see what projects we are proposing and working on, and if you happen to have a Github account you can also comment. </div><div class=""><br class=""></div><div class="">Sorry that was not more clear from the outset.</div><div class=""><br class=""></div><div class="">Martijn</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 26, 2017, at 10:22 AM, Stewart C. Russell <<a href="mailto:scruss@gmail.com" class="">scruss@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 2017-04-25 11:55 PM, <a href="mailto:m@rtijn.org" class="">m@rtijn.org</a> wrote:<br class=""><blockquote type="cite" class=""><br class="">Let me suggest this: I will take the concerns raised here to our team<br class="">and get back to the list before the end of the week with proposed next<br class="">steps to fix where possible. We will use Github tickets to track<br class="">this.<br class=""></blockquote><br class="">As a process suggestion, may I recommend some integration with OSM<br class="">changeset discussion? We ran into an issue last year when Mapbox was<br class="">also adding turn restrictions. There was some friction between local<br class="">mappers and Mapbox staff, as mappers asked questions in changeset<br class="">discussion and didn't see the tickets on Github, while Mapbox staff<br class="">didn't respond to the changeset discussion and assumed the Github<br class="">tickets were authoritative.<br class=""><br class="">I know that Github issues are the industry standard, and the OSM<br class="">comment/discussion mechanisms may seem a little quaint, but we risk<br class="">talking past one another if we splinter the discussion.<br class=""><br class="">cheers,<br class=""> Stewart<br class=""><br class=""><br class="">_______________________________________________<br class="">Talk-ca mailing list<br class=""><a href="mailto:Talk-ca@openstreetmap.org" class="">Talk-ca@openstreetmap.org</a><br class="">https://lists.openstreetmap.org/listinfo/talk-ca<br class=""></div></div></blockquote></div><br class=""></div></body></html>