SponsorshipProcess
|
Size: 1993
Comment: create
|
Size: 3031
Comment: moving "how to sponsor" documentation to UbuntuDevelopment/CodeReviews
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Sponsorship == | ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
| Line 3: | Line 3: |
| The sponsorship process is designed to allow prospective developers to have packages reviewed and uploaded by an official developer to provide a means of learning about Ubuntu development and a low barrier to entry for contribution. | = Sponsorship = |
| Line 5: | Line 5: |
| The sponsorship process is designed to allow prospective developers to have packages reviewed and uploaded. The review and uploading is performed by a Ubuntu Developer (MOTU) or Ubuntu Core Developer (core-dev). Sponsorship provides a means of learning about Ubuntu development and lowers the entry barrier for contribution. | |
| Line 6: | Line 7: |
| == Creating a request == | 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. |
| Line 8: | Line 9: |
| 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 11: | Line 11: |
| * http://people.ubuntu.com/~pitti/scripts/requestsponsor | * [[https://bugs.launchpad.net/ubuntu/+filebug|File an Ubuntu bug in Launchpad]] or follow up on an existing one and * attach your work * in the case of a patch (using the same upstream version), attach your suggested patch ([[PackagingGuide/Recipes/Debdiff|Howto Debdiff]]) * if the package uses a patch system, then make sure to follow the [[UbuntuDevelopment/PatchTaggingGuidelines|patch tagging guidelines]] * in the case of a upstream version update ([[PackagingGuide/Recipes/PackageUpdate|Howto Package Update]]) attach the `.diff.gz` file (and link to the new upstream source if necessary) * subscribe ubuntu-main-sponsors or ubuntu-universe-sponsors as appropriate (details below) and request sponsorship |
| Line 13: | Line 18: |
| Requirements: | === New Packages === |
| Line 15: | Line 20: |
| * 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. |
The process for getting NEW packages (packages which are not in Ubuntu at all yet) reviewed is explained at [[UbuntuDevelopment/NewPackages]]. |
| Line 19: | Line 22: |
| 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 |
|
| Line 36: | Line 26: |
| * https://launchpad.net/~ubuntu-main-sponsors * https://launchpad.net/~ubuntu-universe-sponsors |
|
| Line 37: | Line 29: |
| * https://launchpad.net/people/ubuntu-main-sponsors * https://launchpad.net/people/ubuntu-universe-sponsors |
Do not assign a bug to anyone if it needs sponsorship. |
| Line 42: | Line 33: |
| 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. |
You can see the currently pending requests at: * https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-main-sponsors * https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-universe-sponsors Or combined at: * http://people.ubuntu.com/~dholbach/sponsoring/ |
| Line 47: | Line 39: |
| Save the email in raw text form, and do: {{{ apt-get source package cd package-* gpg -o - /path/to/saved/email | patch -Elp1 }}} |
The `ubuntu-main-sponsors` team handles sponsorship of packages in the `main` and `restricted` components; the `ubuntu-universe-sponsors` team handles sponsorship of packages in the `universe` and `multiverse` components. To find out which component a source package is in, visit `https://launchpad.net/ubuntu/+source/SOURCE-PACKAGE-NAME` and look at the row for the appropriate release in the "Published versions and upstream associations" table. The component name is in the third column. |
| Line 53: | Line 41: |
| You should check the signature verification result. | == Workflow for Review and Sponsorship == If you are processing the universe sponsorship queue, please review the [[UbuntuDevelopment/CodeReviews]] or [[MOTU/Sponsorship/SponsorsQueue|MOTU Sponsorship Procedure Documentation]]. ---- [[CategoryProcess]] |
Sponsorship
The sponsorship process is designed to allow prospective developers to have packages reviewed and uploaded. The review and uploading is performed by a Ubuntu Developer (MOTU) or Ubuntu Core Developer (core-dev). 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 MOTU/Packages/REVU process.
Requesting Sponsorship
File an Ubuntu bug in Launchpad or follow up on an existing one and
- attach your work
in the case of a patch (using the same upstream version), attach your suggested patch (Howto Debdiff)
if the package uses a patch system, then make sure to follow the patch tagging guidelines
in the case of a upstream version update (Howto Package Update) attach the .diff.gz file (and link to the new upstream source if necessary)
- subscribe ubuntu-main-sponsors or ubuntu-universe-sponsors as appropriate (details below) and request sponsorship
New Packages
The process for getting NEW packages (packages which are not in Ubuntu at all yet) reviewed is explained at UbuntuDevelopment/NewPackages.
Sponsoring
Sponsorship is organized by 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:
https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-main-sponsors
https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-universe-sponsors
Or combined at:
The ubuntu-main-sponsors team handles sponsorship of packages in the main and restricted components; the ubuntu-universe-sponsors team handles sponsorship of packages in the universe and multiverse components. To find out which component a source package is in, visit https://launchpad.net/ubuntu/+source/SOURCE-PACKAGE-NAME and look at the row for the appropriate release in the "Published versions and upstream associations" table. The component name is in the third column.
Workflow for Review and Sponsorship
If you are processing the universe sponsorship queue, please review the UbuntuDevelopment/CodeReviews or MOTU Sponsorship Procedure Documentation.
SponsorshipProcess (last edited 2023-11-30 23:02:43 by bdrung)