UbuntuBugControl

Differences between revisions 35 and 36
⇤ ← Revision 35 as of 2010-07-09 17:40:04 →
Size: 6186
Editor: pool-71-252-251-234
Comment:
← Revision 36 as of 2010-07-09 18:13:10 → ⇥
Size: 6227
Editor: c-98-246-63-231
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 "Triaged" or "Won't Fix". You do this when you are [[Bugs/HowToTriage|triaging]]. The Ubuntu Bug Control team (ubuntu-bugcontrol in Launchpad) is a subset of the BugSquad who can change the [[Bugs/Importance|importance]] of Ubuntu bug tasks and set the [[Bugs/Status|status]] of an Ubuntu bug task to "Triaged" or "Won't Fix". You do this when you are [[Bugs/HowToTriage|triaging]].
Line 6: Line 6:
Both individuals and teams can join BugControl. There are generic requirements, and specific requirements. Both individuals and teams can join UbuntuBugControl. There are generic requirements, and specific requirements.
Line 15: Line 15:
 * read: the [[Debugging]] sections relative to your interest.  * read the [[Debugging]] sections relative to your interest.
Line 21: Line 21:
 1. That you promise to be polite to bug reporters, even if they don't deserve it, by signing the Ubuntu Code of Conduct.
 1. 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.
 1. You also need to be aware of the considerations to take when making an Apport crash report, these are private by default and publicly visible. Documentation regarding this can be found at [[ https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20crash%20reports | Triaging Apport crash reports ]].		  1. That you promise to be polite to bug reporters, even if they may not deserve it, by signing the Ubuntu Code of Conduct.
 1. You need to understand [[Bugs/HowToTriage]] and be familiar with [[Bugs/Assignment|assigning bugs]], choosing a bug task [[Bugs/Status|status]] and setting a bug task's [[Bugs/Importance|importance]]. There is a particular procedure for triaging and Importance has a specific meaning, so we want to make sure you understand the conventions.
 1. You also need to be aware of the considerations to take when making an Apport crash report publicly visible. By default these are private. Documentation regarding this can be found at [[ https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20crash%20reports | Triaging Apport crash reports ]].
Line 32: Line 32:
 * 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.  * 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 64: Line 64:
  1. The team '''must''' be a closed one (i.e., a moderated team).   1. The team '''must''' be a closed or moderated one.
Line 66: Line 66:
  1. The team '''must''' have at least one representative tasked with educating new members on BugControl policies.
  1. The representative above '''must''' be a current member of BugControl.		   1. The team '''must''' have at least one representative tasked with educating new members on UbuntuBugControl policies.
  1. The representative above '''must''' be a current member, directly or indirectly, of UbuntuBugControl.
Line 74: Line 74:
  * identify who is/are the representative(s) -- give us the link to the LP home of each one.   * identify who is/are the representative(s) -- give us the link to the Launchpad page of each one.

The Ubuntu Bug Control team (ubuntu-bugcontrol in Launchpad) is a subset of the BugSquad who can change the importance of Ubuntu bug tasks and set the status of an Ubuntu bug task to "Triaged" or "Won't Fix". You do this when you are triaging.

Requirements for joining

Both individuals and teams can join UbuntuBugControl. There are generic requirements, and specific requirements.

Generic Requirements

Requirements for Individuals

You need to demonstrate four things:

  1. That you promise to be polite to bug reporters, even if they may not 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 task status and setting a bug task's importance. There is 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. By default these are private. Documentation regarding this can be found at Triaging Apport crash reports.

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

Warning /!\ Requirement 4 can be waived 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:

Application

Ways to join:

  • Apply to the Ubuntu Bug Control team and e-mail your application to ubuntu-bugcontrol AT lists.launchpad.net; please copy & answer the questions below in an email to ubuntu-bugcontrol AT lists.launchpad.net:

    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 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 (and explain the reasoning) you would give it after becoming a member of Ubuntu Bug Control. Please use urls in your list of bugs.

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

  • Membership in some teams also grants membership to Ubuntu Bug Control, for example: ubuntu-core-dev, ubuntu-core-doc, and ubuntu-dev. You can find if your team is a member by visiting the team's homepage and looking at the "Subteam of" section.

Evaluation Criteria

The application review is a subjective process; however a list of what we usually 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)
  8. Is the reasoning for the bug Importance valid?

Requirements for Teams

  1. The team must be a closed or moderated one.

  2. The team must require its members to sign the Ubuntu Code of Conduct.

  3. The team must have at least one representative tasked with educating new members on UbuntuBugControl policies.

  4. The representative above must be a current member, directly or indirectly, of UbuntuBugControl.

Application

One of the team's administrators should e-mail the team's application to ubuntu-bugcontrol AT lists.launchpad.net. Please give us:

  • a brief reasoning of why it is important for the team to be a member.
  • identify who is/are the representative(s) -- give us the link to the Launchpad page of each one.

Evaluation Criteria

One of the BugControl administrators will review the application and act on it. This may require e-mail/IRC exchange. Evaluation is subjective.

CategoryBugSquad
CategoryUbuntuTeams

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