SponsorshipProcess
Differences between revisions 6 and 79 (spanning 73 versions)
|
Size: 3437
Comment: Added link to draft procedure for processing the universe queue
|
← Revision 79 as of 2025-10-01 10:36:12 ⇥
Size: 665
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Sponsorship == | The contents of the Sponsorship page have been moved to the new Ubuntu Project documentation. |
| Line 3: | Line 3: |
| The sponsorship process is designed to allow prospective developers to have packages reviewed and uploaded. The review and uploading is performed by an official developer. Sponsorship provides a means of learning about Ubuntu development and lowers the entry barrier for contribution. | |
| Line 5: | Line 4: |
| 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 [:MOTU/Packages/REVU] process. | = Sponsorship = |
| Line 7: | Line 6: |
| == Creating a request == | For the general overview of the Sponsorship process, see [[https://documentation.ubuntu.com/project/how-ubuntu-is-made/processes/sponsorship/|the new Sponsorship process page]]. |
| Line 9: | Line 8: |
| MartinPitt wrote a little python script that reads a debdiff from stdin or a file, creates a bug report, and assigns it to the appropriate team: |
== Requesting Sponsorship == |
| Line 12: | Line 10: |
| * http://people.ubuntu.com/~pitti/scripts/requestsponsor This can only be used to diff changes to existing packages; if its a new package, the package should go through the [:MOTU/Packages/REVU] process. Requirements: * You need a deb-src line for the release you upload to (and must be up-to-apt-get-update, of course). * The environment variable DEBEMAIL must be set. * The script currently needs a local MTA. With this script, creating a request is as easy as: {{{ debdiff cupsys_1.2.1-0ubuntu1.dsc cupsys_1.2.1-0ubuntu2.dsc > diff [review diff] requestsponsor diff }}} The script will ask you for your GPG passphrase to sign the bug report. It automatically uses gnome-gpg if it is installed. You can see the currently pending requests at: * https://launchpad.net/people/ubuntu-main-sponsors/+subscribedbugs * https://launchpad.net/people/ubuntu-universe-sponsors/+subscribedbugs |
See the new location for details on [[https://documentation.ubuntu.com/project/contributors/find-a-sponsor/|how to find a sponsor]]. |
| Line 38: | Line 14: |
| Sponsorship is organized by two teams: * https://launchpad.net/people/ubuntu-main-sponsors * https://launchpad.net/people/ubuntu-universe-sponsors Any Ubuntu developer who is interested in acting as a sponsor is welcome to apply for membership in the appropriate team. Since Launchpad's email interface currently does not support attachments, requestsponsor puts the diffs inline into the bug report. Therefore it is inconvenient to grab a diff from the web interface. However, if you are subscribed to the team, you get the diff as (gpg-signed) mail. Save the email in raw text form, and do: {{{ apt-get source package cd package-* gpg -o - /path/to/saved/email | patch -Elp1 }}} You should check the signature verification result. If you are processing the universe sponsorship queue, please review the Draft [:MOTU/Sponsorship/SponsorsQueue:Procedure Documentation] Check the patch over carefully. If there are problems with it, provide constructive feedback to the bug so that it can be revised. A useful checklist for sponsoring may be found on Matt Palmers sponsorship checklist : http://people.debian.org/~mpalmer/sponsorship_checklist.html, though it is neither authoritative nor exhaustive. Exercise your own judgement when reviewing the package. A good review is non-trivial, but you will be responsible for what is uploaded, so be thorough. To upload, do a source only build of the package as normal, but make sure that your name is not in the `Maintainer:` or `Changed-By:` headers of the changes file. The easiest way to do this is to use the `-k` option to `dpkg-buildpackage` or `debsign` to sign it with your key (but leave it otherwise unchanged). Do not use the `-m` or `-e` flags to `dpkg-buildpackage`! |
See the new location for details on [[https://documentation.ubuntu.com/project/contributors/advanced/sponsor-an-upload/|how to sponsor an upload]]. |
| Line 67: | Line 17: |
| [:CategoryProcess] | [[CategoryProcess]] |
The contents of the Sponsorship page have been moved to the new Ubuntu Project documentation.
Sponsorship
For the general overview of the Sponsorship process, see the new Sponsorship process page.
Requesting Sponsorship
See the new location for details on how to find a sponsor.
Sponsoring
See the new location for details on how to sponsor an upload.
SponsorshipProcess (last edited 2025-10-01 10:36:12 by sally-makin)