Idaho/Community/Main: Difference between revisions View history

Latest revision as of 04:27, 10 May 2018

Press here to return to the Community section to see your changes

Communications

Our community uses Discord to facilitate communications. Idaho has channel on the Northwest USA Discord server, which is used to chat with local editors and area/state/regional management. If you're a new/existing editor in Idaho or even if you're just visiting and want to relay information to local editors you can do so by clicking the link below to jump into the group. All editors are also encouraged to join the national server. Links are below:

Join the Idaho Channel of the Northwest USA Discord Server
Join the USA National Discord Server

Discord has a free app available for Windows, MacOS, and Linux computer platforms as well as Android and iOS mobile platforms. You may also use the Discord website to access our Discord channels if you prefer.

Visibility

While editing in Idaho, editors must not use Invisible mode. Editors are not required to socialize in chat, but are expected to respond to inquiries about their edits if questions about them arise. If you decide to minimize chat, please consider using the WME Chat Addon so that you can be "pinged" if somebody needs to talk to you.

Coaching

All editors of Idaho need to be willing and able to accept coaching from any area/state/regional management, as well as peers and outside area management, and then use that coaching to make appropriate corrections. We maintain a strong community by being on the same page with how the mapping should be done. The goal in coaching is to help you improve the experience that Wazers will have when using the app. It is not meant to criticize the way you have gone about a solution, but rather refine it to exceed the needs of our Wazers and to meet the standards set for the map.

You may receive inquiries by Personal Message (PM) if you aren't able to be reached in WME Chat or Discord. Please respond ASAP to any messages you receive (the expectation is a response within 48 hours under most circumstances).

Disciplinary Action

Editors that do not respond to inquiries about their edits, choose not to make appropriate corrections after being coached, and/or cause deliberate damage to the map, etc., may, depending on severity, receive consequences including but not limited to: mandatory formal mentoring, temporary suspension of editing privileges, and permanent loss of editing privileges.

Update Requests

We are the face of Waze to the majority of Wazers and we want to be sure our Wazers are getting the best experience they can. Sometimes things don't go well while Wazing and Update Requests (URs) are submitted to bring those issues to our attention.

The general guidance to working URs in Idaho is the same as the national guidance. We really emphasize that editors answering URs need to have strong people skills and a solid knowledge of Waze map editing so the issue can be successfully and promptly resolved in one report. If the issue becomes something above your ability (e.g. skills and/or rank), or the Wazer becomes unprofessional, please bring it to the attention of an area or state manager.

The keys to success and basic flow of processing URs in Idaho include:

Promptly working the UR after it is reported
Doing your best to identify/fix the problem before making contact with the reporter
Cordially asking for more info if needed, requesting response within 7 days.
- Remind that replies by e-mail are not received; suggest using the Waze app Inbox
Providing a reminder AT LEAST 24 hours before the close of that window
- All requests for more info must allow AT LEAST 7 days to respond. All responses by the reporter restarts the 7 days.
- When unable to provide a reminder within the 7 day window, the Wazer must still receive a 24-hour notice before closing their report.
If no replies are received, close the report as "not identified" and send another message reminding the user that they're welcome to submit the report again if they still have an issue but that we may need more detail from them in order to find and resolve their issue.

Wazers often respond better to personal messages and empathy. Please consider using friendlier comments than the canned messaging available in various scripts/wikis. Show that you understand their frustration and/or apologize for the bad experience where appropriate. This increases the satisfaction that Wazers in Idaho will have.

Please be sure to identify yourself as a volunteer, and if you have management area in Idaho, feel free to use a "signature" if you wish, for example:

--SkyviewGuru
Volunteer, Idaho State Manager

@@ Line 1: / Line 1: @@
 <!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--
 ------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>
