TaskTemplate

Differences between revisions 33 and 44 (spanning 11 versions)
Revision 33 as of 2008-08-06 16:32:42
Size: 2202
Editor: localhost
Comment: converted to 1.6 markup
Revision 44 as of 2010-06-29 12:52:52
Size: 4567
Editor: pc-231-206-161-190
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Deprecated, please see [[UbuntuBugDay/Organizing]] <<Include(BugSquad/Header)>>
Line 3: Line 3:
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||
Line 4: Line 5:
---- This week's Hug Day will focus on '''<<<TARGET>>>'''!
Line 6: Line 7:
After you have triaged or fixed a bug put your '''Launchpad Id''' 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.
Line 7: Line 9:
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''<<BR>><<TableOfContents>>|| == Tools ==
Line 9: Line 11:
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.
For doing your work easier during the hug days remember to use the [[https://wiki.ubuntu.com/UbuntuBugDay/Tools|hugday-tools]].
Line 15: Line 15:
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####
To sign up for 5-A-Day participation, please add your Launchpad ID to the Participants column. (This is not the email address you used for signing up for LP, but the last part of the URL that https://launchpad.net/people/+me redirects you to (everything behind the ~ sign)):
Line 21: Line 17:
More information about [[https://wiki.ubuntu.com/5-A-Day#Tag|tags here]].    1. Click on https://launchpad.net/people/+me
   2. Look at the URL bar, everything behind the ~ sign is your Launchpad ID.

Also sign up here: https://launchpad.net/~5-a-day-participants/+join

== Upstream project ==
## If the project is an upstream one please add the link to that particular bug tracker and home page of the project here.

The '''<<<TARGET>>>''' upstream Bug Tracker and Home page are:

 * Bug Tracker
 * Home Page

Please check for already bugs filed in the upstream Bug tracker before sending our reports.

== 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''' ||
Line 24: Line 46:
== ### 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
Line 25: Line 51:
## 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.
||<rowbgcolor="#FFEBBB"> '''Bug''' || '''Subject''' || '''Triager''' ||
Line 29: Line 53:
## Here be goals for these bugs
== ### Confirmed Bugs ==
Line 31: Line 56:
 * Option 1 '''or'''
 * Option 2 '''or'''
 * Option 3

 * 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''' ||


== ### Bugs with Patches ==
'''To mark it off the list you should:'''
 
  * Verify if the patch really is a patch.
  * If it is not, unmark it as a patch.
  * If it is, get the bug triaged and looked by the maintainer.

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

== ### Bugs to be forwarded Upstream ==
'''To mark it off the list you should:'''

  * Verify the bug is still not fixed
  * Search in the [[https://wiki.ubuntu.com/Bugs/Upstream/|Upstream bug tracker]] for a similar report, if there is no one, open a new report and add a [[https://wiki.ubuntu.com/Bugs/Watches|Bug watch]] to the downstream report.
  * Set status to triaged [[UbuntuBugControl]]

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

== ### Private bugs to be reviewed ==
'''To mark it off the list you should:'''

   * [[UbuntuBugControl]] verify that the report does not contains sensitive data.
   * If it does not, Change the Visibility status to Public.
   * If the report does contains sensitive data, add a comment explaining on why it will keep on the Private status.
Line 39: Line 93:
## example - http://people.ubuntu.com/~brian/complete-graphs/compiz/plots/compiz-1day-new.png
Line 41: Line 94:
## example - attachment:compiz-1day-new.png ## 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 43: Line 105:
CategoryTemplate CategoryBugSquad

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

After you have triaged or fixed a bug put your Launchpad Id 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

To sign up for 5-A-Day participation, please add your Launchpad ID to the Participants column. (This is not the email address you used for signing up for LP, but the last part of the URL that https://launchpad.net/people/+me redirects you to (everything behind the ~ sign)):

  1. Click on https://launchpad.net/people/+me

  2. Look at the URL bar, everything behind the ~ sign is your Launchpad ID.

Also sign up here: https://launchpad.net/~5-a-day-participants/+join

Upstream project

The <<<TARGET>>> upstream Bug Tracker and Home page are:

  • Bug Tracker
  • Home Page

Please check for already bugs filed in the upstream Bug tracker before sending our reports.

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

### Bugs with Patches

To mark it off the list you should:

  • Verify if the patch really is a patch.
  • If it is not, unmark it as a patch.
  • If it is, get the bug triaged and looked by the maintainer.

Bug

Subject

Triager

### Bugs to be forwarded Upstream

To mark it off the list you should:

Bug

Subject

Triager

### Private bugs to be reviewed

To mark it off the list you should:

  • UbuntuBugControl verify that the report does not contains sensitive data.

  • If it does not, Change the Visibility status to Public.
  • If the report does contains sensitive data, add a comment explaining on why it will keep on the Private status.

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)