5-A-Day

Differences between revisions 82 and 98 (spanning 16 versions)
⇤ ← Revision 82 as of 2009-02-18 17:31:48 →
Size: 7150
Editor: i59F729A8
Comment:
← Revision 98 as of 2016-10-27 07:46:00 → ⇥
Size: 7906
Editor: dholbach
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
So the idea is simple - let's get every Ubuntu enthusiasts working on 5 bugs a day - everyone can take part, no matter whether a developer or not. Lets work together and make some ''real progress''! So the idea is simple - let's get every Ubuntu enthusiast working on 5 bugs a day - everyone can take part, no matter whether you are a developer or not. Let's work together and make some ''real progress''!
Line 24: Line 24:
 * If you know your way around Ubuntu quite well, you can help assign bugs to the right package.   * If you know your way around Ubuntu quite well, you can help assign bugs to the right package.
Line 29: Line 29:
## * See how you are doing over here: http://daniel.holba.ch/5-a-day-stats/ ## * See how you are doing over here: http://qa.ubuntu.com/reports/five-a-day/
Line 34: Line 34:
 2. Done!   * your e-mail address must not be hidden from other Launchpad users for you to receive credit
 2. Done! Check out http://reports.qa.ubuntu.com/reports/five-a-day/ to see how you're doing.
Line 36: Line 37:
If you plan to host a Bug Jam, or participate in the Global Bug Jam or any other event, add your event to the Bug Jam section of [[Bugs/Events]]. If you plan to host a '''[[RunningBugJam|Bug Jam]]''', or participate in the '''[[GlobalBugJam|Global Bug Jam]]''', add your event to the Bug Jam section of '''[[Bugs/Events]]'''.
Line 44: Line 45:
 * Do you know if the bug is still occurs in the development release?  * Do you know if the bug still occurs in the development release?
Line 46: Line 47:
You can review the bugs you've reported at https://bugs.launchpad.net/people/+me/+reportedbugs . You should be comfortable with the bugs you've reported in the past; pay particular attention to how more experienced triagers handled your bugs.  
 		 You can review the bugs you've reported at https://bugs.launchpad.net/people/+me/+reportedbugs . You should be comfortable with the bugs you've reported in the past; pay particular attention to how more experienced triagers handled your bugs.
Line 53: Line 54:
 * Bug reports that were submitted yesterday and are still in a New status can be found at http://people.ubuntu.com/~brian/reports/yesterday/  * Bug reports that were submitted yesterday with a high bug gravity - http://qa.ubuntu.com/reports/bugnumbers/yesterday.html
