SponsorshipProcess
|
Size: 5182
Comment:
|
← Revision 77 as of 2023-11-30 23:02:43 ⇥
Size: 5536
Comment: Sponsoring reports moved to http://sponsoring-reports.ubuntu.com/
|
| Deletions are marked like this. | Additions are marked like this. |
| 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. | 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. |
| Line 7: | Line 7: |
| 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. | 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.) |
| Line 11: | Line 11: |
| * [[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 |
To make use of Ubuntu merge proposals, follow these easy steps: * [[http://packaging.ubuntu.com/html/getting-set-up.html|set up the tools]] * [[http://packaging.ubuntu.com/html/udd-intro.html|get the source]] * [[http://packaging.ubuntu.com/html/fixing-a-bug.html#work-on-a-fix|work on the package]] * [[DistributedDevelopment/Documentation/SeekingSponsorship|seek sponsorship]] The traditional process involves: * [[https://bugs.launchpad.net/ubuntu/+filebug|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 "[[SecurityTeam/UpdateProcedures#Issues%20that%20warrant%20a%20security%20update|Issues that warrant a security update]]". * Attach your work * in the case of a patch (using the same upstream version), attach your suggested patch ([[https://packaging.ubuntu.com/html/fixing-a-bug.html#submitting-the-fix-and-getting-it-included|"Submitting the fix"]]). For security updates, please see the [[SecurityTeam/UpdatePreparation#Packaging|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 [[UbuntuDevelopment/PatchTaggingGuidelines|patch tagging guidelines]]. Package specific patch tags may be documented in `debian/README.source`. * review [[UbuntuDevelopment/Patches|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 [[https://help.launchpad.net/BranchMergeProposals|Merge proposal]]. It will make the life of the maintainers a lot easier. === Forwarding Patches Upstream === Review [[Debian/Bugs]] for more information. |
| Line 20: | Line 50: |
| The process for getting NEW packages (packages which are not in Ubuntu at all yet) reviewed is explained at [[UbuntuDevelopment#NewPackages]]. | 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 [[https://ubuntu.com/community/contribute/ubuntu-development/ubuntu-patch-pilots|program documentation]]. Generally asking for help in `#ubuntu-motu` or `#ubuntu-devel` is definitely on topic too. :-) |
| Line 24: | Line 61: |
| '''To review Ubuntu merge proposals, check out [[http://packaging.ubuntu.com/html/udd-uploading.html | these UDD instructions]]'''. | |
| Line 25: | Line 63: |
| Sponsorship is organized by two teams: * https://launchpad.net/~ubuntu-main-sponsors * https://launchpad.net/~ubuntu-universe-sponsors |
Sponsorship is organized into two teams: * https://launchpad.net/~ubuntu-sponsors * https://launchpad.net/~ubuntu-security-sponsors |
| Line 34: | Line 72: |
| * https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-main-sponsors * https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-universe-sponsors |
* https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-sponsors * https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-sponsors&field.component=3&field.component=4 * https://bugs.launchpad.net/~ubuntu-security-sponsors/+subscribedbugs |
| Line 37: | Line 76: |
| * http://people.ubuntu.com/~dholbach/sponsoring/ | * '''http://sponsoring-reports.ubuntu.com/''' |
| Line 39: | Line 78: |
| 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. | ~-(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. |
| Line 44: | Line 85: |
| If you are processing the universe sponsorship queue, please review the [[MOTU/Sponsorship/SponsorsQueue|Procedure Documentation]] or [[UbuntuDevelopment/CodeReviews]] 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`! To find changes for main that need sponsoring, see the list of bugs: https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-main-sponsors or http://people.ubuntu.com/~dholbach/sponsoring/ When you start to work on such a bug, assign it to yourself. (If you find a bug on the list above already assigned to someone other than a member of ubuntu-core-dev, that is a mistake. You should probably deassign them and point them at this wiki page.) When you have a solution, i. e. an updated source package which fixes the problem, create a `debdiff` to the current Ubuntu version and attach it to the bug (don't forget to set the "patch" flag for the attachment). When you have finished working on the bug by uploading, set the state to Fix Released as usual, and unsubscribe ubuntu-main-sponsors. If the bug is a sync request, you can finish it by approving the sync. Edit the Description if necessary so that it is a proper sync request. Write a comment into the bug saying that you approve the sync, and subscribe ubuntu-archive. You should unsubscribe ubuntu-main-sponsors at this point. Leave the bug assigned to yourself in case ubuntu-archive have any questions. You will need to be a member of ubuntu-main-sponsors in order to unsubscribe the team from the bug. |
If you are processing the universe sponsorship queue, please review the [[UbuntuDevelopment/CodeReviews]], [[MOTU/Sponsorship/SponsorsQueue|MOTU Sponsorship Procedure Documentation]], or [[SecurityTeam/SponsorsQueue]]. |
Sponsorship
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: 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.
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. 
Sponsoring
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:
https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-sponsors
https://bugs.launchpad.net/~ubuntu-security-sponsors/+subscribedbugs
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)