GettingInvolved
|
Size: 1026
Comment:
|
← Revision 27 as of 2025-09-18 13:00:02 ⇥
Size: 3246
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| [[Include(BugSquad/Header)]] | #refresh 0 https://canonical-ubuntu-project.readthedocs-hosted.com/contributors/bug-triage/ |
| Line 3: | Line 3: |
| == Joining the Bug Squad == | <<Include(BugSquad/Header)>> |
| Line 5: | Line 5: |
| When joining the Bug Squad the only obligation is to keep up to date with bug management policies. There are no special skills required to join the Bug Squad. There is a lot of [:BugSquad/KnowledgeBase: documentation] available regarding bug management workflow and what information to gather when debugging a bug. | == Bug Squad == Consider joining the [[BugSquad|Bug Squad]] to keep up to date on current issues with triaging. However, joining is entirely optional but recommended. |
| Line 7: | Line 8: |
| To be a member of the Bug Squad you need to have [https://launchpad.net Launchpad] account (which you can [https://launchpad.net/+login easily create]), and then you can [https://launchpad.net/~bugsquad/+join join] the [https://launchpad.net/~bugsquad bugsquad team]. | Should you have any questions relating to triaging or other questions with regards to the Bug Squad team/process you can raise your questions in the [[irc://irc.freenode.org/#ubuntu-bugs|#ubuntu-bugs]] channel on [[IRC|IRC]]. Members of the [[BugSquad|Bug Squad]], [[UbuntuBugControl|Bug Control]], and Canonical employees are available to answer any questions you might have. |
| Line 9: | Line 10: |
| === Mailing list === | |
| Line 11: | Line 11: |
| You really should [https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad subscribe] to the [https://lists.ubuntu.com/archives/ubuntu-bugsquad mailing list]. Bug Day announcments and bug triaging discussion occurs there. | == Assigning Packages == Hundreds of bugs are filed [[https://bugs.launchpad.net/ubuntu/+bugs?field.status%3Alist=NEW&field.importance%3Alist=UNDECIDED&assignee_option=none&field.has_no_package=on|without a package]], either because the reporter did not know the correct package, or was not aware how to assign their bug to a package. Assigning a package to a bug increases the chance of it being fixed greatly by sending the bug right to the developers that can fix it. It is very easy for a new member to start here and learn how to navigate Launchpad while getting to know the community. |
| Line 13: | Line 14: |
| === IRC === | Eventually one can learn what information is needed for some common reports and ask the reporters to attach logs or confirm bug reports. This is a first step on towards more advanced triaging. |
| Line 15: | Line 16: |
| You can almost always find team members via [:IRC:IRC] on the channel #ubuntu-bugs on irc.freenode.org. | More information can be found by visiting the [[Bugs/FindRightPackage]] page. == Triaging Bugs == Bug triage is an essential part of Ubuntu's development. Triaging bugs consists of several things: * Responding to new bugs as they are filed. * Ensuring that new bugs have all the necessary information. * Assigning bugs to the proper package. * Confirming bug reports by trying to reproduce them. * Setting the priority of bugs reports. * Searching for and marking duplicates in the bug tracking system. * Sending bugs to their upstream authors, when applicable. * Cross-referencing bugs from other distributions. * Expiring old bugs. However, you don't need to do all of those things to help! Recreating a bug and setting the status to Confirmed is enough. Bug triage is an excellent way to start helping out. You get to learn a lot about Ubuntu, its available packages, its infrastructure, and you get a feel for the development pulse. You can learn how to triage bugs and chip in, just see the [[Bugs/HowToTriage]] page. == Hug Day == Another great way to get started is to participate in a [[UbuntuBugDay| Hug Day]]. A Hug Day is where we work together on triaging a specific section of Ubuntu in an effort to make a better release. It is called Hug Day because every bug worked on is worth a hug! After participating in a few Hug Days, consider [[UbuntuBugDay/Organizing| organizing a HugDay]] for a package that you wish to see get some TLC. == 5-a-day == Some awesome members of Bug Squad have committed to not only triage bugs, but have committed to touching 5 bugs every day! See [[5-A-Day]] for how to sign up for this optional group that can help track how many bugs you have triaged. ---- CategoryBugSquad |
Bug Squad
Consider joining the Bug Squad to keep up to date on current issues with triaging. However, joining is entirely optional but recommended.
Should you have any questions relating to triaging or other questions with regards to the Bug Squad team/process you can raise your questions in the #ubuntu-bugs channel on IRC. Members of the Bug Squad, Bug Control, and Canonical employees are available to answer any questions you might have.
Assigning Packages
Hundreds of bugs are filed without a package, either because the reporter did not know the correct package, or was not aware how to assign their bug to a package. Assigning a package to a bug increases the chance of it being fixed greatly by sending the bug right to the developers that can fix it. It is very easy for a new member to start here and learn how to navigate Launchpad while getting to know the community.
Eventually one can learn what information is needed for some common reports and ask the reporters to attach logs or confirm bug reports. This is a first step on towards more advanced triaging.
More information can be found by visiting the Bugs/FindRightPackage page.
Triaging Bugs
Bug triage is an essential part of Ubuntu's development.
Triaging bugs consists of several things:
- Responding to new bugs as they are filed.
- Ensuring that new bugs have all the necessary information.
- Assigning bugs to the proper package.
- Confirming bug reports by trying to reproduce them.
- Setting the priority of bugs reports.
- Searching for and marking duplicates in the bug tracking system.
- Sending bugs to their upstream authors, when applicable.
- Cross-referencing bugs from other distributions.
- Expiring old bugs.
However, you don't need to do all of those things to help! Recreating a bug and setting the status to Confirmed is enough.
Bug triage is an excellent way to start helping out. You get to learn a lot about Ubuntu, its available packages, its infrastructure, and you get a feel for the development pulse.
You can learn how to triage bugs and chip in, just see the Bugs/HowToTriage page.
Hug Day
Another great way to get started is to participate in a Hug Day. A Hug Day is where we work together on triaging a specific section of Ubuntu in an effort to make a better release. It is called Hug Day because every bug worked on is worth a hug!
After participating in a few Hug Days, consider organizing a HugDay for a package that you wish to see get some TLC.
5-a-day
Some awesome members of Bug Squad have committed to not only triage bugs, but have committed to touching 5 bugs every day! See 5-A-Day for how to sign up for this optional group that can help track how many bugs you have triaged.
BugSquad/GettingInvolved (last edited 2025-09-18 13:00:02 by sally-makin)