Stephenr1966 (talk | contribs) m (*/Community/Main*/reformatted to fix ToC) |
Roadtechie (talk | contribs) No edit summary |
||
| (7 intermediate revisions by 6 users not shown) | |||
| 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><!-- | <!-- 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 ------> | ------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> | ||
=== Waze | === Waze Mid-Atlantic Discord Server === | ||
We | We have created a channel on the Mid-Atlantic Server just for West Virginia. This channel 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 Mid-Atlantic Discord Server. You can join easily with [https://goo.gl/Z165wt this link]. | |||
=== West Virginia User Report Management === | === West Virginia User Report Management === | ||
====Response Timeline==== | ====Response Timeline==== | ||
(NOTE: all day values are relative to the date the FIRST editor response is sent to the reporter) | ''(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 ---- | <!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ---- | ||
Revision as of 19:24, 10 September 2017
Waze Mid-Atlantic Discord Server
We have created a channel on the Mid-Atlantic Server just for West Virginia. This channel 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 Mid-Atlantic Discord Server. 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.