USA/Great Lakes/Closures/Main

From Wazeopedia

< USA‎ | Great Lakes

Revision as of 19:09, 29 June 2016 by SkiDooGuy (talk | contribs) (SkiDooGuy moved page USA/Great Lakes/Test/Closures/Main to USA/Great Lakes/Closures/Main: Moving to main page. No need for Test page)


Replace this template message with specific information unique to the state. If the information is more than a screen full, consider moving it to a full subpage. Minimally the following link is required to reach the full subpage from the main page. Exclude this link if all the relevant information is already displayed in this section.

See USA/Great Lakes/Closures for guidance in Great Lakes that may not be universal to all other states and territories.

Update Requests

2015-06-06: The Great Lakes Region has standardized on a UR response system after extended discussion in the forum.

Overview

NOTE: all day values are relative to the date the FIRST editor response is sent to the reporter.

Response Timeline

  • Day 0: the first editor who is able to respond to UR should attempt to resolve the UR. If they are successful, they should comment as such in the UR and mark it closed. 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 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

Shared Ownership:

  • All editors are considered to have equal ownership of and responsibility for all URs in the Great Lakes Region.
  • All editors, regardless if they have worked the UR previously, may send any of the responses describe above, provided they adhere the minimum time spacing guidance between responses.
  • All editors are explicitly encouraged to attempt resolving 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
  • While strongly recommended, it is not required to send the followup message.

Process Chart

GLR - UR Process 20150606.png