Martin, could you take a look at my last reply to Tobias - I have actually expressed some concerns with bots in general (very surprisingly, considering my heavy involvement with it previously). I think this tool can actually make the path to bots easier for the community, making new bots safer and reduce the chance of an accidental programming bug -- Tobias "case #1".
I do hear your concern about the "distributed auto-fix", and we should minimize the negative effect. I think the best way would be to have a good community process to propose, evaluate, and approve such queries. Currently, anyone can add create a challenge in MapRoulle without oversight. Only a few devs might see changes in Osmose or the JOSM's autofix (my reply to Tobias actually focuses on JOSM issue, and I think its the most important issue). Here, we could use our wiki to host all queries, e.g. a "proposed" page where everyone will be instructed to be very careful with the changes, as queries have not been extensively vetted, and "approved" - queries that even bots can run automatically. We could have both locally oriented and globally oriented queries. Basically, if anyone wants to cause havoc, they can do it with any tool, but if the person wants to really help, we can guide that help towards the most beneficial contribution. Lastly, it won't be too hard to track which query was used - I can add the query ID to the changeset tag, so if an experimental query starts getting mass-edited, it can be easily discovered. Hope this helps. On Mon, Oct 16, 2017 at 6:13 AM, Martin Koppenhoefer <dieterdre...@gmail.com > wrote: > Frederik: > >> I am appalled that after your abysmal OSM editing history where you more >> often than not ignored existing customs rules, while *claiming* to >> follow them, you're now building a service that entices others to do the >> same. >> > > > >> On Sat, Oct 14, 2017 at 6:09 AM Christoph Hormann <o...@imagico.de> wrote: >>> This is a tool to perform automated edits as per the automated edits >>> policy. A resposible developer of such a tool should inform its users >>> that making automated edits comes with certain requirements and that >>> not following these rules can result in changes being reverted and user >>> accounts being blocked. >>> >> > 2017-10-14 13:06 GMT+02:00 Yuri Astrakhan <yuriastrak...@gmail.com>: > >> Christoph, I looked around Osmose and MapRoulette, and I don't see any >> such warnings . Could you elaborate how you would like these kinds of tools >> to promote good editing practices? Any UI ideas? I'll be happy to improve >> our tools on making sure they meet community expectations. >> > > > I agree with Christoph and Frederik, that this is oviously a tool to > perform (crowdsourced) automated edits, and although it is designed in a > way to make them look like individual contributions, the automated editing > guidelines should apply. I agree with Yuri that there is also (to some > lesser extent, as the editing is not performed by the tool) some > problematic potential in other QA tools like Osmose or "remote batch > fixing" tools like MapRoulette. > > The thing with remotely "fixing tags" is that people usually don't know > the situation on the ground and therefore hardly can make an individual > decision for the specific object. The proposed "one-click-solution" > encourages to do quick "fixes" without looking individually, and you even > refuse to notify people that they might be participating in an automated > edit. In examples like the one you gave, even if you look very hard, you > won't see something that confirms the proposed change (you will have to > know the place). I could imagine there are good cases where your tool can > facilitate fixing problems, e.g. with clear typos (highway=residental), but > changing from one tag to a combination of two is not one of them (either we > could make an automated edit, or if it's disputed, we wouldn't do it at > all, rather than sneaking it in via distributed automated editing). > > Cheers, > Martin > >
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
