Teams

Specific Triaging workflows

These are some Ubuntu teams which handle their own bugs, you may want to check their pages to find out more about specific details of the team's policy or anything else which is relevant.

Launchpad Teams in General

You can browse for teams, but here's a small overview of some useful ones.

Team

Packages they take care of

bluetooth

Bluetooth related bugs

desktop-bugs

the GNOME landscape in main

galago

Galago related bugs

kubuntu-team

KDE and Kubuntu

mono

Mono Team

motu

Universe and Multiverse

motu-swat

Security team for Universe and Multiverse

telepathy

Telepathy related bugs

ubuntu-art

Artwork related bugs

ubuntu-audio

audio-related infrastructure

ubuntu-kernel-team

the Kernel

ubuntu-installer

Installer (both d-i and ubiquity)

ubuntu-security

Security team for main

ubuntu-x-swat

xorg

Informing teams of bugs

Where an appropriate team exists for handling this class of bug, subscribe the team as you go. Where a package is clearly associated with a particular team, the team will often be registered as a bug contact, and so will be automatically subscribed. Some common cases which aren't usually handled automatically:

Edubuntu bugs

edubuntu-team

Kubuntu bugs

kubuntu-team

Xubuntu bugs

xubuntu-team

Accessibility bugs

accessibility

ACPI-related bugs

acpi-bugzilla

Audio related bugs

ubuntu-audio

CJK-related bugs

ubuntu-cjk-testers

Laptop-specific bugs

ubuntu-laptop

Package archive requests and bugs

ubuntu-archive

Printing-related bugs

ubuntu-printing

Server-related bugs

ubuntu-server

Security-related bugs in main/restricted

ubuntu-security

Security-related bugs in universe/multiverse

motu-swat

X-related bugs

ubuntu-x-swat

Mozilla and related

mozilla-bugs

Wherever there is at least one person taking responsibility for a class of bugs, we should create a team for that class in order to allow others to join and easily participate in the subset of bugs which interests them.

Back to HelpingWithBugs.

CategoryBugSquad