<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>Partial solution is to stop cases where company is wasting time of everyone<br></div><div dir="auto">involved. And force said company to improve its editing quality.<br></div><div dir="auto"><br></div><div dir="auto">If some company is OK with damaging editing, ignoring feedback, ignoring rules<br></div><div dir="auto">etc, then even finding great solution and improvements will change nothing.<br></div><div dir="auto"><br></div><div dir="auto">I think that violations of <a href="https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines">https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines</a><br></div><div dir="auto">should be treated seriously.<br></div><div dir="auto"><br></div><div dir="auto">Specifically, user accounts should be actually blocked by DWG in case of mappers<br></div><div dir="auto">reporting lack of compliance.<br></div><div dir="auto"><br></div><div dir="auto">Currently this happens only in case of extreme damage, but should happen far <br></div><div dir="auto">more often. For example in case of user account not documenting properly<br></div><div dir="auto">itself to be paid employee and not linking to OSM Wiki documentation page.<br></div><div dir="auto"><br></div><div dir="auto">Right now various companies can mostly ignore complaints because they <br></div><div dir="auto">are allowed to continue editing in violation of our rules.<br></div><div dir="auto"><br></div><div dir="auto">(This is about Ticket#2020103010000191 Ticket#2021071410000126 reports<br></div><div dir="auto">that resulted in no blocks despite that employees are ignoring most of<br></div><div dir="auto">OEG, including parts trivially easy to actually do.<br></div><div dir="auto"><br></div><div dir="auto">They repeatedly damaged data, mislead about what will be edited, <br></div><div dir="auto">ignored feedback etc. All of that is irritating for mappers and overall value<br></div><div dir="auto">of their activity is negative. Some blocks happened but over 8 months ago, <br></div><div dir="auto">were completely ignored and account is not blocked since that time.)<br></div><div><br></div><div><br></div><div>Oct 17, 2021, 01:32 by jwhelan0112@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="auto"><div>I think the problem is more can we find a different metric for paid mappers to be evaluated on.<br></div><div dir="auto"><br></div><div dir="auto">I accept whatever we choose can be gamed to some extent but if we could measure how many kilometers of highway had been added rather than how many had had their tags updated that might help.<br></div><div dir="auto"><br></div><div dir="auto">Offering guidance to someone who is paid according to how they are measured may not help. Would you deliberately reduce your income if it meant doing things correctly? You might but others might not.<br></div><div dir="auto"><br></div><div dir="auto">Perhaps how many nodes they have added to the map? Plus how many new tags? Can these be measured?<br></div><div dir="auto"><br></div><div dir="auto">Cheerio John<br></div><div dir="auto"><br></div><div dir="auto"><br></div></div><div><br></div><div class=""><div class="" dir="ltr">On Sat, Oct 16, 2021, 19:09 stevea <<a href="mailto:steveaOSM@softworkers.com" rel="noopener noreferrer" target="_blank">steveaOSM@softworkers.com</a>> wrote:<br></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class=""><div>On Oct 16, 2021, at 3:41 PM, Justin Tracey <<a rel="noopener noreferrer" target="_blank" href="mailto:j3tracey@gmail.com">j3tracey@gmail.com</a>> wrote:<br></div><div> > FWIW though, I've personally found that politely reaching out to score-seeker contributors, even if they don't reply, is usually (though not always) enough to get them to at least greatly reduce the problematic behavior in question.<br></div><div> <br></div><div> Excellent, Justin; me, too. I'd even say that MOST of this time, a "reduction" is exactly the (expected) result. But when it is not and stronger measures are required, well, it's time to apply stronger measures. It is as simple as that.<br></div><div> <br></div><div> Bad behavior in OSM must be addressed, and I know that our DWG do "yeoman work" that I and virtually everybody appreciate. But as DWG likely can't do everything (maybe someday they can?) other conscientious users, especially those with the skills to properly wield powerful tools like changeset reverting, remains necessary. Please, be a respected member of the OSM community if / as you use these tools and use them conscientiously in the rare cases when you might find them a requirement.<br></div><div> <br></div><div> Yes, it can be a fine line to determine if somebody (whether through sheer ignorance — understandable and somewhat excusable with the correct attitude of apology and "how can I improve?" — or whether deliberate, determined ill will) is damaging our data inadvertently or with malicious intent. The usual "escalation" steps, starting with contact (and their reply can speak volumes as to what they really mean to do, although there truly are covert actors and real-life liars), moving up to DWG reporting, are correct. "Score seeking" behavior, seemingly only recently (and openly) identified as problematic, might be considered "more mild" forms of damage to our data, but it, too, should be "nipped in the bud" where it is identified.<br></div><div> <br></div><div> Let's not forget the simple tenet that "abuse is abuse," also stated "damage is damage" or even "vandalism is vandalism." I know that good, earnest communication can often "fix" an errant (and apologetic) volunteer's efforts gone awry, these are actually opportunities to level-up novice mappers to become BETTER mappers. But: fifth chances, ninth chances, seventeenth chances...no. We must be ready and willing to excise such cancer.<br></div><div> <br></div><div> SteveA<br></div><div> _______________________________________________<br></div><div> talk mailing list<br></div><div> <a rel="noopener noreferrer" target="_blank" href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br></div><div> <a target="_blank" rel="noopener noreferrer" href="https://lists.openstreetmap.org/listinfo/talk">https://lists.openstreetmap.org/listinfo/talk</a><br></div></blockquote></div></blockquote><div dir="auto"><br></div> </body>
</html>