UbuntuBugControl

Differences between revisions 10 and 11
Revision 10 as of 2007-07-12 14:15:56
Size: 3304
Editor: yttrium
Comment: Modified requirements for joining Ubuntu QA
Revision 11 as of 2007-07-16 20:59:48
Size: 3307
Editor: 249-244
Comment: fixed howtotriage link
Deletions are marked like this. Additions are marked like this.
Line 29: Line 29:
  3. What sensitive data should you look for in a private Apport crash report bug before making it public? See Bugs/HowToTriage[1] for more information.   3. What sensitive data should you look for in a private Apport crash report bug before making it public? See [:Bugs/HowToTriage][1] for more information.

The UbuntuQA team is not the Quality Assurance (QA) team for Ubuntu.

The real QA team is the Ubuntu BugSquad.

Rather, it is a subset of the BugSquad who can change the [:Bugs/Importance] and Milestone fields for any Ubuntu bug. You do this when you are [:Bugs/HowToTriage:triaging].

Requirements for joining

You need to show four things or have an Ubuntu Core Developer vouch for you and your ability to triage bugs:

  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 know [:Bugs/HowToTriage] and 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].

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

In order 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] 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][1] 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 QA. Please use urls in your list of bugs.


[:CategoryBugSquad]BR [:CategoryUbuntuTeams]

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