QATeam
|
Size: 903
Comment: created
|
Size: 3985
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| <<Include(QATeam/Header)>> | |
| Line 2: | Line 3: |
| The Ubuntu QA team is focused on improving the general quality of the distribution. We do this through manual and automated testing, advising other teams on QA procedures and working with bug reports. | 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. |
| Line 4: | Line 5: |
| The main entry oints for the QA team are the BugSquad and the [:TestingTeam:Testing Team]. The {{{ubuntu-qa}}} Launchpad team is a restricted team where members are admitted after an application process, and gives the ability to set the priority of bugs. | 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) |
| Line 6: | Line 11: |
| == Meetings == | === Contact === * [[https://launchpad.net/~ubuntu-qa|Launchpad team]] * [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa|Ubuntu QA mailing list]] * '''#ubuntu-quality''' on irc.freenode.net |
| Line 8: | Line 16: |
| The QA team has regular weekly meetings Wednesdays at 16.00 UTC on '''#ubuntu-meeting'''. Feel free to join in! | === Meetings === |
| Line 10: | Line 18: |
| === Agenda - 2007-10-03 == | The Ubuntu QA team has regular weekly meetings Wednesdays at 17:00 UTC in '''#ubuntu-meeting'''. See agenda and archive at [[/Meetings]] |
| Line 12: | Line 20: |
| * Report from the testing mini-sprint in Oslo * Selecting topics for UDS * Release Candidate next week - where are we on bugs? * QA team wiki pages * Should this one be merged with UbuntuQA? * How can we make the connections between the teams less confusing? |
The Canonical QA team holds regular Automation planning meetings on Wednesdays at 17:00 UTC on '''Skype'''. See agenda and archive at [[/Meetings/Automation]] === Getting Involved === The main entry points for working on QA tasks are the BugSquad and [[Testing|Testing Team]] (see below for contact details). Because Ubuntu QA is a coordination/development/working team the membership guidelines are:<<BR>> * 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: <<BR>> * 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 [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa|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 == ||'''Name'''||'''Purpose/focus'''||'''Launchpad'''||'''Mailing list'''||'''IRC'''||'''Primary contact(s)'''|| ||[[BugSquad|Bug Squad]]||Bug triage||[[https://launchpad.net/~bugsquad|bugsquad]]||[[https://lists.ubuntu.com/mailman/listinfo/Ubuntu-bugsquad|ubuntu-bugsquad]]||'''#ubuntu-bugs'''||Brian Murray (bdmurray)|| ||Bug Control||Extra bug permissions||[[https://launchpad.net/~ubuntu-bugcontrol|ubuntu-bugcontrol]]||[[https://lists.ubuntu.com/mailman/listinfo/Ubuntu-bugsquad|ubuntu-bugsquad]]||'''#ubuntu-bugs'''||Brian Murray (bdmurray)|| ||[[Testing|Testing Team]]||Application/ISO testing||[[https://launchpad.net/~ubuntu-testing|ubuntu-testing]]||[[https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa|ubuntu-qa]]||'''#ubuntu-testing'''||heno/stgraber|| ||SRU Verification||SRU testing/validation||[[https://launchpad.net/~sru-verification|sru-verification]]||[[https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa|ubuntu-qa]]||'''#ubuntu-quality'''||Steve Beattie (sbeattie)|| ||[[QATeam|Ubuntu QA]]||QA coordination/development||[[https://launchpad.net/~ubuntu-qa|ubuntu-qa]]||[[https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa|ubuntu-qa]]||'''#ubuntu-quality'''||Jordan Mantha (Laser''''''Jock)|| ||<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
#ubuntu-quality on irc.freenode.net
Meetings
The Ubuntu QA team has regular weekly meetings Wednesdays at 17:00 UTC in #ubuntu-meeting. See agenda and archive at /Meetings
The Canonical QA team holds regular Automation planning meetings on Wednesdays at 17:00 UTC on Skype. See agenda and archive at /Meetings/Automation
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
Name |
Purpose/focus |
Launchpad |
Mailing list |
IRC |
Primary contact(s) |
Bug triage |
#ubuntu-bugs |
Brian Murray (bdmurray) |
|||
Bug Control |
Extra bug permissions |
#ubuntu-bugs |
Brian Murray (bdmurray) |
||
Application/ISO testing |
#ubuntu-testing |
heno/stgraber |
|||
SRU Verification |
SRU testing/validation |
#ubuntu-quality |
Steve Beattie (sbeattie) |
||
QA coordination/development |
#ubuntu-quality |
Jordan Mantha (LaserJock) |
QATeam (last edited 2021-08-06 08:23:28 by guiverc)