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.)
To make use of Ubuntu merge proposals, follow these easy steps:
The traditional process involves:
- Attach your work
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: https://code.launchpad.net/~ubuntu-art-pkg/ubuntu-artwork/ubuntu 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.
The process for getting NEW packages (packages which are not in Ubuntu at all yet) reviewed is explained at UbuntuDevelopment/NewPackages.
To be set up during Natty cycle.
Inspired by Bazaar's Patch Pilot programme there will be patch pilots in #ubuntu-devel who can help you get your patch accepted. Check the topic to see who's on duty.
- Please respect that these people might have a few other patches in their queue already.
- The package you have a question have about might not necessarily be part of the patch pilot's area of expertise. They will still try to help you get your fix in and probably get you in touch with the 'right' people.
Generally asking for help in #ubuntu-motu or #ubuntu-devel is definitely on topic too.
The general difference between sponsors and patch pilots is:
- sponsors will pick items from the queue based on their preference (be it urgency or area of expertise, etc.)
patch pilots make themselves available on IRC (indicated in the topic in #ubuntu-devel)
patch pilots follow these instructions to get patches ready, not necessarily upload them, but do their best to get the item reviewed and it to a state where it can be included
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.