TODO

Revision 27 as of 2007-11-14 09:29:09

Clear message

Include(MOTU/Headers/Menu)

There's always a lot of work to do in Ubuntu's Universe and Multiverse.

Here a quick list of suggestions, where you can help out:

General Tasks

Anchor(NewSoftware)

Packaging New Software

Packaging new software is a valuable task, but sometimes not trivial. More information on how to do it:

Unmet Dependencies

Help to fix packages that are not installable. A list can be found [http://alt.qeuni.net/~william/debcheck/debcheck.py?list=relationship%2dDepends&arch=ANY on debcheck] updated 6-hourly.

Other Packaging tasks

Anchor(Bugs)

Universe / Multiverse Bugs

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.

Filing Bugs

For general information about bug fixing and helping with bugs, please read ReportingBugs and HelpingWithBugs. Before filing bugs, consider reading [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively]. Also search for the bug in [https://launchpad.net/ubuntu/+bugs Launchpad]: somebody might have found it before you!

Tagging Bugs

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.

Fixing Bugs

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 [https://bugs.launchpad.net/~ubuntu-universe-sponsors/+subscribedbugs bugs that u-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".

Contributing Upstream

Try to check if your report or your fix could be sent to Debian as well. Read ContributingToDebian for more information.

Teams

We already managed to build teams, whose launchpad IDs can be found in the comprehensive list: ["MOTU/Teams"]

Unassigned Bugs

Some bugs, however, are still [https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=datecreated&field.status%3Alist=Unconfirmed&field.status%3Alist=Needs+Info&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&assignee_option=none&field.assignee=&field.owner=&field.component=4&field.component=3&field.component-empty-marker=1&field.status_upstream=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_no_package.used=&search=Search unassigned] and will have to be assigned to the right people/teams.

  • The [http://bugs.debian.org/ Debian bug tracking system] might already have a bug open (or already fixed!) waiting for your package. And the [http://packages.qa.debian.org/ Debian Package Tracking System] might have some info too. It's always worth looking!

  • When you fix a bug in Ubuntu, don't forget (if applicable) to file a bug in Debian and attach your patch. It will make more people happier if the bug is fixed in both Debian and Ubuntu, and we won't have to merge our fix when Debian releases a new version of the package. See [http://www.debian.org/Bugs/Reporting this page about reporting bug to Debian by email].

  • [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively], by Simon Tatham. A must rea

Weekly Tasks

Include(MOTU/TODO/Weekly)


Go back to [:MOTU].BR ["CategoryMOTU"]