@jasonh300 I think you're being overly critical and restrictive. This is a collaborative environment and the handful of country managers can't fix everything. We've got to have newer editors looking at URs and looking to solve map issues too.
I didn't even think URs showed up outside a user's editable area, which means they could have rights to fix the issues within that area. If URs show up everywhere now, that's a WME issue which should be fixed.
jasonh300 wrote:So now, the lower level user has to ask for an unlock, or ask for someone else to fix the problem, creating additional complication.
As long as the lower-ranked editor does that, is it really such an issue? How is it any different than a low-ranked editor running across the same problem during their normal editing of the map and posting an unlock request in the forum?
I agree. Just because there is a conversation going on, asking for an unlock is no different now than before. Hundreds of editors every month ask for unlocks because of a UR they can't resolve due to rank. This is a normal part of the editing workflow. This is not
an additional complication. We've been doing this for years.
jasonh300 wrote:We've worked on and tested this feature for 6 months now to make it a DIRECT communication between the editor and the reporter. Obviously this isn't how it's going to work now that everyone has access to it. This is quickly going to turn into an unmanageable mess.
I disagree. Now I don't have to worry about trying to solve ALL URs in my area using conversations. What I didn't think about in testing is a way to quickly, visually ID URs which I have participated in. Like the Participated list for the forum in Tapatalk.
elle-emme wrote:If you worked on and tested it for six months, then how did this issue never come up? Did no one ever bring up the possibility of rank-locking conversations according to the rank lock of the road the UR was reported on?
But a good % of URs aren't about the road they are reported on anyway, so that's one reason it didn't come up. And I don't think it is worth the effort to pursue as a feature. The whole "issue" with multiple editors being involved in URs and the possible problems with it was partly due to not a lot of overlap between editors. But even before public release, we had issues with URs being closed improperly and having a conversation tool is not going to change it.
elle-emme wrote:edit: also, if it's such a big deal that plebeian editors are forbidden from initiating conversations on roads that are rank-locked and only patrician editors should do so, why isn't it addressed in the Wiki article about URs and conversations?
IMO, it isn't, and therefore, it isn't.
Regarding this, and the instant case:
I don't think low-level editors should be locked out of starting conversations. That's too extreme, and it doesn't really get to the heart of the problem here.
The problem in the instant case is that the low-level editor in question is immediate-blanket-responding in sloppy English to every UR in an area, 80 miles from his managed area, which is managed quite well by two Level 6 Country Managers.
As a matter of simple etiquette between editors
, in proactively managed areas, editors who, (1) do not manage the area in question, and (2) are not local to that area, should allow a few days for the area manager, or someone local to the area, to follow through with editors first.
Managers and locals know their area best, and are best suited to fix issues in their area. If they're not on top of things, of course, other editors can come in and help out. But inexperienced and/or sloppy editors who take a day trip to a city with a well-maintained map are not in a position to help nearly as well as the editors who maintain that map so well.