Ubuntu launches a community quality assurance team

[newbie2]

I'm pleased to announce that a community-driven Ubuntu QA team has
formally been created [0] and is rocking already! I'll keep this
short, but the basic team description/purpose is:

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. [1]

We are broadly looking at enhancing the awareness and contribution to
QA around Ubuntu as well as helping people interested in serious QA
work find a common, collaborative, and open environment. I've put more
details on my blog announcement [2] and the team wiki page [1] so
please have a quick look over the details. We are looking to have a
very diverse team and welcome people to contribute/join.

-Jordan Mantha (on behalf of the Ubuntu QA team)

http://lwn.net/Articles/290195/
http://fridge.ubuntu.com/node/1594

[wersdaluv]

Cool! :)

[madjr]

about time :popcorn:

but it still need members and volunteers.

so if you were pissed with the low quality of hardy then you should join up



The New and Improved Ubuntu QA
Fri, 2008-07-18 04:00 — nali

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!



Now the guys behind kde4 should have had a QA team:


KD4's Wild rationalizations (http://linuxhaters.blogspot.com/2008/07/wild-rationalizations.html)

interesting read