Line 56: Line 57:
 * [[http://people.ubuntu.com/~brian/reports/database/unlinked-bugwatch.html|Unlinked upstream bugs]] - Sometimes people add a link to an upstream bug tracker in the comments of a bug but don't bother creating an upstream task. This is a list of possible targets that can be linked. (Lots of low hanging fruit in this list, but also a bunch of dupes and ones inappropriate to be linked.)  
 * [[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=NEW&field.importance%3Alist=UNKNOWN&field.importance%3Alist=UNDECIDED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&field.has_no_package=on|Bugs without a package]] - Sometimes users do not know which package a bug is in, so they leave it blank - assigning a package to a bug will help move it along to the next step.
 * Check out [[QATeam/BugDayFocus|bugs that were not taken care of during Bug Days]].		  * [[ http://qa.ubuntu.com/reports/launchpad-database/unlinked-bugwatch.html | Unlinked upstream bugs ]] - Sometimes people add a link to an upstream bug tracker in the comments of a bug but don't bother creating an upstream task. This is a list of possible targets that can be linked. (Lots of low hanging fruit in this list, but also a bunch of dupes and ones inappropriate to be linked.)
 * [[https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=NEW&field.importance%3Alist=UNKNOWN&field.importance%3Alist=UNDECIDED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&field.has_no_package=on|Bugs without a package]] - Sometimes users do not know which package a bug is in, so they leave it blank - assigning a package to a bug will help move it along to the next step.
 * Check out [[http://wiki.ubuntu.com/UbuntuBugDay/Planning#Previous%20Bug%20Days|bugs that were not taken care of during Bug Days]].
Line 62: Line 63:
 * Reviewing patches: '''http://daniel.holba.ch/harvest/'''  * Reviewing the list of patches on Ubuntu bugs
Line 70: Line 71:
 * It is unfortunately the case that new bug reports will sometimes go unanswered. This is actively being addressed, but we can always use additional help. The following are lists of bug reports marked as "New" against older kernels.
  * https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bugs?field.status=NEW
  * https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bugs?field.status=NEW
  * https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bugs?field.status=NEW
  * https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bugs?field.status=NEW		  * It is unfortunately the case that new bug reports will sometimes go unanswered. This is actively being addressed, but we can always use additional help. The following are lists of bug reports in older Ubuntu releases:
  * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.tag=lucid&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.upstream_target=&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on|Kernel bugs tagged under lucid]]

What is 5-A-Day?

Put simply, 5-a-day is a great approach to making our list of bugs more manageable by sharing the workload. This is inspired by the philosophy that eating 5 portions of fruit/vegetables keeps you healthy...well, working on 5 bugs a day keeps Ubuntu healthy.

So the idea is simple - let's get every Ubuntu enthusiast working on 5 bugs a day - everyone can take part, no matter whether you are a developer or not. Let's work together and make some real progress!

...and, to make it fun, we have produced some tools and rankings to make those 5 bugs count. Making Ubuntu better and having fun...we like it. Smile :)

So what kind of things can you do as part of your 5-a-day?

If you have never done any development:

  • If you want to just confirm new bugs, you can do that.
  • Find bugs in upstream bug trackers and link them to the Ubuntu bugs in Launchpad.

If you are a developer:

  • Review patches and get them uploaded.
  • If you've experience with a certain package and want to triage bugs you can do that and forward them upstream if necessary.
  • If you know your way around Ubuntu quite well, you can help assign bugs to the right package.

What you need to do to participate?

  • If you haven't helped out with bugs before you might want to take a look at Bugs/HowToTriage or ask the nice people on #ubuntu-bugs on irc.freenode.net.

  • Print out the 5-a-day Playbook to hand out to participants. 5-a-day.pdf

Automatic Reporting

  1. Join the 5-A-Day Participants team!

    • your e-mail address must not be hidden from other Launchpad users for you to receive credit

  2. Done! Check out http://reports.qa.ubuntu.com/reports/five-a-day/ to see how you're doing.

If you plan to host a Bug Jam, or participate in the Global Bug Jam, add your event to the Bug Jam section of Bugs/Events.

Getting Started

A great way to begin is to look over bugs you have reported before and get them into shape. Have you reported a bug on a previous release of Ubuntu before?

  • Is it the best quality bug report it could be?
  • Could it use a better summary or a test case?
  • Do you know if the bug still occurs in the development release?

You can review the bugs you've reported at https://bugs.launchpad.net/people/+me/+reportedbugs . You should be comfortable with the bugs you've reported in the past; pay particular attention to how more experienced triagers handled your bugs.

Not a developer?

Once you feel comfortable to start triaging, the following lists may be a helpful starting point:

You're a developer?

You might be interested in the following lists of bugs:

  • Reviewing the list of patches on Ubuntu bugs
    1. Make sure the bug is still relevant.
    2. Assign it to you.

    3. Transform the patch into a debdiff if necessary.

    4. Make sure it builds and fixes the bug.

    5. Add it to the sponsoring queue or upload it yourself.

  • The Kernel:
  • It is unfortunately the case that new bug reports will sometimes go unanswered. This is actively being addressed, but we can always use additional help. The following are lists of bug reports in older Ubuntu releases:

    • Kernel bugs tagged under lucid

      1. If the report has not had any recent activity, it would be helpful to know if the issue reported still exists or not.
      2. Additionaly, if the issue still exists, it would be useful to know if it is still present in the actively developed kernel.

* If you're interested on GUI applications you may want to take a look to:

CategoryBugSquad

5-A-Day (last edited 2016-10-27 07:46:00 by dholbach)