On Wed, 4 Jan 2023 at 16:08, Jeremy Stanley fungi@yuggoth.org wrote:
On 2023-01-04 15:15:56 +0100 (+0100), Radosław Piliszek wrote: [...]
I have a cloud-related open source project that will be starting the upcoming months and we are looking for hosting. We will most likely decide to host our project on GitHub due to the popularity factor (both for consumers and developers; I am aware the mirroring would help for consumers but we prefer fewer bumps for contributors) [as a side note, this has not been decided yet and OpenDev+Gerrit is still in discussions; and yes, it hurts me that OpenDev and Gerrit are not nearly as popular as GitHub].
Some useful reading material to help sway wavering minds: https://GiveUpGitHub.org/
Thanks, this will surely come in handy now and then.
The question is whether we could utilise (with all possible acknowledgments) the Zuul deployment at OpenDev. If it is a technical matter, we will have some effort to help with those so it might be amendable. If it is the trust matter, then we will agree to trust the OpenDev<->GitHub boundary. However I am mostly not sure about your policy with this and I have not found a reference to this model of OpenDev usage.
The short answer is that OpenDev isn't "Zuul as a service" but rather an integrated code review and testing platform which is built from a combination of Gerrit, Zuul, and other components.
We run Zuul for the projects hosted in our Gerrit deployment. To that end, we sometimes perform advisory testing or ancillary artifact builds for externally-hosted dependencies of projects in OpenDev (whether those dependencies are in other Gerrits somewhere, or on services like github.com or gitlab.com), but we don't consume job configuration from them nor engage in any change gating there.
We explored this previously (four years ago), and the decision we reached on that matter was published here:
https://lists.openstack.org/pipermail/openstack-infra/2019-January/006269.ht...
The Kata "experiment" mentioned in that post was unsuccessful and terminated the next year as explained here:
https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/th...
I'm happy for us to collectively revisit the decision, but for me it comes down to whether our vision for OpenDev is "a la carte" SaaS or an integrated hosting platform, and how that informs investment of our limited resources.
Ack, I had a gut feeling this might be the case but I was still hoping for more options on my plate from that not-(yet?)-existent menu of OpenDev.
Thank you for your prompt answer. I shall be back with our decisions.
Radek -yoctozepto