Differences between revisions 28 and 30 (spanning 2 versions)
Revision 28 as of 2007-11-14 09:32:46
Size: 8006
Editor: i59F77A9D
Revision 30 as of 2007-11-14 15:56:34
Size: 2152
Editor: i59F720DB
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
Packaging new software is a valuable task, but sometimes not trivial. More information on how to do it:

 * [ Packages requested by others]
 * [:UbuntuDevelopment#NewPackages:Policy for inclusion of new packages]
 * [:PackagingGuide/Basic:How to package from scratch]
Check out '''["MOTU/TODO/NewSoftware"]'''.
Line 48: Line 43:
 * [ All open universe/multiverse bugs]
 * Bug related:
  * [ Universe and Multiverse bugs]. There are a lot of bugs, some might even be easy to fix.
  * [ Universe and Multiverse bugs with patches attached]. If you can help to review the patches, we'd probably get some good fixes in.
  * [ 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 unmdetdeps]. 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.

=== Filing Bugs ===
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!

=== 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 [ 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 [ unassigned] and will have to be assigned to the right people/teams.

== Useful links ==
 * The [ Debian bug tracking system] might already have a bug open (or already fixed!) waiting for your package. And the [ 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 [ this page about reporting bug to Debian by email].
 * [ How to Report Bugs Effectively], by Simon Tatham. A must rea
Check out '''["MOTU/TODO/Bugs"]'''.


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


Packaging New Software

Check out ["MOTU/TODO/NewSoftware"].

Unmet Dependencies

Help to fix packages that are not installable. A list can be found [ on debcheck] updated 6-hourly.

Other Packaging tasks


Universe / Multiverse Bugs

Check out ["MOTU/TODO/Bugs"].


Weekly Tasks


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

MOTU/TODO (last edited 2016-10-27 07:45:07 by dholbach)