5-A-Day

Differences between revisions 60 and 98 (spanning 38 versions)
⇤ ← Revision 60 as of 2008-06-16 17:51:52 →
Size: 9319
Editor: echelon
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:
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| <<Include(BugSquad/Header)>>

||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||
Line 5: Line 7:
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. 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.
Line 7: Line 9:
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.		 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 14: Line 27:
 * 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`.
 * '''Check out the section on [:5-A-Day#Log:Automatic Reporting] to see how to participate.'''
 * See how you are doing over here: http://daniel.holba.ch/5-a-day-stats/
 * Print out the 5-a-day Playbook to hand out to participants. attachment:5-a-day.pdf		 == Automatic Reporting ==
Line 20: 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 22: 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 25: 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 28: Line 47:
You can review the bugs you've reported at https://bugs.launchpad.net/people/+me/+reportedbugs .
 		 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 34: Line 53:
 * 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 and are still in a New status can be found at http://people.ubuntu.com/~brian/reports/yesterday/
 * 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
   1. If the report has not had any recent activity, it would be helpful to know if the issue reported still exists or not.
   1. 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:
  || Product || Debugging Instructions||
  ||[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 ||		  * 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
Line 48: Line 56:
 * [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])
 * Check out [:QATeam/BugDayFocus:bugs that were not taken care of during Bug Days].
  * [[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]].
Line 54: Line 63:
 * Reviewing patches: '''http://daniel.holba.ch/really-fix-it/'''  * Reviewing the list of patches on Ubuntu bugs
Line 57: Line 66:
  1. Transform the patch into a [:PackagingGuide/Recipes/Debdiff:debdiff] if necessary.   1. Transform the patch into a [[PackagingGuide/Recipes/Debdiff|debdiff]] if necessary.
Line 59: Line 68:
  1. Add it to the [:SponsorshipProcess:sponsoring queue] or upload it yourself.   1. Add it to the [[SponsorshipProcess|sponsoring queue]] or upload it yourself.
Line 62: Line 71:

= 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 - every day! https://wiki.ubuntu.com/5-A-Day
}}}

[[Anchor(Log)]]
= Automatic Reporting =
This step is optional, but will automatically report your [https://code.launchpad.net/~5-a-day/5-a-day-data/main bug numbers] and update your signature file if you like it to.

== Reporting to the 5-A-Day log ==

 1. Add the following line to your `/etc/apt/sources.list`:
  * For Hardy: {{{
deb http://ppa.launchpad.net/5-a-day/ubuntu hardy main}}}
  * For Gutsy: {{{
deb http://ppa.launchpad.net/5-a-day/ubuntu gutsy main
deb http://ppa.launchpad.net/bughelper-dev/ubuntu gutsy main
deb http://ppa.launchpad.net/bzr/ubuntu gutsy main}}}[[BR]]You can also use the "Software Sources" Editor: [[BR]] attachment:apt-sources.png
 1. Install the `five-a-day` package: {{{
sudo apt-get update; sudo apt-get install five-a-day}}}
 1. '''Join the [https://launchpad.net/~5-a-day/+join 5-a-day] team on Launchpad.''' (Else 5-A-Day is not going to work.)
 1. Tell `5-a-day` which Launchpad user you have: {{{
echo <Your Launchpad ID> > ~/.5-a-day}}} - please note: 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). [[BR]] e.g. The user `dholbach` would type in: {{{
echo dholbach > ~/.5-a-day}}}
 1. If you haven't done so, add your [https://launchpad.net/people/+me/+editsshkeys SSH key to Launchpad]. If you don't have an SSH key, follow the instructions on [:LaunchpadStepByStepInstructions:this page] to generate one.
 1. Run `5-a-day --add`: {{{
5-a-day --add <bugnumbers>}}} For example: {{{5-a-day --add 123456 123457 123458 123459 123460
}}}
 1. Done. :-) ''(Please note: you can also use the 5-A-Day applet - see below.)''

== Update ~/.signature ==

 1. Follow the steps above.
 1. Run: {{{
update-signature}}} and it will automatically update your signature. (It will also preserve an old `~/.signature` file if it finds it.)
 1. Make sure your mail client picks up the shiny new `~/.signature`.

== Generate a blog "signature" ==

 1. Follow the steps above.
 1. Run: {{{
update-signature --html}}} and it will spit out HTML code you can add to your blog entry.

== 5-A-Day Applet ==

 1. Add the PPAs as mentioned above.
 1. Run {{{
sudo apt-get update; sudo apt-get install five-a-day-applet}}}
 1. Right-click on your GNOME panel, add the 5-A-Day applet to it.
 1. Work on a bug as mentioned above.
 1. Drag the Firefox / Epiphany tab on the applet, done.

Check out this [http://launchpadlibrarian.net/12228307/5-a-day-applet_1.mpeg video] to see how it works.

[[Anchor(Team)]]
== Contribute within your LoCo Team ==

We explicitly want LoCo teams to be in this. Sure the `motu` team would do great, the `bugsquad` too but that would be cheating, wouldn't it? :-)

 1. Run {{{
echo <your LoCo Team's LP ID> > ~/.5-a-day-team}}} for example: {{{
echo ubuntu-berlin > ~/.5-a-day-team}}} ('''Note:''' You need to member of that team.)
 1. If you're unsure what your team's Launchpad ID is,
  1. check out [https://edge.launchpad.net/people/+me/+participation your Launchpad team participation page].
  1. find the '''LoCo''' team you're member of [[BR]] attachment:identify-loco.png
  1. click on it
  1. check out the URL in the URL bar of your browser [[BR]] attachment:loco-id.png

[[Anchor(Tag)]]
== Tagging 5-A-Day Bugs ==

This new feature is particularly useful during events like [:UbuntuHugDay:Hug Days] or [:RunningBugJam:Bug Jams].

 1. Make sure you have `five-a-day` version `>= 0.26` installed.
 1. Run {{{
5-a-day --add-tag tag-you-are-going-to-use
}}}
 1. Add 5-A-Day bugs as usual.
 1. ...
 1. Run {{{
5-a-day --remove-tag tag-you-are-going-to-use
}}} to stop using the particular tag.		  * 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]]
   1. If the report has not had any recent activity, it would be helpful to know if the issue reported still exists or not.
   1. 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:
  || Product || Debugging Instructions||
  ||[[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)