5-A-Day

Differences between revisions 67 and 69 (spanning 2 versions)
⇤ ← Revision 67 as of 2008-08-04 04:15:40 →
Size: 8950
Editor: adsl-99-139-209-196
Comment:
← Revision 69 as of 2008-08-06 16:29:58 → ⇥
Size: 8982
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Include(BugSquad/Header)]] <<Include(BugSquad/Header)>>
Line 3: Line 3:
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''<<BR>><<TableOfContents>>||
Line 17: Line 17:
 * 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.'''		  * 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.'''
Line 20: Line 20:
 * 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]		  * 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]]
Line 37: Line 37:
 * 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].  * 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]].
Line 48: Line 48:
  ||[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 ||		   ||[[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 51: Line 51:
 * [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]])
 * Check out [[QATeam/BugDayFocus|bugs that were not taken care of during Bug Days]].
Line 60: Line 60:
  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 62: Line 62:
  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 66: Line 66:
[[Anchor(Log)]] <<Anchor(Log)>>
Line 84: Line 84:
 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. (Else 5-A-Day is not going to work.)  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. (Else 5-A-Day is not going to work.)
Line 88: Line 88:
 1. Done. :-) ''(Please note: you can also use the 5-A-Day applet - see [:5-A-Day#Applet:below].)''  1. Done. :-) ''(Please note: you can also use the 5-A-Day applet - see [[5-A-Day#Applet|below]].)''
Line 91: Line 91:
 * ''If you're part of a LoCo Team, [:5-A-Day#Team:participate] in 5-a-day for your team.''
 * ''If you participate in a [:RunningBugJam:Bug Jam], ask for the name of the tag you agreed to use and [:5-A-Day#Tag:set it in 5-a-day].''		  * ''If you're part of a LoCo Team, [[5-A-Day#Team|participate]] in 5-a-day for your team.''
 * ''If you participate in a [[RunningBugJam|Bug Jam]], ask for the name of the tag you agreed to use and [[5-A-Day#Tag|set it in 5-a-day]].''
Line 107: Line 107:
[[Anchor(Applet)]] <<Anchor(Applet)>>
Line 117: Line 117:
Check out this [http://launchpadlibrarian.net/12228307/5-a-day-applet_1.mpeg video] to see how it works. Check out this [[http://launchpadlibrarian.net/12228307/5-a-day-applet_1.mpeg|video]] to see how it works.
Line 119: Line 119:
[[Anchor(Team)]] <<Anchor(Team)>>
Line 125: Line 125:
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.)		 5-a-day --add-team <your LoCo Team's LP ID>}}} for example: {{{
5-a-day --add-team ubuntu-berlin}}} ('''Note:''' You need to member of that team.)
Line 128: Line 128:
  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. 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}}
Line 131: Line 131:
  1. check out the URL in the URL bar of your browser [[BR]] attachment:loco-id.png   1. check out the URL in the URL bar of your browser <<BR>> {{attachment:loco-id.png}}
Line 133: Line 133:
[[Anchor(Tag)]] <<Anchor(Tag)>>
Line 136: Line 136:
This new feature is particularly useful during events like [:UbuntuHugDay:Hug Days] or [:RunningBugJam:Bug Jams]. This new feature is particularly useful during events like [[UbuntuHugDay|Hug Days]] or [[RunningBugJam|Bug Jams]].

What is 5-A-Day?

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 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.
  • If you want to just confirm new bugs, you can do that.
  • 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?

Anybody who reports bugs

Did you report a bug on a previous release of Ubuntu?

  • 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 .

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:

Automatic Reporting

This step is optional, but will automatically report your bug numbers and update your signature file if you like it to. Also http://daniel.holba.ch/5-a-day-stats/ generates statistics from that data.

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

      BRYou can also use the "Software Sources" Editor: BR attachment:apt-sources.png

  2. Install the five-a-day package: 

    sudo apt-get update; sudo apt-get install five-a-day

  3. 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

  4. If you haven't done so, add your SSH key to Launchpad. If you don't have an SSH key, follow the instructions on this page to generate one. (Else 5-A-Day is not going to work.)

  5. Run 5-a-day --add: 

    5-a-day --add <bugnumbers>
    For example: {{{5-a-day --add 123456 123457 123458 123459 123460

}}}

  1. Done. Smile :-) (Please note: you can also use the 5-A-Day applet - see below.)

Further notes:''

Update ~/.signature

  1. Follow the steps above.

  2. Run: 

    5-a-day --update

    and it will automatically update your signature. (It will also preserve an old ~/.signature file if it finds it.)

  3. Make sure your mail client picks up the shiny new ~/.signature.

Generate a blog "signature"

  1. Follow the steps above.

  2. Run: 

    5-a-day --update --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.

  2. Run 

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

Check out this video to see how it works.

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? Smile :-)

  1. Run 

    5-a-day --add-team <your LoCo Team's LP ID>

    for example: 

    5-a-day --add-team ubuntu-berlin

    (Note: You need to member of that team.)

  2. If you're unsure what your team's Launchpad ID is,

    1. check out your Launchpad team participation page.

    2. find the LoCo team you're member of

    3. click on it

    4. check out the URL in the URL bar of your browser

Tagging 5-A-Day Bugs

This new feature is particularly useful during events like Hug Days or Bug Jams.

  1. Make sure you have five-a-day version >= 0.26 installed.

  2. Run 

    5-a-day --add-tag tag-you-are-going-to-use
  3. Add 5-A-Day bugs as usual.
  4. ...

  5. Run 

    5-a-day --remove-tag tag-you-are-going-to-use
    to stop using the particular tag.

CategoryBugSquad

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