Changes between Version 12 and Version 13 of KiT×2013


Ignore:
Timestamp:
Nov 11, 2012, 8:05:55 PM (9 years ago)
Author:
Daniel Kahn Gillmor
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • KiT×2013

    v12 v13  
    11[[PageOutline]]
    2 = A KibiTicket by 2013 =
     2= A HemiKibiTicket by 2013 =
    33
    4 At the November 3, 2012 support-team meeting, Ross set us an ambitious cleanup goal for this ticketing system.  Reduce the number of [/query?status=new&status=assigned open (new, assigned) tickets] to below 1024 (one [WikiPedia:"Binary Prefix" Kibi]Ticket) by the beginning of the upcoming calendar year.
     4At the November 3, 2012 support-team meeting, Ross set us an ambitious cleanup goal for this ticketing system.  Reduce the number of [/query?status=new&status=assigned open (new, assigned) tickets] to below 1024 (one [WikiPedia:"Binary Prefix" Kibi]Ticket) by the beginning of the upcoming calendar year.  That goal was met by November 10th.  That kind of success means we have to move the goalposts :P so we're now aiming for 512 open tickets instead!
    55
    6 Our shorthand for "A KibiTicket by 2013" is '''KiT×2013'''.
     6Our shorthand for "A HemiKibiTicket by 2013" is '''KiT×2013'''.
    77
    88== Status and Timeline ==
    99
    10 We started with about 1850 tickets in a new/assigned state on November 3rd.  With 59 days until the calendar year ends, this requires us to close on average  14 tickets per day -- all while continuing to deal promptly and effectively with incoming tickets.
    11 
     10We started with about 1850 tickets in a new/assigned state on November 3rd.  By November 11th we were at 971.
    1211[[Image(ticket:6459:tickets.svg)]]
    1312([ticket:6459 graph details])
     
    6867As you're triaging a ticket, go ahead and scan the keywords field.  Try to normalize the keywords into a space-separated list of the relevant terms.  Take a quick search for other similar tickets to see what their keywords look like if you're not sure what's plausible.  This isn't terribly important, and your time will be better spent closing other tickets.  Once you've closed a dozen or two, you'll have a pretty decent sense of what sort of keywords are reasonable.
    6968
    70 ==== Uncertain Outcomes ====
     69=== Uncertain Outcomes ===
    7170
    72 For some tickets, you may find that a resolution was likely found.  However, you cannot quite tell.  In these cases, simply add the keyword/tag 'needs-review'.  This way we'll have a collection of easily identifiable tickets for reviewing later.
    73 
     71For some tickets, you may find that a resolution was likely found.  However, you cannot quite tell.  In these cases, simply add the keyword/tag [tag:needs-review needs-review].  This way we'll have a collection of easily identifiable tickets for reviewing later.
    7472
    7573=== Choose a Resolution ===