Endorsement
Note: This will be quite similar to the application of Guillaume as they work on the same topics in the same team since a similar time.
- Purely for sponsoring I had 24 packages working with Guillaume. OpenStack always releases quite close to all freezes and so there often is a rush to update the whole set of them. After many small discussions over a longer time before I did in Spring 2025 help to get this iteration into the Archive (19). Later in August/September there were 5 more, but those were next cycles upload and not yet the final versions. The model is get git based versions in early and replace them with final version once it exists.
- The quality of the prepared uploads was good, Myles and the OpenStack team have a well established model with repositories from which the changes are pre-reviewed and landed.
- I found a few small things - and while a the time not as responsive to fix them up as Guillaume that was mostly due to Myles and me not having the best timezone overlap AFAICS. I have not seen issues that I flagged repeated, and him asking when unsure - that is what I need to trust in people.
- I do trust Mylses and consider him qualified in regard to requested OpenStack PPU and would even consider him well informed for python package handling in general.
Areas of improvement and next steps
- I think this application (and the same for Guillaume) will help them to cross review and upload these stacks from now on making the OpenStack team independent again. What I expect there is to not become lazy or fast pathing uploads - finding and maintaining their own internal high bar is important as the “pressure → just upload” keeps lingering around every corner.
- After that I would hope he can here and there pick some cases outside of the OpenStack area every now and then to grow his skill and influence.
- Finally, I’m curious about that tooling you work on to track openstack uploads from start to finish and if it could be generic enough to use it for any package that went into SRU (I assume you cover unapproved → build → test → proposed migration). If you can make this usable for everyone
Other things
It didn’t fit in the sections above, but I wanted to mention that it was nice to see the quick evolution of Myles being thrown into the MIR team when James left and his journey from. WTH are we doing, to simple reviews sometimes a bit too mild, to quickly be a reliable reviewer holding up the quality bar of Ubuntu main to everyone. It has nothing to do with OpenStack PPU but he has seen enough quality and problem MIR discussions that he is aware of more sources of issues than he’d otherwise be - and that is great as well.