SponsorshipProcess

Differences between revisions 44 and 45
Revision 44 as of 2009-09-22 01:51:27
Size: 4117
Editor: c-75-67-232-52
Comment:
Revision 45 as of 2009-12-11 14:58:40
Size: 4430
Editor: pool-71-114-235-234
Comment:
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
 * subscribe ubuntu-main-sponsors or ubuntu-universe-sponsors as appropriate (details below)  * subscribe ubuntu-main-sponsors, ubuntu-universe-sponsors or ubuntu-security-sponsors as appropriate (details below)
Line 47: Line 47:
 * https://launchpad.net/~ubuntu-security-sponsors
Line 55: Line 56:
 * https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-security-sponsors
Line 58: Line 60:
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. 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.
Line 63: Line 65:
If you are processing the universe sponsorship queue, please review the [[UbuntuDevelopment/CodeReviews]] or [[MOTU/Sponsorship/SponsorsQueue|MOTU Sponsorship Procedure Documentation]]. If you are processing the universe sponsorship queue, please review the [[UbuntuDevelopment/CodeReviews]], [[MOTU/Sponsorship/SponsorsQueue|MOTU Sponsorship Procedure Documentation]], or [[SecurityTeam/UpdateProcedures]].

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 (run what-patch in the source tree to find out), 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 (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 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.

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:

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; 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 Procedure Documentation, or SecurityTeam/UpdateProcedures.


CategoryProcess

SponsorshipProcess (last edited 2023-11-30 23:02:43 by bdrung)