The New and Improved Ubuntu QA

For the last couple of weeks, Jordan Mantha been working behind the scenes on creating a community Ubuntu QA (quality assurance) team. For quite a while Canonical has largely driven QA efforts in Ubuntu. The community can and should step up in this area (see this wiki page for more background information).

In short, a new community-driven Ubuntu QA team is up and running! The IRC channel is #ubuntu-quality and the mailing list is ubuntu-qa.

From the team wiki page:

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 broken down 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)

Getting Involved

The main entry points for working on QA tasks are the BugSquad and Testing Team, however feel free to drop by #ubuntu-quality, if you are interested in Ubuntu QA.

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 (such as BugSquad or Testing Team)
  • 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

Huge props go to Emmet Hikory, Steve Beattie, Henrik Omma, and the rest of the team for helping this get launched.

So stay tuned for more exciting QA developments, feel free to contribute, and rock on!

Bookmark the permalink.

Leave a Reply