UbuntuBugControl

Differences between revisions 19 and 21 (spanning 2 versions)
⇤ ← Revision 19 as of 2008-04-04 19:33:37 →
Size: 3521
Editor: c-24-21-234-111
Comment:
← Revision 21 as of 2008-04-04 20:22:45 → ⇥
Size: 3818
Editor: c-24-21-234-111
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
The Ubuntu Bug Control team (ubuntu-bugcontrol in Launchpad), formerly known as ubuntu-qa, is a subset of the BugSquad who can change the [:Bugs/Importance importance] of bugs and set the [:Bugs/Status status] of a bug to "Won't Fix". You do this when you are [:Bugs/HowToTriage:triaging]. The Ubuntu Bug Control team (ubuntu-bugcontrol in Launchpad), formerly known as ubuntu-qa, is a subset of the BugSquad who can change the [:Bugs/Importance:importance] of bugs and set the [:Bugs/Status:status] of a bug to "Won't Fix". You do this when you are [:Bugs/HowToTriage:triaging].
Line 6: Line 6:
You need to show four things or have an Ubuntu Developer vouch for you and your ability to triage bugs: You need to demonstrate four things:
Line 8: Line 8:
 1. You promise to be polite to bug reporters, even if they don't deserve it. Even if they are rude to you, you have to respond gracefully and not take it personally.
 2. You need to understand [:Bugs/HowToTriage] and [:Bugs/Assignment] and also have read the [:Bugs/Importance] page. There's a particular procedure for triaging and Importance has a specific meaning, so we want to make sure you understand the conventions.
 3. You also need to be aware of the considerations to take when making an Apport crash report publicly visible. Documentation regarding this can be found at [https://wiki.ubuntu.com/Bugs/HowToTriage#head-f46ac7bd66be716a03d2d4fb0788725cc9cc7ba0 Triaging Apport crash reports].		  1. That you promise to be polite to bug reporters, even if they don't deserve it, by signing the Ubuntu Code of Conduct.
 2. You need to understand [:Bugs/HowToTriage] and be familiar with [:Bugs/Assignment:assigning bugs], choosing a bug [:Bugs/Status:status] and setting a bug's [:Bugs/Importance importance]. There's a particular procedure for triaging and Importance has a specific meaning, so we want to make sure you understand the conventions.
 3. You also need to be aware of the considerations to take when making an Apport crash report, there are private by default, publicly visible. Documentation regarding this can be found at [https://wiki.ubuntu.com/Bugs/HowToTriage#head-f46ac7bd66be716a03d2d4fb0788725cc9cc7ba0 Triaging Apport crash reports].
Line 12: Line 12:

Requirement 4 is waivable if you are an upstream developer / bug triager or if an Ubuntu developer vouches for you and your ability to triage bug reports.
Line 15: Line 17:
 * sign up: with the BugSquad.
Line 17: Line 18:
 * triage: [https://launchpad.net/distros/ubuntu/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=Unconfirmed&field.importance%3Alist=Undecided&assignee_option=none&field.assignee=&field.owner=&field.component=1&field.component=2&field.component-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_no_package.used=&search=Search some bugs] and keep a short list (at least 5) of your best ones.
Line 20: Line 20:
 * apply: to the [http://launchpad.net/people/ubuntu-bugcontrol Ubuntu Bug Control team] and reply to the Ubuntu Bug Control team application you will receive '''or'''
 * apply and e-mail BrianMurray directly with responses to the application provided below '''or'''
 * show up to an UbuntuBugDay and contact [:BrianMurray:bdmurray] in the `#ubuntu-bugs` [:IRC] channel on `irc.freenode.net`.		  * read: [:Bugs/Assignment].
 * triage: [https://launchpad.net/distros/ubuntu/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=Unconfirmed&field.importance%3Alist=Undecided&assignee_option=none&field.assignee=&field.owner=&field.component=1&field.component=2&field.component-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_no_package.used=&search=Search some bugs] and keep a short list (at least 5) of your best ones.

Ways to join:
 * Apply: to the [http://launchpad.net/people/ubuntu-bugcontrol Ubuntu Bug Control team] and reply to the Ubuntu Bug Control team application you will receive '''or'''
 * Apply and e-mail BrianMurray directly with responses to the application provided below '''or'''
 * Participate in an UbuntuBugDay and contact [:BrianMurray:bdmurray] in the `#ubuntu-bugs` [:IRC] channel on `irc.freenode.net` '''or'''
 * If you are an upstream developer or bug triager contact [https://launchpad.net/~jorge Jorge Castro]
Line 26: Line 31:
  2. Have you read [:Bugs/HowToTriage], [:Bugs/Assignment] and [:Bugs/Importance]? Do you have any questions about that documentation?   2. Have you read [:Bugs/HowToTriage], [:Bugs/Assignment], [:Bugs/Status] and [:Bugs/Importance]? Do you have any questions about that documentation?

The Ubuntu Bug Control team (ubuntu-bugcontrol in Launchpad), formerly known as ubuntu-qa, is a subset of the BugSquad who can change the [:Bugs/Importance:importance] of bugs and set the [:Bugs/Status:status] of a bug to "Won't Fix". You do this when you are [:Bugs/HowToTriage:triaging].

Requirements for joining

You need to demonstrate four things:

  1. That you promise to be polite to bug reporters, even if they don't deserve it, by signing the Ubuntu Code of Conduct.

  2. You need to understand [:Bugs/HowToTriage] and be familiar with [:Bugs/Assignment:assigning bugs], choosing a bug [:Bugs/Status:status] and setting a bug's [:Bugs/Importance importance]. There's a particular procedure for triaging and Importance has a specific meaning, so we want to make sure you understand the conventions.

  3. You also need to be aware of the considerations to take when making an Apport crash report, there are private by default, publicly visible. Documentation regarding this can be found at [https://wiki.ubuntu.com/Bugs/HowToTriage#head-f46ac7bd66be716a03d2d4fb0788725cc9cc7ba0 Triaging Apport crash reports].

  4. Have a list of triaged bugs that demonstrate you understand triaging.

Requirement 4 is waivable if you are an upstream developer / bug triager or if an Ubuntu developer vouches for you and your ability to triage bug reports.

In order to join:

Ways to join:

Application

  1. Do you promise to be polite to bug reporters even if they are rude to you or Ubuntu? Have you signed the Ubuntu Code of Conduct?
  2. Have you read [:Bugs/HowToTriage], [:Bugs/Assignment], [:Bugs/Status] and [:Bugs/Importance]? Do you have any questions about that documentation?
  3. What sensitive data should you look for in a private Apport crash report bug before making it public? See [:Bugs/HowToTriage] for more information.
  4. Is there a particular package or group of packages that you are interested in helping out with?
  5. Please list of five or more bugs which you have triaged. These bugs should demonstrate your understanding of the triage process and how to properly handle bugs. If there is a bug in your list that does not have an importance indicate what importance you would give it after becoming a member of Ubuntu Bug Control. Please use urls in your list of bugs.

[:CategoryBugSquad]BR [:CategoryUbuntuTeams]

UbuntuBugControl (last edited 2019-02-21 10:13:37 by brian-murray)