On Thu, Sep 18, 2025 at 7:48 PM Doug Goldstein <cardoe@cardoe.com> wrote:

Hello,

It appears that skyline, both skyline-console and skyline-apiserver, have been broken from a test standpoint for a bit. Additionally the last patch from not one of the core members that has been merged was June 12th, which is also the last time a core member has commented on a patch not from the core members.

There has been a recent uptick in contributors coming from another organization and I would like to help see their contributions land. Some of these are fixes so that the tests actually pass as well as fixes for other bugs and new features. There have also been requests for backports to 2025.1. What do we need to get this work to start landing and make sure this project stays healthy?

fix for skyline-console tests: https://review.opendev.org/c/openstack/skyline-console/+/961092 fix for one of the two failing skyline-apiserver tests: https://review.opendev.org/c/openstack/skyline-console/+/961092 open skyline-apiserver changes: https://review.opendev.org/q/project:openstack/skyline-apiserver+status:open open skyline-console changes: https://review.opendev.org/q/project:openstack/skyline-console+status:open

Thank you for highlighting these patches. As we noted during numerous discussions on #openstack-tc, the underlying concern here is that the Skyline team is small, and apparently, they've had recent challenges to deal with alongside project/community maintenance. Besides that, over the past few years, the team hasn't grown despite the growth in project usage. I want to take the opportunity to urge the team to actively consider adding new core reviewers to help with some of the bandwidth concerns. In another thread [1], we were looking for volunteers that could help the team, and Skyline's PTL, Wu Wenxiang, has stated that they'd welcome any new contributors—but we have a chicken-and-egg problem where: - New contributors will need to establish their knowledge of the codebase and trust with the rest of the core team to be anointed as core reviewers. - The existing team doesn't seem to have the bandwidth or time to engage and are mired with challenges (firewalls, language and time zone barriers, little or no presence on OFTC's #openstack-skyline channel, no PTG discussions, etc.). I'd like to break this logjam. If these CI fixes can't be prioritized by the team, it affects code delivery processes in OpenStack, and the project is hostile towards new/interested contributors no matter the well-meaning intentions of the current core team. We'll be discussing this issue in the OpenStack TC's weekly meeting next week (Sept. 29th, 2025) [2]. I'm inviting the Skyline team to participate; if it's harder to meet in sync, please feel free to respond to this thread with your thoughts for resolution.

Thanks. — Doug

[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.... [2] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda