SponsorshipProcess
|
Size: 4452
Comment: workflow updates
|
Size: 3838
Comment: drop requestsponsor
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Sponsorship == | = Sponsorship = |
| Line 6: | Line 6: |
== Creating a request == 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: * 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 Do not assign a bug to anyone if it needs sponsorship. (See Workflow, below.) |
|
| Line 44: | Line 14: |
| Do not assign a bug to anyone if it needs sponsorship. |
|
| Line 46: | Line 18: |
| 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://launchpad.net/people/ubuntu-main-sponsors/+subscribedbugs * https://launchpad.net/people/ubuntu-universe-sponsors/+subscribedbugs Or combined at: * http://people.ubuntu.com/~dholbach/sponsoring/ |
| Line 51: | Line 24: |
| Save the email in raw text form, and do: {{{ apt-get source package cd package-* gpg -o - /path/to/saved/email | patch -Elp1 }}} |
|
| Line 57: | Line 25: |
| You should check the signature verification result. | === New Packages === |
| Line 59: | Line 27: |
| If you are processing the universe sponsorship queue, please review the Draft [:MOTU/Sponsorship/SponsorsQueue:Procedure Documentation] | The process for getting NEW packages (packages which are not in Ubuntu at all yet) reviewed is explained at [:UbuntuDevelopment#NewPackages]. == Workflow for Review and Sponsorship == If you are processing the universe sponsorship queue, please review the [:MOTU/Sponsorship/SponsorsQueue:Procedure Documentation] or ["UbuntuDevelopment/CodeReviews"] |
| Line 67: | Line 39: |
| === Workflow === |
|
| Line 71: | Line 41: |
| or http://people.ubuntu.com/~dholbach/sponsoring/ |
|
| Line 72: | Line 44: |
| 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 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 whic 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). |
| Line 78: | Line 52: |
| You will need to be a member of ubuntu-main-sponsors in order to unsubscribe the team from the bug. === Proposed new approach using the tool ppaput === ''This process still might change.'' ["SponsorshipProcess/ppaput"] |
Sponsorship
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.
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.
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://launchpad.net/people/ubuntu-main-sponsors/+subscribedbugs
https://launchpad.net/people/ubuntu-universe-sponsors/+subscribedbugs
Or combined at:
New Packages
The process for getting NEW packages (packages which are not in Ubuntu at all yet) reviewed is explained at [:UbuntuDevelopment#NewPackages].
Workflow for Review and Sponsorship
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:
or
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 whic 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.
Proposed new approach using the tool ppaput
This process still might change.
["SponsorshipProcess/ppaput"]
SponsorshipProcess (last edited 2023-11-30 23:02:43 by bdrung)