The sponsorship process is designed to allow prospective developers to have packages reviewed and uploaded. Sponsorship provides a means of learning about Ubuntu development and lowers the entry barrier for contribution.

The process outlined here is aimed at dealing with incremental changes to existing packages within Ubuntu. (For mentoring on the creation of entirely new packages, please see the UbuntuDevelopment/NewPackages process.)

Requesting Sponsorship

To make use of Ubuntu merge proposals, follow these easy steps:

The traditional process involves:

  • File an Ubuntu bug in Launchpad or follow up on an existing one. If you think this might be a security update, please review the security team's "Issues that warrant a security update".

  • Attach your work
    • in the case of a patch (using the same upstream version), attach your suggested patch ("Submitting the fix"). For security updates, please see the security update packaging guidelines.

    • if the package uses a patch system (run what-patch in the source tree to find out), use edit-patch to comply with the choice of patch system, then make sure to follow the patch tagging guidelines. Package specific patch tags may be documented in debian/README.source.

    • review our general patch guidelines that give tips how to get the patch included upstream as well.

    • in the case of a upstream version update attach the .diff.gz file (and link to the new upstream source if necessary)

  • Subscribe ubuntu-sponsors or ubuntu-security-sponsors as appropriate (details below)

Packages maintained on Launchpad Code Hosting

Special attention is required if packages are maintained on Launchpad's Code Hosting. You might run into a message like this, when getting the source package:

$ apt-get source ubuntu-artwork
Reading package lists... Done
Building dependency tree       
Reading state information... Done
NOTICE: 'ubuntu-artwork' packaging is maintained in the 'Bzr' version control system at:
Please use:
bzr get https://code.launchpad.net/~ubuntu-art-pkg/ubuntu-artwork/ubuntu
to retrieve the latest (possible unreleased) updates to the package.

In these cases please consider registering a Merge proposal. It will make the life of the maintainers a lot easier.

Forwarding Patches Upstream

Review Debian/Bugs for more information.

New Packages

The process for getting NEW packages (packages which are not in Ubuntu at all yet) reviewed is explained at UbuntuDevelopment/NewPackages.

Getting Help

If you are unsure how to get a package sponsored, would like to add a new package or submit a patch, or have questions getting your package upstream into Debian, the Ubuntu Patch Pilots can help. To find out how to get in touch, please check the program documentation.

Generally asking for help in #ubuntu-motu or #ubuntu-devel is definitely on topic too. Smile :-)


To review Ubuntu merge proposals, check out these UDD instructions.

Sponsorship is organized into two teams:

Do not assign a bug to anyone if it needs sponsorship.

Any Ubuntu developer who is interested in acting as a sponsor is welcome to apply for membership in the appropriate team.

You can see the currently pending requests at:

Or combined at:

(occasionally it may be useful to check if there are non-/ubuntu bugs that fail to be noticed: https://bugs.launchpad.net/bugs/+bugs?field.subscriber=ubuntu-sponsors)

The ubuntu-sponsors team handles general sponsorship of packages in Ubuntu; the ubuntu-security-sponsors team handles sponsorship of packages in the security pocket for all components.

Workflow for Review and Sponsorship

If you are processing the universe sponsorship queue, please review the UbuntuDevelopment/CodeReviews, MOTU Sponsorship Procedure Documentation, or SecurityTeam/SponsorsQueue.


SponsorshipProcess (last edited 2023-11-30 23:02:43 by bdrung)