+===Communications===
+Our community uses Discord to facilitate communications. [https://discord.gg/xXacqnv {{RootPage2}} has channel] on the Northwest USA Discord server, which is used to chat with local editors and area/state/regional management. If you're a new/existing editor in {{RootPage2}} or even if you're just visiting and want to relay information to local editors you can do so by clicking the link below to jump into the group. All editors are also encouraged to join the national server. Links are below:
-== Update Requests ==
+[https://discord.gg/xXacqnv Join the {{RootPage2}} Channel of the Northwest USA Discord Server]<br>
+[https://discord.gg/WRq3tzV Join the USA National Discord Server]
-An Update Request (UR) is a Map Issue reported by a user from the Waze client app. It is also a layer in the Map Editor. For more information on Update Requests, please refer to the [[Update Requests in Waze Map Editor|Update Request Wiki Page]]
+Discord has a free app available for Windows, MacOS, and Linux computer platforms as well as Android and iOS mobile platforms. You may also use the Discord website to [https://discordapp.com/channels/313435914540154890/313436999011008513 access our Discord channels] if you prefer.
-In Idaho, we have "adopted" at 0/6/7 system for response to Update Requests. 0/6/7 is the short way of explaining the following.
+===Visibility===
+'''While editing in {{RootPage2}}, editors must not use Invisible mode.''' Editors are not required to socialize in chat, but are expected to respond to inquiries about their edits if questions about them arise. If you decide to minimize chat, please consider using the [http://wiki.waze.com/wiki/Scripts/WME_Chat_addon WME Chat Addon] so that you can be "pinged" if somebody needs to talk to you.
+===Coaching===
+All editors of {{RootPage2}} need to be willing and able to accept coaching from any area/state/regional management, as well as peers and outside area management, and then use that coaching to make appropriate corrections. We maintain a strong community by being on the same page with how the mapping should be done. The goal in coaching is to help you improve the experience that Wazers will have when using the app. It is not meant to criticize the way you have gone about a solution, but rather refine it to exceed the needs of our Wazers and to meet the standards set for the map.
-=== Day 0 ===
+You may receive inquiries by Personal Message (PM) if you aren't able to be reached in WME Chat or Discord. Please respond ASAP to any messages you receive (the expectation is a response within 48 hours under most circumstances).
-At the earliest possible convenience for an editor, an editor should investigate the available resources shown from the data provided by Waze and other legal sources.(GPS Trace, Route, Location and GIS Maps) to determine if a valid error occurred and attempt to Solve the report if possible. If an error is not obvious, then the editor should comment on the UR seeking such information. The information in the original comment should contain:
-*Approximate Location
+===Disciplinary Action===
-*7 Day Comment Period
+Editors that do not respond to inquiries about their edits, choose not to make appropriate corrections after being coached, and/or cause deliberate damage to the map, etc., may, depending on severity, receive consequences including but not limited to: mandatory formal mentoring, temporary suspension of editing privileges, and permanent loss of editing privileges.
-*Reply using Waze Inbox, not email.
-*Editor Name (Optional)
-*Editor Rank (Optional)
-Example:
+=== Update Requests ===
+We are the face of Waze to the majority of Wazers and we want to be sure our Wazers are getting the best experience they can. Sometimes things don't go well while Wazing and Update Requests (URs) are submitted to bring those issues to our attention.
-"Hello! Thanks for your report from X St and Y Ave. Unfortunately, no other details came through with your report. Please let us know any details that will help us identify and resolve the problem and we'll be glad to get this resolved for you!
+The general guidance to working URs in {{RootPage2}} is the same as the [[Update_Requests_in_Waze_Map_Editor|national guidance]]. We really emphasize that editors answering URs need to have strong people skills and a solid knowledge of Waze map editing so the issue can be successfully and promptly resolved in one report. If the issue becomes something above your ability (e.g. skills and/or rank), or the Wazer becomes unprofessional, please bring it to the attention of an [[{{RootPage2}}#Area Managers|area or state manager]].
-Please reply within 7 days using the Inbox within the Waze app (do not reply to the e-mail itself). Thanks! "
+The keys to success and basic flow of processing URs in {{RootPage2}} include:
+* Promptly working the UR after it is reported
+* Doing your best to identify/fix the problem before making contact with the reporter
+* Cordially asking for more info if needed, requesting response within 7 days.
+** Remind that replies by e-mail are not received; suggest using the Waze app Inbox
+* Providing a reminder AT LEAST 24 hours before the close of that window
+** All requests for more info must allow AT LEAST 7 days to respond. All responses by the reporter restarts the 7 days.
+** When unable to provide a reminder within the 7 day window, the Wazer must still receive a 24-hour notice before closing their report.
+* If no replies are received, close the report as "not identified" and send another message reminding the user that they're welcome to submit the report again if they still have an issue but that we may need more detail from them in order to find and resolve their issue.
--EditorName
+Wazers often respond better to personal messages and empathy. Please consider using friendlier comments than the canned messaging available in various scripts/wikis. Show that you understand their frustration and/or apologize for the bad experience where appropriate. This increases the satisfaction that Wazers in {{RootPage2}} will have.
-Volunteer Map Editor
+Please be sure to identify yourself as a volunteer, and if you have management area in {{RootPage2}}, feel free to use a "signature" if you wish, for example:
+''--SkyviewGuru''<br>
+''Volunteer, {{RootPage2}} State Manager''
-=== Day 6 ===
-Once the sixth day has came since the original comment, and there is no other comment from the reporter, the editor should politely remind the reporter that they only have 24 hours to comment on the report before it will be closed.
-"Hello! Sorry to bother you again. I have not received a response regarding your report. In order to investigate your report, I need further information. Please respond within 24 hours or your report will be closed as "not identified". Thanks! "
--EditorName
-Volunteer Map Editor
-=== Day 7 ===
-URs may be closed due to lack of reporter response, provided at least 24 hours have elapsed since the Day 6 Reminder Message (Day 7 since original comment)
-"As we were not provided the requested information, we are unable to continue investigating this issue and are closing the report. Feel free to report map issues as you travel, but please understand that most issues require additional detail to investigate and resolve. Thanks!"
-A UR which is closed due to inactivity should be closed as "Not Identified".
 <!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----

Search