Ubuntu Wiki

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

• Launchpad team

• Ubuntu QA mailing list

• #ubuntu-quality on irc.freenode.net

Meetings

The Ubuntu QA team has regular weekly meetings Wednesdays at 17:00 or 19:00 UTC in #ubuntu-quality. 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

QA related teams