5-A-Day
|
Size: 5841
Comment:
|
Size: 7196
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 35: | Line 35: |
| == Anybody who reports bugs == | == Getting Started == |
| Line 37: | Line 37: |
| Did you report a bug on a previous release of Ubuntu? | 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 40: | Line 40: |
| * Could it use a better summary or a test case? | * Could it use a better summary or a test case? |
| Line 43: | Line 43: |
| 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 51: | 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 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 || |
|
| Line 64: | Line 53: |
| * [[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. |
|
| Line 65: | Line 56: |
| Line 77: | Line 67: |
| * 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 || |
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 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!
...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:
- 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.
Check out the section on 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. 5-a-day.pdf
Join the Launchpad team
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 is 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:
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 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/
Reviewing bugs marked for expiration - https://bugs.launchpad.net/ubuntu/+expirable-bugs
Bugs that need forwarding to the Upstream bugtrackers (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.
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.)
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.
You're a developer?
You might be interested in the following lists of bugs:
Reviewing patches: http://daniel.holba.ch/harvest/
- Make sure the bug is still relevant.
- Assign it to you.
Transform the patch into a debdiff if necessary.
- Make sure it builds and fixes the bug.
Add it to the 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 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
- If the report has not had any recent activity, it would be helpful to know if the issue reported still exists or not.
- 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
5-A-Day (last edited 2016-10-27 07:46:00 by dholbach)