<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 21, 2016 at 9:52 PM, Michal Skrivanek <span dir="ltr"><<a href="mailto:mskrivan@redhat.com" target="_blank">mskrivan@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
> On 21 Nov 2016, at 19:48, Vojtech Szocs <<a href="mailto:vszocs@redhat.com">vszocs@redhat.com</a>> wrote:<br>
><br>
><br>
><br>
> ----- Original Message -----<br>
>> From: "Eyal Edri" <<a href="mailto:eedri@redhat.com">eedri@redhat.com</a>><br>
>> To: "Vojtech Szocs" <<a href="mailto:vszocs@redhat.com">vszocs@redhat.com</a>><br>
>> Cc: "Barak Korren" <<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a>>, "devel" <<a href="mailto:devel@ovirt.org">devel@ovirt.org</a>>, "board" <<a href="mailto:board@ovirt.org">board@ovirt.org</a>>, "Michal Skrivanek"<br>
>> <<a href="mailto:mskrivan@redhat.com">mskrivan@redhat.com</a>><br>
>> Sent: Monday, November 21, 2016 7:23:44 PM<br>
>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project<br>
>><br>
>>> On Mon, Nov 21, 2016 at 8:17 PM, Vojtech Szocs <<a href="mailto:vszocs@redhat.com">vszocs@redhat.com</a>> wrote:<br>
>>><br>
>>><br>
>>><br>
>>> ----- Original Message -----<br>
>>>> From: "Barak Korren" <<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a>><br>
>>>> To: "Brian Proffitt" <<a href="mailto:bproffit@redhat.com">bproffit@redhat.com</a>><br>
>>>> Cc: "Michal Skrivanek" <<a href="mailto:mskrivan@redhat.com">mskrivan@redhat.com</a>>, <a href="mailto:board@ovirt.org">board@ovirt.org</a>, "devel" <<br>
>>> <a href="mailto:devel@ovirt.org">devel@ovirt.org</a>><br>
>>>> Sent: Monday, November 21, 2016 7:01:08 PM<br>
>>>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project<br>
>>>><br>
>>>> -1<br>
<br>
</span>I wonder if 8x +1 beats one -1 :)<br>
<span class=""><br>
>>>> Not because of anything with the project itself - I think it is<br>
>>>> genuinely awesome, but because I expect a project that emerges out of<br>
>>>> the incubation process to "look" like an oVirt project, by which I<br>
>>>> mean:<br>
>>>> 1. Have the code in the oVirt Gerrit<br>
<br>
</span>I wonder why that would be required. We experimented with other projects being off gerrit as well(e.g. cockpit-ovirt) and bug tracking out of redhat bugzilla and for certain projcts it makes sense. With more integration with other upstream projects I see us moving to github even more...<br>
<span class=""><br>
>>>> 2. Have tests and builds running on oVirt's CI system.<br>
<br>
</span>Can we run mobile testing on current infra?<br></blockquote><div><br></div><div>We won't know until we'll try right? fact is no one asked for it until now..</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
>>>> 3. Have artefacts served from oVirt's mirrors.<br>
<br>
</span>What artifacts? The final APK? Why? It's not a yum repo.<br></blockquote><div><br></div><div>The fact we're only hosting RPMs (not entirely right, we host images as well) doesn't mean we can't host anything else, we're actually working on support for building/deploying containers.</div><div>I'm sure we can find a way if the project owner wants it. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
>>>> 4. Have bugs tracked in oVirt's bugzilla.<br>
<br>
</span>No<br>
That should never be imposed on any new project. If someone loves slow outdated tools, so be it, but for new projects I again do not see us promoting it in future<br></blockquote><div><br></div><div>I agree this point is less relevant, and each project can handle his own tracking ( but again, if he will want to be released as part of oVirt and not independently, then I'm not sure he'll have a choice but to align )</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
>>><br>
>>> For 1 and 4, I feel that the benefit of allowing some projects to be hosted<br>
>>> on GitHub (attract & involve community through GitHub's public service)<br>
>>> does<br>
>>> out-weigh the rule of strict consistency (have everything in oVirt Gerrit).<br>
>>><br>
>>><br>
>> Any project in oVirt gerrit can be mirrored to GitHub, and most of them are<br>
>> ( see <a href="http://github.com/oVirt" rel="noreferrer" target="_blank">github.com/oVirt</a> )<br>
<br>
</span>We do mirror it IIRC (or it may have been cockpit-ovirt), it's just the other way around - the master copy is at github<br>
<span class=""><br>
>><br>
>><br>
>>> Although, not sure how hard would it be to modify oVirt CI system to allow<br>
>>> building GitHub hosted projects.<br>
>>><br>
>><br>
>> We are supporting it, Lago is an example of such project.<br>
>><br>
>><br>
>>><br>
>>> The guidelines should be clear about whether a project must be hosted via<br>
>>> oVirt Gerrit, whether it must have its bugs tracked via oVirt Bugzilla,<br>
>>> etc.<br>
>>><br>
>><br>
>> I don't think its a must, but its highly recommended IMO, and will help the<br>
>> project grow.<br>
>> Imagine this scenario:<br>
>><br>
>> the project grows and uses its own CI/testing frameworks and reaches a<br>
>> point it wants to join the oVirt eco-system,<br>
>> At that point it will be much harder to integrate it if at all, assuming<br>
>> the tools he's been using were not aligned with<br>
>> the tooling other projects are using.<br>
>><br>
>> Also - in terms of release process, its will be very hard to include it in<br>
>> an official oVirt release if he wishes to do so,<br>
>> as all oVirt projects are built in the current infra and shipped as a<br>
>> single repository.<br>
<br>
</span>You're missing the point it's not a yum repo.<br></blockquote><div><br></div><div>See my comments above on supporting other artifacts than rpms. </div><div><br></div><div>I think you're missing the point of the advantages such a project can get by joining, instead of managing its infra himself ( if it has any ),</div><div>It gets a massive CI/CD infrastructure already built and working, and will be able to do integration / testing with a real oVirt instance (using OST for e.g).</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
><br>
> Eyal, I agree with your points.<br>
><br>
> I just wanted to point out the possibility of hosting project's<br>
> sources on GitHub (point 1 from Barak's list). And as you wrote,<br>
> Lago is a good example of such project.<br>
><br>
> Using standard oVirt CI infra & tools (points 2 & 3 from Barak's<br>
> list) should be mandatory for all oVirt projects, to keep things<br>
> manageable from build/release perspective. Full agreement here.<br>
><br>
> As for bug tracking (point 4 from Barak's list), I see Lago using<br>
> GitHub's issue tracking interface, so this should be OK too..<br>
><br>
> In general, I'd say that moVirt maintainers should clearly voice<br>
> their vision on converging (or not) towards points 1,2,3,4 that<br>
> Barak has mentioned in his email.<br>
<br>
</span>I would say no. And that is fine<br>
<span class=""><br>
><br>
> For me, having source code & issues on GitHub, but using standard<br>
> oVirt CI infra & tools, is still acceptable for an oVirt project,<br>
> but it's just my own opinion.<br>
<br>
</span>I agree we can mix and match, though in this case I'm not sure how realistic is to run CI for an APK<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>I'm pretty sure that if we wanted to check that option, it will be possible even if by using emulators, but no one from the project has ever approached us so I can't really say anything before I see requirements.</div><div>I tend not to rule out anything I haven't verified possible before.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
><br>
>><br>
>><br>
>>><br>
>>>><br>
>>>> On 21 November 2016 at 19:07, Brian Proffitt <<a href="mailto:bproffit@redhat.com">bproffit@redhat.com</a>><br>
>>> wrote:<br>
>>>>> All:<br>
>>>>><br>
>>>>> The moVirt Project was initially accepted as an oVirt incubator<br>
>>> project in<br>
>>>>> February 2015. It has been a successful subproject for quite some time<br>
>>> and<br>
>>>>> it is well due for being accepted as a full oVirt project. I believe<br>
>>> it is<br>
>>>>> appropriate to post a Call for Vote on the Devel and Board lists.<br>
>>>>><br>
>>>>> <a href="http://www.ovirt.org/develop/projects/project-movirt/" rel="noreferrer" target="_blank">http://www.ovirt.org/develop/<wbr>projects/project-movirt/</a><br>
>>>>><br>
>>>>> A “healthy” project, as determined by the oVirt Board, can be found at<br>
>>>>> <a href="http://www.ovirt.org/develop/projects/adding-a-new-project/" rel="noreferrer" target="_blank">http://www.ovirt.org/develop/<wbr>projects/adding-a-new-project/</a><br>
>>>>><br>
>>>>> Voting will be open until 1200 UTC Nov. 30, 2016. A net total of +7<br>
>>> votes<br>
>>>>> should be received to formalize this project as an full oVirt project.<br>
>>>>> Please use the following vote process:<br>
>>>>><br>
>>>>> +1<br>
>>>>> Yes, agree, or the action should be performed. On some issues, this<br>
>>> vote<br>
>>>>> must only be given after the voter has tested the action on their own<br>
>>>>> system(s).<br>
>>>>><br>
>>>>> ±0<br>
>>>>> Abstain, no opinion, or I am happy to let the other group members<br>
>>> decide<br>
>>>>> this issue. An abstention may have detrimental affects if too many<br>
>>> people<br>
>>>>> abstain.<br>
>>>>><br>
>>>>> -1<br>
>>>>> No, I veto this action. All vetos must include an explanation of why<br>
>>> the<br>
>>>>> veto is appropriate. A veto with no explanation is void.<br>
>>>>><br>
>>>>> Thank you!<br>
>>>>><br>
>>>>> Brian Proffitt<br>
>>>>> Principal Community Analyst<br>
>>>>> Open Source and Standards<br>
>>>>> @TheTechScribe<br>
>>>>> 574.383.9BKP<br>
>>>>><br>
>>>>> ______________________________<wbr>_________________<br>
>>>>> Devel mailing list<br>
>>>>> <a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
>>>>> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br>
>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> Barak Korren<br>
>>>> <a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a><br>
>>>> RHEV-CI Team<br>
>>>> ______________________________<wbr>_________________<br>
>>>> Devel mailing list<br>
>>>> <a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
>>>> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br>
>>> ______________________________<wbr>_________________<br>
>>> Devel mailing list<br>
>>> <a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
>>> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br>
>>><br>
>>><br>
>>><br>
>><br>
>><br>
>> --<br>
>> Eyal Edri<br>
>> Associate Manager<br>
>> RHV DevOps<br>
>> EMEA ENG Virtualization R&D<br>
>> Red Hat Israel<br>
>><br>
>> phone: <a href="tel:%2B972-9-7692018" value="+97297692018">+972-9-7692018</a><br>
>> irc: eedri (on #tlv #rhev-dev #rhev-integ)<br>
>><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div></div></div>
</div></div>