Universe and Multiverse contain several thousand packages. A valuable contribution to Ubuntu is fixing their bugs. Bugs tagged as bitesize are specially suited for new contributors.
- Try to confirm the bug.
- Get the source for it.
- Get it fixed with help of
- Bug related:
Universe and Multiverse bugs. There are a lot of bugs, some might even be easy to fix.
Confirmed security bugs. Fixing a security bug in a community-supported Ubuntu package is a great way to learn about Ubuntu, packaging and bug fixing in general.
Universe and Multiverse bugs with patches attached. If you can help to review the patches, we'd probably get some good fixes in. (Check out http://daniel.holba.ch/temp/no_attention to find bugs with patches that are not in the sponsors queue yet.)
Universe and Multiverse Incomplete bugs. Some of the Incomplete bugs have been in that state for a long time, let's review them.
Universe and Multiverse bugs that need forwarding Upstream. These bugs need to get forwarded upstream.
Universe and Multiverse Fix Committed bugs. Make sure that these Fix Committed bugs are really in the process of getting fixed.
Universe and Multiverse crasher bugs. Let's forward them upstream and check for dups.
- Tagged bugs:
Universe and Multiverse bugs marked as packaging. These bugs are all packaging related.
Universe and Multiverse bugs marked as bitesize. These bugs are for new contributors.
Universe and Multiverse bugs marked as upgrade. Bugs that request new upstream versions - please help reviewing them carefully.
Universe and Multiverse bugs marked as ftbfs. Bugs describing build failures of packages.
Universe and Multiverse bugs marked as unmetdeps. Bugs that indicate packages not being installable due to missing dependencies.
However you contribute to Universe bug squashing, you are welcome to come and join the Universe bug squashers in #ubuntu-bugs and #ubuntu-motu on IRC. In these channels we have a bug bot called ubotu, that can give us more information on bug numbers.
For general information about bug fixing and helping with bugs, please read ReportingBugs and HelpingWithBugs. Before filing bugs, consider reading How to Report Bugs Effectively. Also search for the bug in Launchpad: somebody might have found it before you!
To make bugs easier to find for new contributors and to group them into helpful classes, you can help by tagging bugs on launchpad as:
packaging if you think that the bug lies only in the packaging.
bitesize if you think that it's suitable for a beginner.
upgrade if the upgrade of a package is suggested and the request should be carefully checked.
ftbfs if the bug described a problem to build the package.
unmetdeps if the package is not installable due to missing dependencies.
needs-packaging if it's a request for an application which isn't in the repositories.
patch if there is a patch attached to the bug.
If you DO NOT have upload permissions, check out SponsorshipProcess on how to get your changes included in Ubuntu.
If you DO have upload permissions, check the bugs that u-s is subscribed to from time to time: if the package was uploaded and built on all architectures, you can close the bug by marking it as "Fix released".
Try to check if your report or your fix could be sent to Debian as well. Read ContributingToDebian for more information.
We already managed to build teams, whose launchpad IDs can be found in the comprehensive list: MOTU/Teams
Some bugs, however, are still unassigned and will have to be assigned to the right people/teams.