In order 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). After the Debian Import Freeze, you will have to file a bug with the summary field "Please sync <packagename> from debian <distro>" where <packagename> is the package you would like to see. Find the date for Debian Import Freeze on the release schedule page.
To get a package into Ubuntu, please file a bug in Launchpad and make sure it has the tag needs-packaging. Please mention where to get the source for it and which license it is under. An example request is here. Make sure you check which packages have already been requested.
Because we want Free Software to reach as many people as possible and do not want to have 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) but on the WNPP package in Debian's bugtracker. If you file a needs-packaging bug, please link it to the Debian WNPP bug as well.
Packaging it yourself
You can follow the Packaging Guide directives.
NEW packages through Debian
Ubuntu regularly incorporates source packages from Debian, so it is encouraged to upload a package to Debian first to automatically have it in Ubuntu in due time. In order to have faster reviews, several teams have been set up to manage a given subset of packages. Some of them are:
More teams can be found here.
Ubuntu does virtually all package maintenance in teams. If you have a deep interest in a particular package and a desire to be the primary person responsible for it, you would likely be happier to get the package into Debian and maintain it there. Debian has a strong culture around individual package maintainers that is not present in Ubuntu. Additionally there are roughly an order of magnitude more Debian Developers than Ubuntu developers. It is quite difficult to get a new package into Ubuntu due to the shear 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 directly.
If you choose to do this, file an Intent to Package (ITP) bug on the WNPP package in Debian to let others know that you're working on it, 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.
Going through MOTU
Packages which are not in Ubuntu yet, require extra scrutiny and go through a special review process, before they get uploaded and get a final review by the archive admins. More information on the review process, including the criteria which will be applied, can be found on the Code Reviewers page. Developers are encouraged to examine their own packages using these guidelines prior to submitting them for review.
To receive higher quality bug reports write an apport hook for your package.
The MOTU team approval policy for new packages:
MOTUs can upload new packages directly to the archive. However they are greatly encouraged to have a new package reviewed prior to uploading. (cf. MOTU/Council/Meetings/2007-02-23)
The MOTU team uses the following workflow:
- When you start to work on a new package, assign the needs-packaging bug to yourself and set it In Progress (if there is no needs-packaging bug, file one).
Once you have an initial package, upload it to REVU, add the link to the package in REVU to the description of the bug. From this point on, no further Launchpad entries are made until the package is uploaded.
- Once the approved package is uploaded, the uploading MOTU will set the bug status to Fix Committed.
- When the package clears the NEW queue it will automatically be set to Fix Released (debian/changelog must close the needs-packaging bug). This is done with a bullet point that follows the format:
* Initial release (LP: #242910)
where "LP" refers to "Launchpad". See the Packaging Guide for more information on changelogs.
Feature Freeze is the latest approval date (July 21st 2011 for "Oneiric" aka Ubuntu 11.10): it is recommended to get things done in a couple weeks earlier, as getting approval may take some time. REVU days are planned through Feature Freeze, but the last days are likely only to grab packages that are really required to meet the feature goals for the release.
These are permitted, but REVU is the official location for getting packages reviewed.
The key policy point is that two MOTUs must advocate the package. Most MOTUs use REVU and it may be more difficult to get packages in alternative locations reviewed.
Also of interest
Always check if there is an ITP (intent to package) bug filed against the wnpp package in Debian. That means, somebody is already working on packaging the software for Debian. Join forces with them rather than reinventing the wheel.
mentors.debian.net, a website where people interested in getting their packages inside Debian can upload their packages. You need to browse the directories to find packages. ContributingToDebian has additional information on getting your work into Debian.
Debian's WebSVN It's possible that a package has been worked on for Debian but has a status of UNRELEASED. Check the appropriate directories that begin with "pkg" that your package may fall under. For example, game packages would be under "pkg-games".