On Thu, Oct 2 25 21:08, Robie Basak wrote:
> On Fri, Sep 26, 2025 at 11:21:56AM +0200, Robert Kratky wrote:
>> Following further discussion with the IS team, it's clear they cannot
>> dedicate cycles to adapting their LP -> GH sync solution for our
>> purposes right now.
>>
>> Therefore, I'd like to move forward with the previously suggested
>> (temporary) alternative: using individual GitHub account IDs in the
>> CODEOWNERS file. I realize this is a sub-optimal solution as it requires
>> a manual intervention to reflect any potential changes to team
>> composition.
>
> I'll ask again please that you implement something that notifies you
> when a relevant Launchpad team changes, so that you can then manually
> fix the GitHub side. This should take all of half an hour for someone
> familiar with the Launchpad API, so I don't think it's a big ask. This
> would avoid imposing a burden and friction on new team members who can't
> be expected to know what to do nor who to contact.
Ack. I submitted https://github.com/ubuntu/ubuntu-project-docs/pull/212
This adds a GH workflow (executed every night) to check for changes in
defined LP teams and submit an automated PR in case of detected changes
(details of the mechanics in the PR description).
I believe this does what you're asking for (until we have a really
automated solution).
>> However, in view of the fact that the 'Ubuntu Project' docs are now
>> being actively worked on (and this focus is planned to continue during
>> the 26.04 cycle), I'm convinced there'd be no danger of creating "second
>> class citizens" as Robie put it.
>
> I don't see how you can be convinced given that you said just above that
> you (collectively) cannot prioritise fixing this.
What I meant was that while I don't have leverage to force the IS team
to prioritize this, I know the Docs team (and Ubuntu Engineering) are
not going to abandon this documentation any time soon (and thus required
updates, including to CODEOWNERS, will be happening).
Robert
