i feel like we need one, as well as a vision how everything should look like.
right now many discussion in the forum feel like buzzword bingo and people giving there 5 cents (no offense).
i guess it would make sense to identify people, who have the experience bootstrapping and operating such environments. so they can lead the discussion on what is needed, when it is needed, and how it should be done.
Whatever gets done, it needs to go into the code repos with justifications/decisions documented for future generations, so changes can be also justified similarly.
So yes, identify people, make them contributors to a roadmap github.io repo that publishes their decisions as a static page.
This is something Taylor and I are working on along with Rob.
We all have full time jobs and families, but I promise we’re working to get information out. It’s really sporadic right now and we’re doing all we can.
Let me know how/what to bring to the table to get this work party started. I have experience building packages (mock) and yum repo mirrors (also the orphaned i686 for 7) . Who is Team lead?
Myself and @tgmux are the “Infrastructure Managers” which is I believe what the official ish name is. Check out the github @ github.com/rocky-linux/infrastructure and the other repos to get involved! also come join on slack (links on rockylinux.org) if you haven’t already.
@schlitzered - Apologies for the shortness of this (quoted) message. It was not meant as a jibe at anyone in particular, but just to explain that things are moving quickly and there are conversations happening all over the place. I agree it’s not great… but there’s little that can be done. The project is experiencing such rapid growth.
I have experience managing and deploying infrastructure, builds, and automation from corporate jobs first at SoftLayer and now at … another major IBM acquisition.