Hello, I think adding Paul is a good idea. However, the original idea of having Steve was to include a person handling releases so that they know what requires urgent backports.
How do you deal with that? Kind regards, Marta On Tue, May 19, 2026 at 1:27 PM Richard Purdie via lists.openembedded.org <[email protected]> wrote: > Hi, > > We realised that Steve Sakoman was listed as part of the the security > team but has retired and we believe we should find a replacement. The > YP TSC discussed this and would like to propose Paul Barker as a > candidate. > > Security reports and issues are on the rise and things are only going > to require more time as the CRA comes into effect and more issues are > found using new generations of AI. Paul is funded by YP, which gives us > more potential to be able to focus on issues and in the changing > landscape we feel that is an important to have represented on the team. > > I have to admit that we were initially confused about the process for > this however it it is documented on the wiki under "security team > appointment": > > https://wiki.yoctoproject.org/wiki/Security_private_reporting > > We're therefore asking for nominations and/or feedback, which can be to > me, or either of the TSCs. We'll set a deadline of one week for > candidates, until the 26th May. This should be enough time but if there > are any concerns on that, let us know. > > Cheers, > > Richard > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2353): https://lists.openembedded.org/g/openembedded-architecture/message/2353 Mute This Topic: https://lists.openembedded.org/mt/119388716/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
