5-A-Day

Differences between revisions 12 and 98 (spanning 86 versions)
⇤ ← Revision 12 as of 2008-02-08 16:15:14 →
Size: 4496
Editor: i59F70638
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 1: Line 1:
= 5 a Day = <<Include(BugSquad/Header)>>
Line 3: Line 3:
== What is 5-A-Day? == ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||
Line 5: Line 5:
We, that means '''everybody''', will do 5 bugs a day - every day. With only five bugs that everybody looks at every day, we will cover a lot of ground. = What is 5-A-Day? =
Line 7: Line 7:
What you can do? That's up to you, your interests and your abilities.
 * If you're a developer, you can help out reviewing patches and getting them uploaded.		 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. :)

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

If you have never done any development:
Line 10: Line 18:
 * 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.
Line 11: 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 13: Line 26:
== What you need to do to participate? == = 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. [[attachment:5-a-day.pdf]]
## * See how you are doing over here: http://qa.ubuntu.com/reports/five-a-day/
Line 15: Line 31:
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`. == Automatic Reporting ==
Line 17: Line 33:
=== Anybody who reports bugs ===  1. '''[[https://launchpad.net/~5-a-day-participants/+join|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.
Line 19: Line 37:
Did you report a bug on a previous release of Ubuntu? 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]]'''.

== 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?
Line 22: Line 44:
  * Could it use a better summary or a test case?
 * Do you know if the bug is still occurs in the development release?		  * Could it use a better summary or a test case?
 * Do you know if the bug still occurs in the development release?
Line 25: Line 47:
Review bugs you've reported by going to your launchpad page, clicking on the Bugs tab and then click "List reported bugs" in the Actions portlet. Or go to `https://bugs.launchpad.net/~<launchpad-login>/+reportedbugs` where launchpad-login is your launchpad user name.
 
=== Not a developer? ===		 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 29: Line 49:
Once you feel you comfortable to start triaging, the following lists may be a helpful starting point: == Not a developer? ==
Line 31: Line 51:
 * 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		 Once you feel comfortable to start triaging, the following lists may be a helpful starting point:

 * Bugs reported using the "Help -> Report a Problem" contain detailed information regarding the system the bug was reported on therefore they can be easier to triage. They are all tagged 'apport-bug' and you can find ones with a status of "New" at [[https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_contact=&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=apport-bug&field.tags_combinator=ANY&field.has_no_package.used=&search=Search|New apport-bugs]].
 * Bug reports that were submitted yesterday with a high bug gravity - http://qa.ubuntu.com/reports/bugnumbers/yesterday.html
 * Reviewing bugs marked for expiration - https://bugs.launchpad.net/ubuntu/+expirable-bugs
 * [[https://bugs.launchpad.net/ubuntu/+bugs?field.status_upstream=pending_bugwatch&field.status_upstream-empty-marker=1|Bugs that need forwarding to the Upstream bugtrackers]] ([[Bugs/Upstream|Instructions]]) - since a majority of bugs from users are of software that is developed by upstreams it is important that bug linkages are as complete as possible.
 * [[ 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]].

== 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.
  1. Assign it to you.
  1. Transform the patch into a [[PackagingGuide/Recipes/Debdiff|debdiff]] if necessary.
  1. Make sure it builds and fixes the bug.
  1. Add it to the [[SponsorshipProcess|sponsoring queue]] or upload it yourself.
 * The Kernel:
  * http://people.ubuntu.com/~ogasawara/hardy-buglist.html - It's an excellent starting place for the community to get involved and work with the Ubuntu kernel team.
 * 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]]
Line 38: Line 75:
 * If you're interested on GUI applications you may want to take a look to:  * If you're interested on GUI applications you may want to take a look to:
Line 40: Line 77:
  ||[https://bugs.launchpad.net/ubuntu/+source/update-manager/+bugs?field.status=NEW UpdateManager] || DebuggingUpdateManager ||
  ||[https://bugs.launchpad.net/ubuntu/+source/compiz/+bugs?field.status=NEW Compiz] || DebuggingCompiz ||
 * Reviewing bugs marked for expiration - https://bugs.launchpad.net/ubuntu/+expirable-bugs



=== You're a developer? ===
You might be interested in the following lists of bugs:
 * Reviewing patches:
  * https://lists.ubuntu.com/archives/ubuntu-devel/2008-January/024960.html explains how to get a list of bugs that have patches attached that did not make it to the sponsoring queue yet.
  * https://bugs.launchpad.net/ubuntu/+bugs?field.status_upstream=resolved_upstream is a list of bugs that were fixed Upstream or in other Distributions but not fixed in Ubuntu.
  1. Make sure the bug is still relevant.
  1. Assign it to you.
  1. Transform the patch into a [:PackagingGuide/Recipes/Debdiff:debdiff] if necessary.
  1. Make sure it builds and fixes the bug.
  1. Add it to the [:SponsorshipProcess:sponsoring queue] or upload it yourself.
 * The Kernel:
  * http://people.ubuntu.com/~ogasawara/hardy-buglist.html - It's an excellent starting place for the community to get involved and work with the Ubuntu kernel team.

== What you can do to spread the message? ==
 * Add your 5 a day to your blog posts.
  * Either on http://planet.ubuntu.com ([:PlanetUbuntu] if you're part of `ubuntumembers`)
  * or on http://ubuntuweblogs.org/ (follow the [http://ubuntuweblogs.org/submit.html instructions])
 * Add your 5 a day to mailing list posts (in the signature).
{{{
Example:

My 5 today:
 - Bug 123456 (upstream fix included in Ubuntu)
 - Bug 123457 (upstream fix included in Ubuntu)
 - Bug 123458 (explained about debdiff process)
 - Bug 123459 (sponsored the upload)
 - Bug 123460 (guided patch into sponsoring queue)

Do 5 a day - everyday! http://wiki.ubuntu.com/5-A-Day
}}}		   ||[[https://bugs.launchpad.net/ubuntu/+source/update-manager/+bugs?field.status=NEW|UpdateManager]] || DebuggingUpdateManager ||
  ||[[https://bugs.launchpad.net/ubuntu/+source/compiz/+bugs?field.status=NEW|Compiz]] || DebuggingCompiz ||

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)