Adding packages to desktop-common

Steve Langasek steve.langasek at
Thu Jun 21 00:30:39 UTC 2018

Hi Simon,

Thanks for writing this up.

Consistent with my previous comments, I don't think there should be an aging
period by default for additions to the desktop-common seed.  I would much
prefer to see a policy that consists of:

 - all additions to the seed should be publically announced.
 - all additions to the seed must be reverted in response to objections from
   any of the flavors, to allow a consensus to be reached.
 - additions of packages that substantively change the runtime behavior of
   the seed - such as added daemons - should be subjected to additional
   scrutiny, and in those cases there should be an aging period prior to
   committing the change.

I believe this preserves the rights of the flavors to veto changes that they
disagree with, while optimizing for the common case and preserving
development velocity when the changes are non-objectionable.

On Tue, Jun 19, 2018 at 09:27:51PM -0500, Simon Quigley wrote:
> Hello,
> I have drafted a proposal for adding packages to the desktop-common
> seed. This would be useful to ensure that everybody involved in shipping
> the contents of the seed agrees on what's in it.
> Here are the main points of this proposal:
>  - If a package is going to be included, an email should be sent to
> ubuntu-release with some information on what it is, why we need it, if
> there are any issues with it, and who is responsible for the package.
>  - An aging period of one week should be used to make sure there are no
> objections to a package's inclusion. If this needs to be waived, the
> person proposing its inclusion should state so on the mailing list, and
> feel free to proceed.
>  - If anyone opposes during or after the aging period, they should work
> out any concerns with the person proposing it and/or the people
> responsible for the package. If issues can't be worked out, we can't
> include it. (If the party opposing it goes MIA, the proposal should be
> re-sent to the mailing list.)
>  - If there's no objections, it can be added, provided a link to the
> proposal is in the commit message.
> Here is the full text of the proposal:
> Let me know if you have any questions, but otherwise I will be available
> during the next Technical Board meeting.
> Thanks.
> -- 
> Simon Quigley
> tsimonq2 at
> tsimonq2 on freenode and OFTC
> 5C7A BEA2 0F86 3045 9CC8
> C8B5 E27F 2CF8 458C 2FA4

> -- 
> Ubuntu-release mailing list
> Ubuntu-release at
> Modify settings or unsubscribe at:

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                         
slangasek at                                     vorlon at
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <>

More information about the Ubuntu-release mailing list