On Mon, Nov 21, 2016 at 8:01 PM, Barak Korren <bkorren(a)redhat.com> wrote:
Not because of anything with the project itself - I think it is
genuinely awesome, but because I expect a project that emerges out of
the incubation process to "look" like an oVirt project, by which I
1. Have the code in the oVirt Gerrit
2. Have tests and builds running on oVirt's CI system.
3. Have artefacts served from oVirt's mirrors.
4. Have bugs tracked in oVirt's bugzilla.
I have to agree on the above, moVirt can be even greater if he can use the
tools all other oVirt projects are using.
The oVirt infra team is here to help close that gap if needed, shouldn't
take too long if the maintainers are on board.
I think the project visibility will increase significantly once he's part
of the oVirt infra eco-system.
On 21 November 2016 at 19:07, Brian Proffitt <bproffit(a)redhat.com> wrote:
> The moVirt Project was initially accepted as an oVirt incubator project
> February 2015. It has been a successful subproject for quite some time
> it is well due for being accepted as a full oVirt project. I believe it
> appropriate to post a Call for Vote on the Devel and Board lists.
> A “healthy” project, as determined by the oVirt Board, can be found at
> Voting will be open until 1200 UTC Nov. 30, 2016. A net total of +7 votes
> should be received to formalize this project as an full oVirt project.
> Please use the following vote process:
> Yes, agree, or the action should be performed. On some issues, this vote
> must only be given after the voter has tested the action on their own
> Abstain, no opinion, or I am happy to let the other group members decide
> this issue. An abstention may have detrimental affects if too many people
> No, I veto this action. All vetos must include an explanation of why the
> veto is appropriate. A veto with no explanation is void.
> Thank you!
> Brian Proffitt
> Principal Community Analyst
> Open Source and Standards
> Devel mailing list
Devel mailing list
EMEA ENG Virtualization R&D
Red Hat Israel
irc: eedri (on #tlv #rhev-dev #rhev-integ)