Open Stack

 ---- On Thu, 09 Dec 2021 09:57:27 -0600 Jean-Philippe Evrard <openstack at a.spamming.party> wrote ----
 > Hello folks,
 > 
 > The current governance requires the projects to follow certain guidelines [1], some of which are already covered by skyline. One of such guidelines is the PTI [2], which is detailed in more details for python in [3].
 > 
 > I am interested by the case of Skyline.
 > Skyline is a truely new project for OpenStack, bringing value to the ecosystem. It is forward looking.
 > Yes, it is different than existing projects.
 > Yes, it doesn't pass the pti for python [3].
 > 
 > If you check the PTI for golang [4], many of those commands could be easily wired on Skyline project using a Makefile (of course it wouldn't pass the dependency management part of that document, for which we require glide [5]... unmaintained since 2019, ahem... [6]).
 > 
 > So the question is: Is OpenStack ready to move forward and adapt to new kinds of packaging/software? If yes, let's modify the PTIs (or python PTI) to cover the case for skyline, and allow that team to move forward. 
 > It's not like it's doing something very different than some new python projects.
 > 
 > Yes, OpenStack is mature... I (simply) hope it's also a place for casual contributions, and where developers can have fun with tech. And yes, it won't please everyone from day one (especially distros), but I hope we can work this out together, rather than discard the project because it doesn't fit the mold.

Yes, those are the inconsistency we currently have in the Skyline project, but that is not what they will stick to. In Yoga PTG[1], the skyline team iterates through all these points and plans to
improve those and be consistent with the other OpenStack projects. They said they will
work on packaging, PTI, using Oslo code etc.

Boxiang Zhu mentioned the same in the governance patch also[2].

If they deny moving Skyline towards the OpenStack way of packing, testing, using Oslo, etc., we should consider whether to reject the OpenStack official project or modify our new
project application criteria. But this is not the case, and they agree to improve all those things.

Now we have more clear direction from them in the governance patch also, so I feel this is good
to go as an official project, and while they will be in OpenStack, we all can help them to
improve the things in OpenStack way.

Also, TC discussed in PTG the new concept of 'Tech pre-review' where we will monitor
such new projects' health, contribution, and direction going in the direction of OpenStack way. This
 'Tech pre-review'  is not up yet, so let's see how we define it.

[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025541.html
[2] https://review.opendev.org/c/openstack/governance/+/814037 
[3] https://etherpad.opendev.org/p/tc-yoga-ptg#L263

-gmann

 > 
 > Regards,
 > Jean-Philippe Evrard (evrardjp)
 > 
 > [1]: https://governance.openstack.org/tc/reference/new-projects-requirements.html
 > [2]: https://governance.openstack.org/tc/reference/project-testing-interface.html
 > [3]: https://governance.openstack.org/tc/reference/pti/python.html
 > [4]: https://governance.openstack.org/tc/reference/pti/golang.html
 > [5]: https://github.com/Masterminds/glide
 > [6]: https://travis-ci.org/github/Masterminds/glide
 > 
 >