11:07 a.m.
On Tue, Jan 15, 2019 at 4:07 PM Sandro Bonazzola <sbonazzo(a)redhat.com wrote:
That's my pleasure. Great thanks for your help.
>>
[1]: https://github.com/imjoey/ovirt-engine-sdk-go
>> [2]: https://ovirt-jira.atlassian.net/browse/OVIRT-2460
>> [3]:
>>
https://www.ovirt.org/develop/release-management/releases/4.3/release-man...
>> _______________________________________________
>> Devel mailing list -- devel(a)ovirt.org
>> To unsubscribe send an email to devel-leave(a)ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/OCABRD46XI6...
> > --
> SANDRO BONAZZOLA
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
> Red Hat EMEA <https://www.redhat.com/ > sbonazzo(a)redhat.com
> <https://red.ht/sig
Il giorno mar 15 gen 2019 alle ore 03:09 Joey Ma <majunjiev(a)gmail.com> ha
scritto:
> Hi fellows,
> My name is Joey. Now I'm maintaining the project
ovirt-engine-sdk-go[1]
> which provides a Golang based sdk for oVirt engine REST API.
> During the past year, I was keeping in touch Ondra, Juan
and Martin. It's
> very appreciated that they helped me a lot to improve the sdk and also
> added me into the oVirt developer team[2] in github. Both Ondra and I think
> that the project is in great shape and ready for production use. :-)
> The original plan is to add the project into oVirt 4.3
official release.
> While according to the schedules[3] for 4.3, maybe there's no enough time
> to make it done due to some additional CI work.
> So if I may ask, is that possible to add the project as an
oVirt
> incubator project first, by transferring the project from my personal
> account to oVirt orgnization in github or gerrit? And then accept it as a
> full oVirt project after all the graduation requirements are matched.
> Thank you all in advance.
> Regards,
> Joey
Hi Joey, before submitting the
incubation request to the oVirt Board, I'm
reviewing the process:
https://ovirt.org/develop/projects/incubating-an-subproject.html
Your project integrates with oVirt API extending them for Go language
support so on this we are ok.
Are you committing to maintain the project supporting the release schedule
of oVirt project?
Yes, for sure.
License of the project is ASL 2.0 so it's in approved licenses.
Project has 4 releases and 1 maintainer so it classify as project in
developing stage. It's a small project so I believe that the classification
here is not really correct.
Yes, agreed.
Project has 5 contributors so the onboarding requires 3
"+1" votes.
My only concern is that last release is 4.0.6 and dates October 2018. I
would expect a 4.3.0 release aligned with oVirt Engine 4.3 API.
I use 4.0.x to represent that it's not an official release. Current 4.0.6
is keeping in sync with the official Java sdk 4.2.5 release. While maybe I
should have followed the Python sdk instead, which is already in 4.2.9 :-)
I think that if you can release such version, I can give my +1 to
onboarding this project in incubation state and propose it to the Board.
OK. I just released 4.3.0 a couple of minutes ago, which adopted the
metamodel-1.3.0 and model-4.3.20 for sdk generation.
In any case, thanks for your commitment improving oVirt, very nice job!