5-A-Day

Differences between revisions 80 and 95 (spanning 15 versions)
⇤ ← Revision 80 as of 2008-09-20 07:51:00 →
Size: 7195
Editor: 79-72-68-121
Comment: fix title
← Revision 95 as of 2010-10-10 22:09:21 → ⇥
Size: 7402
Editor: c-67-191-203-118
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
||<tablestyle="font-size: 0.85em; border: none; width: 100%; background-color: #f1f1ed; font-weight: bold;"> [[5-A-Day]] || [[5-A-Day/Reporting|Automatic Reporting]] ||
Line 10: 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 28: 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 29: 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/Reporting|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]]
 * Join the [[https://launchpad.net/~5-a-day|Launchpad team]]		 == Automatic Reporting ==

 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://qa.ubuntu.com/reports/five-a-day/ to see how you're doing.

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 41: 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 50: 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 53: 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 59: Line 63:
 * Reviewing patches: '''http://daniel.holba.ch/harvest/'''  * Reviewing patches: '''http://harvest.ubuntu.com/opportunities/'''

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://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:

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