TaskTemplate

Differences between revisions 33 and 37 (spanning 4 versions)
Revision 33 as of 2008-08-06 16:32:42
Size: 2202
Editor: localhost
Comment: converted to 1.6 markup
Revision 37 as of 2009-02-02 14:52:17
Size: 2836
Editor: port-213-160-23-154
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Deprecated, please see [[UbuntuBugDay/Organizing]] <<Include(BugSquad/Header)>>

||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||

This week's Hug Day will focus on '''<<<TARGET>>>'''!

After you have triaged or fixed a bug put your name in the last column and set the row's background to green by adding '''lightgreen''' in the first cell of the column after '''rowbgcolor='''. This will let people know that the bug in that row has been hugged.

== Tools ==

For doing your work easier during the hug days remember to use the [[https://wiki.ubuntu.com/UbuntuBugDay/Tools|hugday-tools]].

== 5-a-day-ing ==
During hug days you can also do [[https://wiki.ubuntu.com/5-A-Day|5-A-Day]] for this one you can do the following in order to tag your work on the hug day:

 * 5-a-day --add-tag hugday-'''<<<DATE>>>'''
 * Add bugs to 5-a-day as usual
 * And when done with hug day run: 5-a-day --remove-tag hugday-'''<<<DATE>>>'''

== Stock Responses ==
## You should add any stock responses that might be useful on this page as well.

For problem specific Stock Responses see: [[Bugs/Responses]]

== ### New Bugs ==
'''To mark it off the list you should:'''
 * Verify the bug is still not fixed
 * Request any needed info, Subscribe, Status to incomplete '''or'''
 * Set status to Confirmed

||<rowbgcolor="#FFEBBB"> '''Bug''' || '''Subject''' || '''Triager''' ||


== ### Incomplete Bugs ==
'''To mark it off the list you should:'''
 * Change the bug's status to "Confirmed" or "Triaged" if the reporter replied with enough information '''or'''
 * Ask a secondary follow up question and subscribe to the bug report

||<rowbgcolor="#FFEBBB"> '''Bug''' || '''Subject''' || '''Triager''' ||


== ### Confirmed Bugs ==
'''To mark it off the list you should:'''

 * Verify the bug is still not fixed
 * Request any needed info, Subscribe, Status to incomplete or
 * Set status to triaged [[UbuntuBugControl]]
 
||<rowbgcolor="#FFEBBB"> '''Bug''' || '''Subject''' || '''Triager''' ||


== Progress ==
## it is nice to have pictures which you can do by directly linking to a graph at http://people.ubuntu.com/~brian/complete-graphs/ just by adding a hyperlink to the graph in the wiki page
## at the end of day I usually save the graph to my local system and then add it as an attachment to the wiki page
## example - attachment:compiz-1day-new.png

{{http://people.ubuntu.com/~brian/complete-graphs/TARGET/plots/TARGET-1day-triaging.png}}

== More Bugs ==
## If you think the list you made might be depleted, or want to let others know how to find similar bugs in the future, add a link to a 'live' version.

This list is just a nibble of the [[https://bugs.launchpad.net/ubuntu/+source/TARGET|bigger picture]].
Line 5: Line 66:


||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''<<BR>><<TableOfContents>>||

Here we have a sampling of bugs to work on for Hug Day. After you have triaged or fixed a bug put your name in the last column and set the row's background to green by adding '''lightgreen''' in the first cell of the column after "background-color:" and before ";". This will let people know that the bug in that row has been hugged.

You might find it more convenient to edit the wiki page using {{{editmoin}}} a command line utility for editing moinmoin wiki pages. It is available as a package in Gutsy and Hardy. More information including an easier way to do this was [[https://lists.ubuntu.com/archives/ubuntu-bugsquad/2007-November/000666.html|mailed]] to the Bug Squad.

== 5-a-day-ing ==

During hug days you can also do [[https://wiki.ubuntu.com/5-A-Day|5-A-Day]] for this one you can do the following in order to tag your work on the hug day:
 
 * 5-a-day --add-tag hugday-####DATE####
 * Add bugs to 5-a-day as usual
 * And when done with hug day run: 5-a-day --remove-tag hugday-####DATE####

More information about [[https://wiki.ubuntu.com/5-A-Day#Tag|tags here]].



## repeat as necessary for each unique type of bug
== XYZ bugs in status or importance ==
Description of what kind of bugs they are and how people can find more.

## Here be goals for these bugs
'''To mark it off the list you should:'''
 * Option 1 '''or'''
 * Option 2 '''or'''
 * Option 3

||<rowbgcolor="#FFEBBB"> '''Bug''' || '''Subject''' || '''Triager''' ||

== Progress ==
## it is nice to have pictures which you can do by directly linking to a graph at http://people.ubuntu.com/~brian/complete-graphs/ just by adding a hyperlink to the graph in the wiki page
## example - http://people.ubuntu.com/~brian/complete-graphs/compiz/plots/compiz-1day-new.png
## at the end of day I usually save the graph to my local system and then add it as an attachment to the wiki page
## example - attachment:compiz-1day-new.png
----
CategoryTemplate
CategoryBugSquad

This week's Hug Day will focus on <<<TARGET>>>!

After you have triaged or fixed a bug put your name in the last column and set the row's background to green by adding lightgreen in the first cell of the column after rowbgcolor=. This will let people know that the bug in that row has been hugged.

Tools

For doing your work easier during the hug days remember to use the hugday-tools.

5-a-day-ing

During hug days you can also do 5-A-Day for this one you can do the following in order to tag your work on the hug day:

  • 5-a-day --add-tag hugday-<<<DATE>>>

  • Add bugs to 5-a-day as usual
  • And when done with hug day run: 5-a-day --remove-tag hugday-<<<DATE>>>

Stock Responses

For problem specific Stock Responses see: Bugs/Responses

### New Bugs

To mark it off the list you should:

  • Verify the bug is still not fixed
  • Request any needed info, Subscribe, Status to incomplete or

  • Set status to Confirmed

Bug

Subject

Triager

### Incomplete Bugs

To mark it off the list you should:

  • Change the bug's status to "Confirmed" or "Triaged" if the reporter replied with enough information or

  • Ask a secondary follow up question and subscribe to the bug report

Bug

Subject

Triager

### Confirmed Bugs

To mark it off the list you should:

  • Verify the bug is still not fixed
  • Request any needed info, Subscribe, Status to incomplete or
  • Set status to triaged UbuntuBugControl

Bug

Subject

Triager

Progress

http://people.ubuntu.com/~brian/complete-graphs/TARGET/plots/TARGET-1day-triaging.png

More Bugs

This list is just a nibble of the bigger picture.


CategoryBugSquad

UbuntuBugDay/TaskTemplate (last edited 2010-06-29 12:52:52 by pc-231-206-161-190)