qwaletee wrote:Pesach,

Ideally, that would be nice. One of my driving factors is that I spend hours each week just keeping on top of Brooklyn URs, so that the borough doesn't just become a mess of bubbles. Unfortunately, that sometimes forces me to keep the etiquette to a polite minimum. I don't know if others find themselves in a similar position, but I personally wouldn't want to be HELD to such a standard.

I use standard replies which I copy and paste from a note application and then modify when necessary.

Sent using Tapatalk for Android 4.4.2

DwarfLord wrote:For anyone interested, I've put up a wiki of my own homebrew canned responses for the most common situations I've encountered. It's one way to have common cut-and-paste answers handy while sharing them with others too.

I'm pretty happy with these for my purposes and not too interested in tweaking them further, but if I'm wrong about anything of course I'd sure like to know. I post the link here simply as suggested raw material.

https://wiki.waze.com/wiki/User:DwarfLord/UR

I posted some of my canned responses to my wiki namespace as well.

You can see them and copy for yourself, feel free to tailor to your needs.
My UR canned responses

qwaletee wrote:I posted a bunch of mine on one of the forums posts, have to hunt them down, because I don't have access to the usual file this second.

Of course, that's better than my phone situation, which I won't have access to for a while... broken screen.

my deepest condolences[emoji22]

Sent using Tapatalk for Android 4.4.2

qwaletee wrote:

PesachZ wrote:

qwaletee wrote:I posted a bunch of mine on one of the forums posts, have to hunt them down, because I don't have access to the usual file this second.

Of course, that's better than my phone situation, which I won't have access to for a while... broken screen.

my deepest condolences[emoji22]

Sent using Tapatalk for Android 4.4.2

Only question is, what now. I was only 4-5 months into the contract. No insurance. The part costs $60-$90, and I'm technically-oriented, but the teardown procedure is pretty complicated (I believe 13 screws, prying off of about five glued layers, and removal of about 8 latches, 6 ribbons, and 6 sensors, ebfore even getting to the glass). And I worry mre about build-up than tear-down.

I've herad LG offers repair at about $150 plus shipping and wiat time.

weigh the difference between the replacement cost and the repair cost less the repair parts against your time and confidence in your repair abilities.

repair $150-($75 parts + 2 hrs labor rate ~ $30)= $45
The savings of DIY vs Lg is $45 and the risk is ($75 parts + 2 hrs labor rate ~ $30 + new phone $500) - $150 what repair would have cost = $455

I personally would send to lg or a third party repair shop which guarantees their work if it is a decent phone worth >$300

Sent using Tapatalk for Android 4.4.2

qwaletee wrote:So I jumped on the bandwagon (which I guess I sort of instigated), and moved my stuff to the Wiki.
https://wiki.waze.com/wiki/User:Qwaletee/UR-boilerplate

maybe we should create a subjection in the UR wiki with links to all these personal page, noting that they are ones for inspiration, can be copied, but are not official.

Sent using Tapatalk for Android 4.4.2

DwarfLord wrote:
Don't know about you but I get a bit punchy after doing too many of these. General-error UR: "It's red" My answer: "What's red? What color should it be?"

That's when I know it's time to turn off the UR layer and start doing FC upgrades.

Sent using Tapatalk for Android 4.4.2

IMHO, I would not put time frames or anything that implies any kind of deadline in the message to the reporter, or even any messages the reporter can see. I agree this can put undue pressure on the reporter and even less willing to work with us, while we rely on their sheer good will.

That being said, we should definitely establish and publish (which we might have already - the 7-day rule?) concrete and objective guidelines of when something should be closed in order to prevent editors from bulk-closing URs for a few points.

Maybe we shouldn't close URs initially responded to by someone else without at least trying to ask that editor first? I don't think that's unfair to have to ask, but I would request we use PM or some other means where the reporter cannot see that we're trying to get rid of the UR.

I would recommend keeping questions to the reporter as short and on-point as possible. Maybe introduce yourself as a volunteer editor (it definitely humanizes us to the greater world of Wazers) in a sentence and ask your question in another. There's no need to enumerate that you couldn't find anything wrong; if it weren't for that you wouldn't be asking the question.

General Error:
Hi, I am a volunteer editor for Waze. Can I ask what went wrong here?

Incorrect turn direction:
Hi, I am a volunteer editor for Waze. Can I ask which turn was wrong and why?

Etc, etc...

First paragraph!? You gotta be kidding me. As a reporter, I'd be over it and moving on halfway through the first paragraph. I actually like txemt's approach.

I live in northern NJ where we see hundreds (if not more) URs a week, most of which end up referring to things that cannot be fixed in WME. Ain't nobody got time for that!

I try not to NI any URs until they've turned red and it's been 7 days since the last thing was said in the conversation (whichever comes later), unless I've determined from the conversation with the reporter that there is no map issue, and explained it to them. If a UR is already red when I respond to it, it's unlikely the reporter will remember what went wrong, especially if it was something subtle, but I usually apologetically ask, briefly referencing the street and city, and if there's no conversation after 7 days, it can be NI-ed either by me when I cycle back around to the area or by anyone else there. Never do I say anything that would make the reporter feel like there's a deadline to answer; we are relying on their goodwill to share with us their knowledge of the roads and we need to respect and appreciate that.

URs with actual conversations are more of a gray area. You have to judge by the conversation and its timestamps what may or may not be going on and maybe even PM the last editor to take part in the conversation to get an update. I don't like to expose to the reporter that I'm trying to ping a case that I'm thinking might have timed out, so often a PM to the editor works better than a conversation comment. For example, many URs I come across have to do with incorrectly located destinations, many of which need to be corrected on Google Map Maker. This can take an indeterminate amount of time, depending on how familiar the community over there is with any particular editor, since that's what appears to drive their review process. I personally, like to keep Waze URs open until I have a testable outcome that places the the destination's pin the correct spot. This can easily sometimes involve a couple weeks of no conversation interaction in the UR, especially if I can't get to Waze on a computer every single day during that time.