On Tue, Nov 9, 2021 at 6:40 PM Emilien Macchi <emilien@redhat.com> wrote:
>
> On Wed, Nov 3, 2021 at 12:43 PM Jeremy Stanley <fungi@yuggoth.org> wrote:
> [...]
>
>> This was based on experiences trying to work with the Kata
>> community, and the "experiment" referenced in that mailing list post
>> eventually concluded with the removal of remaining Kata project
>> configuration when https://review.opendev.org/744687 merged
>> approximately 15 months ago.
>
>
> ack
>
> I haven't seen much pushback from moving to Gerrit, but pretty much all feedback I got was from folks who worked (is working) on OpenStack, so a bit biased in my opinion (myself included).
> Beside that, if we would move to opendev, I want to see some incentives in our roadmap, not just "move our project here because it's cool".
>
> Some ideas:
> * Consider it as a subproject from OpenStack SDK? Or part of a SIG?
My $0.01 opinion is to move the OpenStack SDK "project" to be a
generic "SDK" project, in which gophercloud could live. Mainly for a
point of contact perspective, but I think "whatever works" may be best
in the end.
I agree with Julia's comment here.
> * CI coverage for API regression testing (e.g. gophercloud/acceptance/compute running in Nova CI)
I strongly suspect it wouldn't be hard to convince ironic contributors
to do something similar for Ironic's CI.
++ I will be more than happy to help with this since I've contributed to gophercloud, and I've also helped them to add a job that runs Ironic so we could run acceptance tests.
> * Getting more exposure of the project and potentially more contributors
> * Consolidate the best practices in general, for contributions to the project, getting started, dev environments, improving CI jobs (current jobs use OpenLab zuul, with a fork of zuul jobs).
On a plus side, the official SDK list could be updated... This would
be kind of epic, actually.
++ I think this would be very good.
>
> Is there any concern would we have to discuss?
> --
> Emilien Macchi