Streamlining package set management

Iain Lane laney at
Sun Nov 6 17:48:40 UTC 2011

Hi there,

On Sat, Nov 05, 2011 at 11:43:51AM +0000, Mark Shuttleworth wrote:
> On 10/10/11 21:27, Iain Lane wrote:
> > An issue highlighted in the developer survey was that package set
> > management is a bit too bureaucratic. We just discussed this at the DMB
> > meeting[0] and I proposed some relatively minor changes to the process
> > that should streamline it a bit.
> >
> >   - As a matter of policy, each package set has a single uploader, which
> >     is a team. The DMB can either handle applications to the team or
> >     delegate to an appopriate council if one is set up.
> Can the upload processing system handle multiple uploaders/teams? If so,
> then the DMB also has the option of compositing teams. I say this
> because we've generally found it's better to have an ACL than to try and
> construct a new team every time you want to give a permission to two teams.

It can, but the DMB doesn't have permissions to manipulate the
uploaders, only the packages in sets for which it is the owner. This
is probably a Launchpad bug.

The team we are creating here is specifically an
~ubuntu-<packageset>-dev team with uploaders as members (i.e. a new team
which is specifically for managing upload to this packageset). Thus, it
is simple to add multiple teams or individuals as uploaders, and is easy
to manipulate and view through Launchpad's web UI.

> > […]   
> >   - Package additions are done by requesting on devel-permissions. Any
> >     DMB member will check against the criteria and add if it matches (or
> >     feed back if not).
> Similarly, can a package be in multiple package sets? It should be
> possible, and if so, the DMB might also want to check if adding the
> package to the packageset would impact on other teams, and ensure
> there's mutual awareness and coordination.

Awareness is a good idea, but we would expect teams to be able to work
together so probably would not block on this.

> >  - (Added since the meeting) Requests for package additions will be
> >     aged for three(?) days on devel-permissions, in order to allow time
> >     for DMB members to object. If there are objections that cannot be
> >     resolved over email then the matter will be taken to the next DMB
> >     meeting.
> >
> > TB & DMB, what do you think of this?
> +1 from me, apologies if that comes too late to be useful.

Thanks. No it does not — this came up at the TB in the week, and they
actually simply delegated the DMB authority to manage sets as they see


Iain Lane                                  [ iain at ]
Debian Developer                                   [ laney at ]
Ubuntu Developer                                   [ laney at ]
PhD student                                       [ ial at ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <>

More information about the technical-board mailing list