Role of the Sponsorship Queue

Daniel Chen seven.steps at
Wed Mar 3 02:04:18 GMT 2010

On Tue, Mar 2, 2010 at 8:50 AM, Daniel Holbach
<daniel.holbach at> wrote:
> The major disagreement is if the sponsorship queue is
>  - a general list of changes that need be reviewed (after having made
>   sure they are actual code changes, etc.) - basically a TOREVIEW list
>   for people who can upload
>  - an exclusive list of work done by new contributors who want to join
>   the Ubuntu Development team eventually - so a place where mentoring
>   happens

For simplicity's sake, I prefer the former: items in a sponsorship
queue should be immediately staged for upload.  Drive-by contributions
would better fit into a review queue.

> The distinction is important because "including contributed fixes" would
> require developers to check various lists for input and probably treat
> them differently ("can you update patch to do XYZ in a special way?" vs
> "I modified your patch and uploaded it."), etc.

Are we leaning toward removing the developer requirement for review,
e.g., REVU allows comments from non-Ubuntu uploaders?

More information about the ubuntu-devel mailing list