New packages

For a piece of software to be included in Ubuntu, it must meet the Ubuntu License Policy.

Requesting a new package for Ubuntu

Packages that have recently been added to Debian unstable will be automatically synced into Ubuntu prior to the Debian Import Freeze (DIF). Once synced, they will follow the proposed-migration flow. If instead the release process already reached the Debian Import Freeze, you must file a bug with the summary field “Please sync <packagename> from debian <distro>” where <packagename> is the package you would like to see.

To get a package into Ubuntu, file a bug in Launchpad and make sure it has the tag needs-packaging.

In the bug, mention where to get the source for it and which license it is under. An example request is shown here. Make sure you check which packages have already been requested.

Since we want Free Software to reach as many people as possible and do not want too much duplication of packaging effort, it is useful for packages that meet the requirements of the Debian Free Software Guidelines to be requested within Debian’s Work-Needing and Prospective Packages (WNPP) process by filing a Request for Package (RFP) bug on the WNPP package in Debian’s bug tracker.

If you file a needs-packaging bug, please link it to the Debian WNPP bug as well.

Packaging it yourself

If you want to try packaging it yourself, refer to our guide on How to create a new package.

NEW packages through Debian

Ubuntu regularly incorporates source packages from Debian, so it is encouraged to upload a package to Debian first. Your package will reach a much broader audience if it is in Debian and all of its derivatives.

To have faster reviews, several teams have been set up to manage subsets of packages, including:

See the full list of teams. If there is no team available that takes care of the group of packages you are interested in, contact the Debian mentors (see “Further Reading” below).

Ubuntu does virtually all package maintenance in teams. If your package is related to any of the existing teams within Debian, work with that team to get the package uploaded to Debian. If there is no team already, consider starting a new team within Debian (e.g. at Alioth) for any package that is likely to have a significant number of bugs or other maintenance overheads (like architecture-specific issues).

Additionally, there are roughly an order of magnitude more Debian Developers than Ubuntu Developers. It is comparably more difficult to get a new package into Ubuntu due to the sheer volume of requests compared to the available resources for reviews. In many cases, people have an easier time getting their package into Ubuntu via Debian than doing so directly.

If you choose to do this, file an Intent to Package (ITP) bug on the WNPP package in Debian to let others know you’re working on it (reportbug -B debian wnpp should do the right thing). Then, go through the Debian Mentors to get the package uploaded. A number of Ubuntu Developers are also Debian Maintainers or Debian Developers, so they may be able to help you navigate Ubuntu/Debian interactions.

Some good tips

Request sponsorship

Submitting new packages through Debian is the preferred path. However, if your package is Ubuntu-specific or can’t go into Debian for some other reason, request sponsorship to have it reviewed and uploaded.

Start with How to find a sponsor for the current sponsorship process.

Deadline

Feature Freeze is the latest approval date. It is recommended to get things done a couple of weeks earlier than that, as getting approval may take some time. If you have a deadline, make sure you factor review and approval time into your timeline.

Review of new packages

After the new package is uploaded, it will show up and be held in the NEW queue. It is then checked by the Archive Admin team.

Further reading