On Mon, Apr 26, 2021 at 4:19 PM Dimitri John Ledkov <dimitri.led...@canonical.com> wrote: > > Hi, > > On Tue, Apr 20, 2021 at 8:29 PM Steve Langasek > <steve.langa...@canonical.com> wrote: > > > > [The ordinary membership of the ubuntu-archive team is handled internally by > > the archive team, and directly by the launchpad team admins; Cc:ing TB for > > awareness, but they can be dropped from Cc: going forward, modulo the > > separate discussion point Seb brings up.] > > > > On Tue, Apr 20, 2021 at 04:29:14PM +0100, Dimitri John Ledkov wrote: > > > Hi ~ubuntu-archive admins & techboard, > > > > > I would like to apply for ~ubuntu-archive team membership. Initially > > > scoped to exclusively working on & reviewing existing kernel related > > > packages. Many tasks to publish regular kernel updates require > > > privileges above of ~ubuntu-core-dev since binary packages are renamed > > > with every upload and signing is required to be performed. > > > > > I am well versed in binary package reviews, adding / removing > > > packages, submitting / reviewing / signing signed artefacts. I > > > understand and use most archive reports, and have contributed fixes to > > > them in the past. I will not exercise the ~ubuntu-archive powers on > > > any request that I myself generate. I shouldn't need any ssh access > > > either. > > > > Is this request in response to a perceived lack of throughput on kernel > > handling? A desire to move handling of the kernels to someone within the > > Kernel Team other than Andy, to free him up for other work? Is this > > request backed by the Kernel Team as a whole? > > The broad answer to all of the above is yes. > > > > > Note that there are other existing AA+SRU team members who are trained up on > > handling of kernel updates (Łukasz and myself). > > Whilst true, I believe there have been further changes that may not be > straight forward anymore. > > I'll follow up on that with a smaller audience. >
This week we are down to one person, and I am not sure if the kernel-signing-bot processes are being followed correctly. A person pulled out of PTO has geen assisting. > > > I don't know about Łukasz, > > but I have had zero requests for me to handle kernel updates for probably at > > least a year; they seem to all get handled on UK time before my start of > > work. So if there is a need to speed up handling of kernel updates, I'd > > like to understand first why the available resources are not being leveraged > > for this before adding more people to a privileged team. > > There is now an ever increasing amount of kernels and work that needs to be done, for longer time periods, for more ubuntu series and more kernels. Also given that devel releases are using production signing keys, and most kernels enable signing, it is now becoming impossible for me to assist in review and publication of devel series kernels as well. > > Also, I am generally opposed to giving people privileged team access on the > > basis that they only intend to use the access for a limited subset of that > > team's responsibilities, without a clear plan to also train that person up > > to handle all of the tasks. > > > > I'm happy to train to handle all the tasks of both AA & > ~canonical-signing & SRU. > Learning and handling all tasks is essential, especially during high workload periods, whilst still maintaining multiple eyeballs on things. And spreading the load to ensure we still have good throughput of reviews, and spare capacity for surge. For example, we are at the moment in a crunch period of certifying all jammy LTS derivative kernels. Continuing bootstrap of UC22. Whilst preparing Focal point release. Whilst still having regular ongoing work kernel, signing, and SRU work. Even if I am not yet trained or ready to take on all of the tasks, being able to handle review & signing for devel series and edge kernels, would free up a lot of capacity of more trained people to better handle things requiring even higher care - for example the current point release. > > None of this precludes you being made a member of the team, I just want us > > to be clear about rationale and the parameters under which such a thing > > should happen. How can I start with training on all the tasks to start onboarding into these teams? So far I am observing out of date tooling, with different members of the team doing things differently to achieve similar end results. I kind of want a hangout / life stream, review of kernels by apw with vorlon/sil2100/myself to see if we are all on the same page or not, for reviewing and signing devel & stable kernels for example. And how can we use any of the bots to help with UC grub/shim signing. Regards, Dimitri. -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
