SponsorshipProcess
Differences between revisions 48 and 79 (spanning 31 versions)
|
Size: 4551
Comment:
|
← 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: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| | The contents of the Sponsorship page have been moved to the new Ubuntu Project documentation. |
| Line 5: | Line 6: |
| 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. |
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 11: | Line 10: |
| * [[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]]). 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), 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 ([[PackagingGuide/Recipes/PackageUpdate|Howto Package Update]]) attach the `.diff.gz` file (and link to the new upstream source if necessary) * subscribe ubuntu-main-sponsors, ubuntu-universe-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. === New Packages === The process for getting NEW packages (packages which are not in Ubuntu at all yet) reviewed is explained at [[UbuntuDevelopment/NewPackages]]. |
See the new location for details on [[https://documentation.ubuntu.com/project/contributors/find-a-sponsor/|how to find a sponsor]]. |
| Line 44: | Line 14: |
| Sponsorship is organized by two teams: * https://launchpad.net/~ubuntu-main-sponsors * https://launchpad.net/~ubuntu-universe-sponsors * https://launchpad.net/~ubuntu-security-sponsors 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 * https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-security-sponsors Or combined at: * http://people.ubuntu.com/~dholbach/sponsoring/ 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; the `ubuntu-security-sponsors` team handles sponsorship of packages in the `security` pocket for all 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]], [[MOTU/Sponsorship/SponsorsQueue|MOTU Sponsorship Procedure Documentation]], or [[SecurityTeam/UpdateProcedures]]. |
See the new location for details on [[https://documentation.ubuntu.com/project/contributors/advanced/sponsor-an-upload/|how to sponsor an upload]]. |
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)