m (Copying text of wiki page for coparison with the "Oregon/AM/Editor/Area" page) |
m (Copying text of wiki page for coparison with the "West Virginia/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 ------> | |||
=== Waze West Virginia Google Hangout === | |||
---------------------- | We have created a Google Hangout (GHO) just for West Virginia. The GHO is where you can go to interact and chat with fellow editors along with your Area and State Managers. It will give you good insight into the best practices and policies in regard to map editing plus give an easy, convenient way for editors to stay in touch, ask questions (''any questions, we all started at Rank #1 at some point''), request downlocks or review of your work and get Peer-to-Peer Mentoring. | ||
- | If you are editing in West Virginia please join us on the WV Editor Hangout. You can join easily with [https://docs.google.com/forms/d/e/1FAIpQLSdGds9PsBtOEfvtdFGVEgTxHaS7-sQZ2_XiXcvX869MKq5SAA/viewform this link]. | ||
=== West Virginia User Report Management === | |||
====Response Timeline==== | |||
''(NOTE: all day values are relative to the date the FIRST editor response is sent to the reporter)'' | |||
'''Day 0''' | |||
The first editor who is able to respond to a User Report (UR) should attempt to resolve the UR. If they are successful, they should comment as such in the UR and mark it '''"Solved'''". If more information from the reporter is required to make progress towards closure, a response should be sent to the reporter containing the information needed for resolution. | |||
'''Day 4+''' | |||
Polite reminders should be sent to reporters who have not responded to the initial request for information at any time, '''provided at least four full days have elapsed''' since the initial response was sent | |||
'''Day 8+''' | |||
URs may be noted as closed due to lack of reporter response at any time, '''provided at least four full days have elapsed''' since the followup message was sent. These need to be marked as '''"Not Identified"''' and a brief comment sent. | |||
'''Shared Ownership''' | |||
All editors are considered to have equal ownership of and responsibility for all URs in West Virginia. All editors, regardless if they have worked the UR previously, may send any of the responses described above, provided they adhere to the minimum time spacing guidance between responses. All editors are explicitly encouraged to attempt to resolve URs at any point during their lifecycle, even if others happen to be actively working it at the same time. | |||
'''Notes''' | |||
The ideal timeline for UR response is when responses are sent as early as the minimum required time spacing between messages permits; experience has reliably shown that UR response rates are much higher when editors are able to send responses promptly. The 4+ day followup / reminder has shown remarkable improvement in reporter responses everywhere that it has been implemented. | |||
The script [[Scripts#URComments|URComments]] streamlines the process of responding to a UR and provides comments based on the UR type and can be edited prior to sending to fit your needs. | |||
-- | <!---- 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. | ||
---- 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 04:17, 16 February 2017
Waze West Virginia Google Hangout
We have created a Google Hangout (GHO) just for West Virginia. The GHO is where you can go to interact and chat with fellow editors along with your Area and State Managers. It will give you good insight into the best practices and policies in regard to map editing plus give an easy, convenient way for editors to stay in touch, ask questions (any questions, we all started at Rank #1 at some point), request downlocks or review of your work and get Peer-to-Peer Mentoring.
If you are editing in West Virginia please join us on the WV Editor Hangout. You can join easily with this link.
West Virginia User Report Management
Response Timeline
(NOTE: all day values are relative to the date the FIRST editor response is sent to the reporter)
Day 0
The first editor who is able to respond to a User Report (UR) should attempt to resolve the UR. If they are successful, they should comment as such in the UR and mark it "Solved". If more information from the reporter is required to make progress towards closure, a response should be sent to the reporter containing the information needed for resolution.
Day 4+
Polite reminders should be sent to reporters who have not responded to the initial request for information at any time, provided at least four full days have elapsed since the initial response was sent
Day 8+
URs may be noted as closed due to lack of reporter response at any time, provided at least four full days have elapsed since the followup message was sent. These need to be marked as "Not Identified" and a brief comment sent.
Shared Ownership
All editors are considered to have equal ownership of and responsibility for all URs in West Virginia. All editors, regardless if they have worked the UR previously, may send any of the responses described above, provided they adhere to the minimum time spacing guidance between responses. All editors are explicitly encouraged to attempt to resolve URs at any point during their lifecycle, even if others happen to be actively working it at the same time.
Notes
The ideal timeline for UR response is when responses are sent as early as the minimum required time spacing between messages permits; experience has reliably shown that UR response rates are much higher when editors are able to send responses promptly. The 4+ day followup / reminder has shown remarkable improvement in reporter responses everywhere that it has been implemented.
The script URComments streamlines the process of responding to a UR and provides comments based on the UR type and can be edited prior to sending to fit your needs.