Gohelp software rota: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(29 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''THIS IS NOW CLOSED--SWITCHED TO JIRA'''
{|
{|
|+ Current Rota
|+ Current Rota
|-
|-
| Seth
| Seth
| February 6th
| September 3rd
|
|-
|-
| Tony
| Tony
| February 13th
| September 10th
|
|-
|-
| Chris
| Chris
| February 20th
| September 17th
|
|-
|-
| Ben
| Ben
| February 27th
| September 24th
|
|-
|-
| Mary
| Mary
| March 5th
| October 1st
|-
| Heiko
| March 12th
|-
| Seth
| March 19th
|-
| Tony
| March 26th
|-
| Chris
| April 2nd
|-
| Ben
| April 9th
|-
| Mary
| April 16th
| *
| *
|-
|-
| Heiko
| April 22rd
|-
| Seth
| April 30th
|-
| Tony
| May 7th
|-
| Chris
| May 14th
|-
| Ben
| May 21st
|-
| Mary
| May 28th
|-
| Heiko
| June 4th
|}
|}
'''CLOSED'''


=Purpose=
=Purpose=

Latest revision as of 18:01, 7 October 2012

THIS IS NOW CLOSED--SWITCHED TO JIRA

Current Rota
Seth September 3rd
Tony September 10th
Chris September 17th
Ben September 24th
Mary October 1st *

CLOSED

Purpose

To make sure that all email forwarded to the software group from GO Help is answered in a timely manner.

People in rota

Seth, Tony, Chris, Ben, Mary, Heiko

Process

We are going to use a rota where each person will be 'on duty' for 1 week at a time. Any questions hitting the software list during that time should be shepherded by the person on duty.

It is responsibility of the person on duty to make sure that all queries are answered by answering it themselves, forwarding it on to someone else who knows more, or harassing the software list until something happens. The person on duty must also make sure that any answer gets back to either the GO Help list or the originator of the query from GO Help.

At the end of your shift, please send a reminder email to the next person on the list to remind them that it's their turn.

GO help main page