GettingInvolved
|
Size: 1521
Comment:
|
Size: 1604
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| == Joining the Bug Squad == | == Bug Squad == |
| Line 5: | Line 5: |
| When joining the Bug Squad the only obligation is to keep up to date with bug management policies. | Consider joining the BugSquad to keep up to date on current issues with triaging. However, joining is entirely optional. |
| Line 7: | Line 7: |
| The only special skills necessary to join the Bug Squad are curiousity and a desire to help. You don't need to know python, perl, C or some other programming language. There is a lot of [:BugSquad/KnowledgeBase: documentation] available regarding bug management workflow and what information to gather when debugging a bug. | Members of the Bug Squad and Canonical employees are available in #ubuntu-bugs who can answer any questions you might have. |
| Line 9: | Line 9: |
| To be a member of the Bug Squad you do need to have a [https://launchpad.net Launchpad] account, and then you can [https://launchpad.net/~bugsquad/+join join] the [https://launchpad.net/~bugsquad bugsquad team]. | |
| Line 11: | Line 10: |
| === Mailing list === | == Assigning Packages == |
| Line 13: | Line 12: |
| You 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 discussions occur there. | 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 [:Bugs/FindRightPackage: 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 15: | 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 17: | Line 16: |
| You can almost always find team members via [:IRC:IRC] on the channel #ubuntu-bugs on irc.freenode.org. | |
| Line 21: | Line 19: |
| A great way to get started is to join in an [https://wiki.ubuntu.com/UbuntuBugDay Ubuntu Hug Day]. A Hug Day is where we collectively work on making bug reports more complete, triaging and even fixing them. It is called Hug Day because every bug worked on is worth a hug! Members of the Bug Squad and Canonical employees are available in #ubuntu-bugs who can answer any questions you might have. | Another great way to get started is to participate in a [https://wiki.ubuntu.com/UbuntuBugDay Hug Day. A Hug Day is where we work together on triaging a specific section of Ubuntu in 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 attention. |
Bug Squad
Consider joining the BugSquad to keep up to date on current issues with triaging. However, joining is entirely optional.
Members of the Bug Squad and Canonical employees are available in #ubuntu-bugs who can answer any questions you might have.
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 [:Bugs/FindRightPackage: 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.
Hug Day
Another great way to get started is to participate in a [https://wiki.ubuntu.com/UbuntuBugDay Hug Day. A Hug Day is where we work together on triaging a specific section of Ubuntu in 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 attention.
BugSquad/GettingInvolved (last edited 2025-09-18 13:00:02 by sally-makin)