UbuntuBugControl
2823
Comment: Added having a CoreDev vouch for you
|
3304
Modified requirements for joining Ubuntu QA
|
Deletions are marked like this. | Additions are marked like this. |
Line 9: | Line 9: |
You need to show three things or have an Ubuntu Core Developer vouch for you and your ability to triage bugs: | You need to show four things or have an Ubuntu Core Developer vouch for you and your ability to triage bugs: |
Line 11: | Line 11: |
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 know the conventions. 3. Have a list of triaged bugs that demonstrate you understand triaging. |
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. |
Line 18: | Line 19: |
* sign the [http://www.ubuntu.com/community/conduct Ubunt Code of Conduct]. | * [https://launchpad.net/codeofconduct sign] the [http://www.ubuntu.com/community/conduct Ubuntu Code of Conduct]. |
Line 28: | Line 29: |
3. Is there a particular package or group of packages that you are interested in helping out with? 4. 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. |
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. |
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:
- 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.
- 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.
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].
- Have a list of triaged bugs that demonstrate you understand triaging.
In order to join:
sign up: with the BugSquad.
[https://launchpad.net/codeofconduct sign] the [http://www.ubuntu.com/community/conduct Ubuntu Code of Conduct].
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 (about 5) of your best ones.
- read: [:Bugs/Importance].
apply: to the [http://launchpad.net/people/ubuntu-qa UbuntuQA team] and reply to the Ubuntu QA 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.
Application
- 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?
- Have you read [:Bugs/HowToTriage] and [:Bugs/Importance]? Do you have any questions about that documentation?
- 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.
- Is there a particular package or group of packages that you are interested in helping out with?
- 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.
Links
- [:Bugs/HowToTriage]
[http://launchpad.net/people/ubuntu-qa UbuntuQA in Launchpad]
UbuntuBugControl (last edited 2019-02-21 10:13:37 by brian-murray)