Puerto Rico/Closures/Main: Difference between revisions View history

 
(5 intermediate revisions by 2 users not shown)
Line 7: Line 7:
==Update Requests==
==Update Requests==


[[File:Request pin open-low.png]] [[File:Request pin open-med.png]] [[File:Request pin open-high.png]] [[File:Request pin open-low.png]] [[File:Request pin open-med.png]] [[File:Request pin open-high.png]] [[File:Request pin open-low.png]] [[File:Request pin open-med.png]] [[File:Request pin open-high.png]] [[File:Request pin open-low.png]] [[File:Request pin open-med.png]] [[File:Request pin open-high.png]] [[File:Request pin open-low.png]] [[File:Request pin open-med.png]] [[File:Request pin open-high.png]]
[[File:Request pin open-low.png]] [[File:Request pin open-med.png]] [[File:Request pin open-high.png]] [[File:Request pin open-low.png]] [[File:Request pin open-med.png]] [[File:Request pin open-high.png]] [[File:Request pin open-low.png]] [[File:Request pin open-med.png]] [[File:Request pin open-high.png]] [[File:Request pin open-low.png]] [[File:Request pin open-med.png]] [[File:Request pin open-high.png]] [[File:Request pin open-low.png]] [[File:Request pin open-med.png]]


04-04-2016: Puerto Rico has standardized on a UR response system after extended discussion in the Google Hang Outs.
04-04-2016: Puerto Rico has standardized on a UR response system after extended discussion in the Google Hang Outs.
Line 15: Line 15:
'''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.


<big>'''Response Timeline'''</big>
<big>'''Response Timeline:'''</big>


* Day 0: The first editor who is able to respond to UR should attempt to resolve the UR. If successfully found a resolution, the UR should be marked Solved along with a message. Optionally, the editor can wait a few days to follow up in the report. If more information from the reporter is required to make progress towards a resolution, a response should be sent to the reporter containing the information needed for resolution.
* '''Day 0:''' The first editor who is able to respond to UR should attempt to resolve the UR. If successfully found a resolution, the UR should be marked Solved along with a message. Optionally, the editor can wait a few days to follow up in the report. If more information from the reporter is required to make progress towards a resolution, a response should be sent to the reporter containing the information needed for resolution.


* '''Day 4:''' Reminder message sent if no response from the reporter is recieved since day 0.


* Day 5+: URs that has no response shall be closed as Not Identified due to lack of reporter response at any time.
* '''Day 5+:''' URs that has no response shall be closed as Not Identified due to lack of reporter response at any time.




Line 27: Line 28:
* All editors are considered to have equal ownership of and responsibility.
* All editors are considered to have equal ownership of and responsibility.


 
* All editors, regardless if they have worked the UR previously, may send any of the responses described above, provided they adhere the minimum time spacing guidance between responses.
* 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.
.
* 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
 


<big>'''Notes:'''</big>
<big>'''Notes:'''</big>

Latest revision as of 03:02, 11 March 2018


See Puerto Rico/Closures for guidance in Puerto Rico that may not be universal to all other states and territories.


Update Requests

04-04-2016: Puerto Rico has standardized on a UR response system after extended discussion in the Google Hang Outs.

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 successfully found a resolution, the UR should be marked Solved along with a message. Optionally, the editor can wait a few days to follow up in the report. If more information from the reporter is required to make progress towards a resolution, a response should be sent to the reporter containing the information needed for resolution.
  • Day 4: Reminder message sent if no response from the reporter is recieved since day 0.
  • Day 5+: URs that has no response shall be closed as Not Identified due to lack of reporter response at any time.


Shared Ownership:

  • All editors are considered to have equal ownership of and responsibility.
  • All editors, regardless if they have worked the UR previously, may send any of the responses described 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.
  • It is NOT required to send a reminder in the report before closing it due to the lack of response.
  • When the reporter responds back, and more information is needed for a resolution, 5 days is the minimum time before closing it due to the lack of response.