RFC: auto-generated packageset for Canonical OEM enablement metapackages

[Robie Basak]

On Tue, Aug 11, 2020 at 02:56:59PM +0100, Iain Lane wrote:
> The script - or the purpose that drives my wanting it - is quite an 
> important part of the proposal to me, because new source packages 
> (equivalent to newly-enabled lines of hardware) are going to be one of 
> the most frequent calls upon this OEM procedure, and I want that to be 
> able to be self-served by the team that is driving the enablement within 
> Canonical.

Understood. I only grasped the essence of this when rereading your
proposal earlier. Sorry I had not understood it during the meeting
yesterday.

> We can discuss how this should work in detail though, that's fine by me.  
> I'd be happy to write a script and then hand it over to the DMB to run 
> (on a timer), for example. I can imagine various safety guards 
> additional to that, like the script emailing its modifications to this 
> list.
> 
> Maybe we should take this thread in the direction of how to manage the 
> packages contained in set now.

Sure!

I like your proposal to have the script email its modifications to this
list. I assume also that the PPA would belong to the new Launchpad team?

We don't currently have anywhere for the DMB to run scripts on "bot
credentials". Do you have any suggestions for that?

I've also seen suggestions about handing over management of the
packageset to a different team such as ~ubuntu-sru or ~ubuntu-archive
(the latter makes more sense to me). AIUI, that can easily be done using
Launchpad's existing ACL mechanisms, though of course it would be
another level of surprising/edge case behaviour that we will need to
carefully document. Could this help with my "bot credentials" question?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/devel-permissions/attachments/20200811/daa023c4/attachment.sig>