Machete808 (talk | contribs) m (Copying text of wiki page for coparison with the "Idaho/AM/Editor/Area2" page) |
Machete808 (talk | contribs) m (Copying text of wiki page for coparison with the "Idaho/Community/Main" page) |
||
| 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=== | |||
In {{RootPage2}}, we use Google Hangouts (GHO) and Slack to facilitate communications and community. | |||
==== Google Hangout (Chat) ==== | |||
{{RootPage2}} has a Google Hangout (GHO) for the state, 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. | |||
[http://hangouts.google.com/group/XAYmpH0eQCTEb62f2 Join {{RootPage2}} GHO] | |||
There is also a Northwest Region GHO, which has a similar mission but serves Alaska, Idaho, Montana, Oregon, Washington, and Wyoming so there are many more editors in there who can assist. Most of the northwest's State Managers have area management over {{RootPage2}}, so you can more quickly get help by joining this channel. | |||
[http://hangouts.google.com/group/LuufQQzA4plHLCFH3 Join Northwest Region GHO] | |||
Google Hangouts is a free app available on Android and iOS devices. You also can use an extension in the Chrome Web Browser to access this chat. Go to [http://www.google.com/+/learnmore/hangouts/ google.com/+/learnmore/hangouts] for more information. | |||
==== Slack ==== | |||
We also have a Slack channel for the northwest region in the Waze USA team that you are [http://docs.google.com/forms/d/e/1FAIpQLScPdOwbVtSIbjjGsPoxMNR8qlU0MFJO3cvOkhm-TIHsNgiWeQ/viewform welcome to join]. | |||
===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. | |||
You may receive inquiries by Personal Message (PM) if you aren't able to be reached in WME Chat, GHO, or Slack. 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 {{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]]. | |||
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. | |||
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. | |||
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'' | |||
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ---- | |||
------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ||
-- | ---- This page is only transcluded into (displayed on) the main page for this state. | ||
-- following | ---- It directly follows the common guidelines applicable to all states. When this | ||
- | ---- page is present (even if blanked), it displaces any optional code that might be | ||
-- | ---- in that section. | ||
---- If the original optional code from the main page for this section is still | |||
---- desired, it can be restored by adding the following code to the first line | |||
---- between the "DO NOT MODIFY" lines on this page: | |||
---- {{:USA/CommonState/Community|optional}} | |||
---- | |||
------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ||
{{ | ---- If there will be a full page for this section, use code similar to the wording | ||
---- below to provide a hyperlink to that page. When creating the full page, use the | |||
---- link on the talk page to ensure the preload data is provided to help with | |||
---- formatting the page. Don't just use the red link from this section once it is | |||
---- saved. | |||
---- | |||
See [[{{BasePage2}}/Community]] for guidance in {{RootPage2}} that may not be universal to all other states. | |||
---- | |||
------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ||
---- This section has three possible purposes: | |||
---- 1. It is only providing a hyperlink to the full page for this section. | |||
---- | ---- 2. It is only providing some unique guidance for this state that differs from | ||
---- | ---- other states. | ||
---- 3. It is intentionally wiping out the general optional content for this section | |||
---- | ---- for this state. | ||
---- | ------------------------------------------------------------------------------------> | ||
------------------------------------------------------------------------------------ | |||
Revision as of 13:49, 16 February 2017
Communications
In PesachZ, we use Google Hangouts (GHO) and Slack to facilitate communications and community.
Google Hangout (Chat)
PesachZ has a Google Hangout (GHO) for the state, which is used to chat with local editors and area/state/regional management. If you're a new/existing editor in PesachZ 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.
There is also a Northwest Region GHO, which has a similar mission but serves Alaska, Idaho, Montana, Oregon, Washington, and Wyoming so there are many more editors in there who can assist. Most of the northwest's State Managers have area management over PesachZ, so you can more quickly get help by joining this channel.
Google Hangouts is a free app available on Android and iOS devices. You also can use an extension in the Chrome Web Browser to access this chat. Go to google.com/+/learnmore/hangouts for more information.
Slack
We also have a Slack channel for the northwest region in the Waze USA team that you are welcome to join.
Visibility
While editing in PesachZ, 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 PesachZ 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, GHO, or Slack. 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 PesachZ 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 PesachZ 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 PesachZ will have.
Please be sure to identify yourself as a volunteer, and if you have management area in PesachZ, feel free to use a "signature" if you wish, for example:
--SkyviewGuru
Volunteer, PesachZ State Manager