UbuntuBugControl

Differences between revisions 25 and 26
⇤ ← Revision 25 as of 2008-06-25 20:18:21 →
Size: 4482
Editor: c-24-21-234-111
Comment: Have applications sent to mailing list not bdmurray
← Revision 26 as of 2008-08-06 16:29:38 → ⇥
Size: 4517
Editor: localhost
Comment: converted to 1.6 markup
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 "Triaged" or "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 "Triaged" or "Won't Fix". You do this when you are [[Bugs/HowToTriage|triaging]].
Line 9: Line 9:
 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].		  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 17: Line 17:
 * [https://launchpad.net/codeofconduct sign] the [http://www.ubuntu.com/community/conduct Ubuntu Code of Conduct].
 * read: [:Bugs/Importance].
 * read: [:Bugs/Status].
 * 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.		  * [[https://launchpad.net/codeofconduct|sign]] the [[http://www.ubuntu.com/community/conduct|Ubuntu Code of Conduct]].
 * read: [[Bugs/Importance]].
 * read: [[Bugs/Status]].
 * 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.
Line 24: Line 24:
 * Apply: to the [http://launchpad.net/people/ubuntu-bugcontrol Ubuntu Bug Control team] and send the the Ubuntu Bug Control team application you will receive to ubuntu-bugcontrol AT lists.launchpad.net '''or'''  * Apply: to the [[http://launchpad.net/people/ubuntu-bugcontrol|Ubuntu Bug Control team]] and send the the Ubuntu Bug Control team application you will receive to ubuntu-bugcontrol AT lists.launchpad.net '''or'''
Line 26: Line 26:
 * If you are an upstream developer or bug triager contact [https://launchpad.net/~jorge Jorge Castro]  * If you are an upstream developer or bug triager contact [[https://launchpad.net/~jorge|Jorge Castro]]
Line 30: Line 30:
  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.		   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.
Line 50: Line 50:
 * [:Bugs/HowToTriage]
 * [:Bugs/Importance]
 * [:Bugs/Status]
 * [:Bugs/Assignment]
 * [http://launchpad.net/people/ubuntu-bugcontrol Ubuntu Bug Control in Launchpad]		  * [[Bugs/HowToTriage]]
 * [[Bugs/Importance]]
 * [[Bugs/Status]]
 * [[Bugs/Assignment]]
 * [[http://launchpad.net/people/ubuntu-bugcontrol|Ubuntu Bug Control in Launchpad]]
Line 57: Line 57:
[:CategoryBugSquad][[BR]]
[:CategoryUbuntuTeams]		 [[CategoryBugSquad]]<<BR>>
[[CategoryUbuntuTeams]]

The Ubuntu Bug Control team (ubuntu-bugcontrol in Launchpad), formerly known as ubuntu-qa, is a subset of the BugSquad who can change the importance of bugs and set the status of a bug to "Triaged" or "Won't Fix". You do this when you are 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 assigning bugs, choosing a bug status and setting a bug's 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 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:

  • Apply: to the Ubuntu Bug Control team and send the the Ubuntu Bug Control team application you will receive to ubuntu-bugcontrol AT lists.launchpad.net or

  • Apply and e-mail ubuntu-bugcontrol AT lists.launchpad.net directly with responses to the application provided below or

  • If you are an upstream developer or bug triager contact Jorge Castro

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.

Evaluation Criteria

The application review is a subjective process however a list of what we look for follows:

  1. Has the applicant provided the importance they would give a bug report?
  2. Is the applicant respectful and tactful in their communications?
  3. Are the applicant's comments detailed and do they explain their actions?

  4. Is the applicant following the DebuggingProcedures for the package the bug report is about?

  5. Has the applicant made bug titles or descriptions more descriptive?
  6. Has the applicant added any bug watches to bug reports? (Linked bugs upstream)
  7. Has the applicant forwarded any bugs upstream? (Registered in upstream bts and reported an Ubuntu bug)

CategoryBugSquad
CategoryUbuntuTeams

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