<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=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi, <div class=""><br class=""></div><div class="">I want to share some follow up from our team (this is ongoing).</div><div class=""><br class=""></div><div class="">* We looked more closely at the issues of naming driveways. We identified a total of 16 changesets that had named driveways in them that we added, and we fixed these if they hadn’t been already.</div><div class="">* We have discussed and tightened up our best practices and policies dealing with evaluating and using external data sources, especially when the information conflicts with local mappers’ work. </div><div class=""><br class=""></div><div class="">The entire team appreciates your close scrutiny of our work. We feel bad about the mistakes we make, and the energy wasted on fixing. I know that we have also made a large number of good improvements to the map in Canada; improvements that will help especially navigation use of OSM.</div><div class=""><br class=""></div><div class="">Please don’t hesitate to share new and ongoing concerns. I will follow up as the team works on improving our process.</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Martijn</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Apr 25, 2017, at 9:55 PM, <a href="mailto:m@rtijn.org" class="">m@rtijn.org</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi all, <div class=""><br class=""></div><div class=""><div class=""><blockquote type="cite" class=""><div class="">On Apr 25, 2017, at 11:29 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 12:43 AM, Andrew Lester wrote:<br class=""><blockquote type="cite" class="">Okay Telenav, you win. …<br class=""></blockquote><br class="">Yes, that must be frustrating. Would hate to lose you as a contributor.<br class=""></div></div></blockquote><div class=""><br class=""></div>Alienating and driving away local contributors is the last thing we would want to accomplish!</div><div class=""><br class=""></div><div class="">Let’s try and move past hurtful statements about us and our intent, and towards some hopefully constructive ways to fix mistakes we have made and prevent future ones from happening.</div><div class=""><br class=""></div><div class="">Let me suggest this: I will take the concerns raised here to our team and get back to the list before the end of the week with proposed next steps to fix where possible. We will use Github tickets to track this. This is something new we are starting to make our work and processes more visible and transparent: <a href="https://github.com/TelenavMapping/mapping-projects/issues" class="">https://github.com/TelenavMapping/mapping-projects/issues</a>. You can follow along and chime in there as well. </div><div class=""><br class=""></div><div class="">My invitation to set up a town hall meeting with you and some of our team members also still stands.</div><div class=""><br class=""></div><div class="">Andrew — I added the issues you mentioned in your email as tickets. Some of them need more information to be actionable though, I hope you are able to provide some.</div><div class=""><br class=""></div><div class="">Stewart:</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">They're also adding futile turn restrictions at the join of one-way<br class="">on/off ramps, like this:<br class=""><br class=""> <a href="https://www.openstreetmap.org/relation/7096540" class="">https://www.openstreetmap.org/relation/7096540</a><br class=""></div></div></blockquote><div class=""><br class=""></div>That changeset was closed more than a month ago, we stopped adding these ‘implicit’ restrictions after the issue was first raised and it had become clear that there needed to be more discussion around them.<br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">(in a huge changeset, with the super-helpful comment “small updates”, no<br class="">less)<br class=""></div></div></blockquote><div class=""><br class=""></div>You’re right, that’s not very helpful at all — we actually recently tightened up our changeset commit best practices to avoid things like huge changesets and meaningless comments. We published this on Github as well (feedback welcome): <a href="https://github.com/TelenavMapping/mapping-projects/wiki/Changeset-Best-Practices" class="">https://github.com/TelenavMapping/mapping-projects/wiki/Changeset-Best-Practices</a></div></div><div class=""><br class=""></div><div class="">I hope this helps us move forward.</div><div class=""><br class=""></div><div class="">Martijn</div></div>_______________________________________________<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></blockquote></div><br class=""></div></div></body></html>