QATeam

Differences between revisions 42 and 43
Revision 42 as of 2008-08-18 17:15:07
Size: 3630
Editor: c-24-21-234-111
Comment:
Revision 43 as of 2008-09-18 11:00:54
Size: 3823
Editor: cpc1-oxfd8-0-0-cust993
Comment:
Deletions are marked like this. Additions are marked like this.
Line 51: Line 51:

||<tablestyle="width:95%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Sub-pages:'''||<<Navigation(children,1)>>||
||<tablestyle="width:100%;" style="width: 40px; border: none; -moz-border-radius-topleft: 15px ;-moz-border-radius-bottomleft: 15px; background-color: #F1F1DD; border: none; -moz-border-radius-topright: 15px;-moz-border-radius-bottomright: 15px; font-size: 0.75em; text-align: left;">~+'''Sub-pages:'''+~<<Navigation(children,1)>>||

The Ubuntu QA team is focused on developing tools, policies, and practices for ensuring Ubuntu's quality as a distribution as well as providing general advice, oversight, and leadership of QA activities within the Ubuntu project.

In general, QA in Ubuntu is divided into the following areas:

  • Defect Management (Bug Triage)
  • Quality Control (Update, Application, and Pre-Release Testing)
  • Quality Assurance (Verification of Changes, Policy Compliance Review)
  • Product Improvement (Development)

Contact

Meetings

The Ubuntu QA team has regular weekly meetings Wednesdays at 17:00 UTC in #ubuntu-meeting. See agenda and archive at /Meetings

Getting Involved

The main entry points for working on QA tasks are the BugSquad and Testing Team (see below for contact details).

Because Ubuntu QA is a coordination/development/working team the membership guidelines are:

  • Individuals, not teams may be members.
  • Memberships expire annually and can be renewed by members themselves.
  • People from all areas of QA are encouraged to join.

Requirements to join the team:

  • established record of contributing to QA in Ubuntu (see the list of relevant teams below)
  • be an Ubuntu Member or ready to become one (i.e. significant and sustained contribution to Ubuntu)
  • an introductory email sent to the ubuntu-qa list introducing yourself, your previous QA work, and your plans for working in the team.

What kinds of things does Ubuntu QA do?

  • Coordinate between the various QA-related teams
  • Build communities around QA work and help them run smoothly
  • Provide lead-from-the-front leadership to Ubuntu's QA projects

  • Assess and communicate Ubuntu's QA needs
  • Develop tools and services needed in Ubuntu QA work
  • Work on creating consistent and efficient QA-related policies
  • whatever else comes up or people want to contribute

Name

Purpose/focus

Launchpad

Mailing list

IRC

Primary contact(s)

Bug Squad

Bug triage

bugsquad

ubuntu-bugsquad

#ubuntu-bugs

Brian Murray (bdmurray)

Bug Control

Extra bug permissions

ubuntu-bugcontrol

ubuntu-bugsquad

#ubuntu-bugs

Brian Murray (bdmurray)

Testing Team

Application/ISO testing

ubuntu-testing

ubuntu-qa

#ubuntu-testing

heno/stgraber

SRU Verification

SRU testing/validation

sru-verification

ubuntu-qa

#ubuntu-quality

Steve Beattie (sbeattie)

Ubuntu QA

QA coordination/development

ubuntu-qa

ubuntu-qa

#ubuntu-quality

Jordan Mantha (LaserJock)

Sub-pages:

QATeam (last edited 2021-08-06 08:23:28 by guiverc)