Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-29 Thread Eldad Marciano 
+1

On Tue, Nov 29, 2016 at 2:23 PM, Sandro Bonazzola <sbona...@redhat.com>
wrote:

> Brian, Board, I think we have enough +1.
>
> On Tue, Nov 22, 2016 at 10:02 AM, Jakub Niedermertl <jnied...@redhat.com>
> wrote:
>
>> +1
>>
>> - Original Message -
>> > From: "Roman Mohr" <rm...@redhat.com>
>> > To: "Brian Proffitt" <bprof...@redhat.com>
>> > Cc: "Michal Skrivanek" <mskri...@redhat.com>, bo...@ovirt.org, "devel"
>> <devel@ovirt.org>
>> > Sent: Tuesday, November 22, 2016 9:30:23 AM
>> > Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt
>> Project
>> >
>> > +1
>> >
>> > On Mon, Nov 21, 2016 at 6:07 PM, Brian Proffitt < bprof...@redhat.com >
>> > wrote:
>> >
>> >
>> >
>> > All:
>> >
>> > The moVirt Project was initially accepted as an oVirt incubator project
>> in
>> > February 2015. It has been a successful subproject for quite some time
>> and
>> > it is well due for being accepted as a full oVirt project. I believe it
>> is
>> > appropriate to post a Call for Vote on the Devel and Board lists.
>> >
>> > http://www.ovirt.org/develop/projects/project-movirt/
>> >
>> > A “healthy” project, as determined by the oVirt Board, can be found at
>> > http://www.ovirt.org/develop/projects/adding-a-new-project/
>> >
>> > 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:
>> >
>> > +1
>> > 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
>> system(s).
>> >
>> > ±0
>> > 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
>> > abstain.
>> >
>> > -1
>> > 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
>> > @TheTechScribe
>> > 574.383.9BKP
>> >
>> > ___
>> > Devel mailing list
>> > Devel@ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/devel
>> >
>> >
>> > ___
>> > Devel mailing list
>> > Devel@ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/devel
>> ___
>> Devel mailing list
>> Devel@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>



-- 
-Eldad
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-22 Thread Piotr Kliczewski 
+1

On Tue, Nov 22, 2016 at 9:18 AM, Vinzenz Feenstra <vfeen...@redhat.com> wrote:
>
> On Nov 22, 2016, at 9:12 AM, Tomas Jelinek <tjeli...@redhat.com> wrote:
>
>
>
> - Original Message -
>
> From: "Nir Soffer" <nsof...@redhat.com>
> To: "Michal Skrivanek" <mskri...@redhat.com>
> Cc: "devel" <devel@ovirt.org>, "board" <bo...@ovirt.org>
> Sent: Monday, November 21, 2016 10:00:05 PM
> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
>
> On Mon, Nov 21, 2016 at 9:52 PM, Michal Skrivanek <mskri...@redhat.com>
> wrote:
>
>
>
> On 21 Nov 2016, at 19:48, Vojtech Szocs <vsz...@redhat.com> wrote:
>
>
>
> - Original Message -
>
> From: "Eyal Edri" <ee...@redhat.com>
> To: "Vojtech Szocs" <vsz...@redhat.com>
> Cc: "Barak Korren" <bkor...@redhat.com>, "devel" <devel@ovirt.org>,
> "board" <bo...@ovirt.org>, "Michal Skrivanek"
> <mskri...@redhat.com>
> Sent: Monday, November 21, 2016 7:23:44 PM
> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
>
> On Mon, Nov 21, 2016 at 8:17 PM, Vojtech Szocs <vsz...@redhat.com>
> wrote:
>
>
>
> - Original Message -
>
> From: "Barak Korren" <bkor...@redhat.com>
> To: "Brian Proffitt" <bprof...@redhat.com>
> Cc: "Michal Skrivanek" <mskri...@redhat.com>, bo...@ovirt.org, "devel"
> <
>
> devel@ovirt.org>
>
> Sent: Monday, November 21, 2016 7:01:08 PM
> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt
> Project
>
> -1
>
>
> I wonder if 8x +1 beats one -1 :)
>
>
> 9X :-)
>
>
> adding my obviously biased +1, so not sure if it counts...
>
>
> +1 for including the project as is.
>
> If someone wants to run the project test or build it, the right way
> to vote is by sending patches and making it happen.
>
> I think we should get out of our gerrit silo and move all ovirt
> projects to github. This will give ovirt much better visibility.
>
> Here are some projects developed on github:
> https://github.com/systemd/systemd
> https://github.com/rust-lang/rust/
> https://github.com/kubernetes/kubernetes
>
>
> I would add also https://github.com/ManageIQ/ which we as oVirt devels are
> contributing to regularly.
>
>
> https://github.com/cockpit-project/cockpit
> https://github.com/OpenShift
>
>
>
>
> Nir
>
>
> 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
> mean:
> 1. Have the code in the oVirt Gerrit
>
>
> 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...
>
> 2. Have tests and builds running on oVirt's CI system.
>
>
> Can we run mobile testing on current infra?
>
>
> We are using travis for this. Our complete config file is:
> language: android
> script: "./gradlew build"
> android:
>  components:
>- platforms-tools
>- tools
>- build-tools-21.1.2
>- android-21
>
> We don't have any additional tooling developed or anything like that.
> If we will start thinking about doing some custom/complicated stuff, we
> may consider moving to ovirt's CI. Currently, I don't see a reason.
>
>
> 3. Have artefacts served from oVirt's mirrors.
>
>
> What artifacts? The final APK? Why? It's not a yum repo.
>
>
> We need to serve them using google play store so it will reach the users
> easily.
> We could serve also RPM packaged APKs
> or even create our alternative "something like play store" but Im not sure
> what benefits
> it would bring us.
>
>
> 4. Have bugs tracked in oVirt's bugzilla.
>
>
> No
> 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
>
>
> +1
>
> Well, long story short, moVirt is a simple small tool developed by a very
> small team
> and occasionally contributed by community (mostly as outreachy interns or
> intern candidates).
> It needs a swift, stable, minimal and well known tooling around which does
> exactly what we need.
> The current comb

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-22 Thread Vinzenz Feenstra 

> On Nov 22, 2016, at 9:12 AM, Tomas Jelinek <tjeli...@redhat.com> wrote:
> 
> 
> 
> - Original Message -
>> From: "Nir Soffer" <nsof...@redhat.com>
>> To: "Michal Skrivanek" <mskri...@redhat.com>
>> Cc: "devel" <devel@ovirt.org>, "board" <bo...@ovirt.org>
>> Sent: Monday, November 21, 2016 10:00:05 PM
>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
>> 
>> On Mon, Nov 21, 2016 at 9:52 PM, Michal Skrivanek <mskri...@redhat.com>
>> wrote:
>>> 
>>> 
>>>> On 21 Nov 2016, at 19:48, Vojtech Szocs <vsz...@redhat.com> wrote:
>>>> 
>>>> 
>>>> 
>>>> - Original Message -
>>>>> From: "Eyal Edri" <ee...@redhat.com>
>>>>> To: "Vojtech Szocs" <vsz...@redhat.com>
>>>>> Cc: "Barak Korren" <bkor...@redhat.com>, "devel" <devel@ovirt.org>,
>>>>> "board" <bo...@ovirt.org>, "Michal Skrivanek"
>>>>> <mskri...@redhat.com>
>>>>> Sent: Monday, November 21, 2016 7:23:44 PM
>>>>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
>>>>> 
>>>>>> On Mon, Nov 21, 2016 at 8:17 PM, Vojtech Szocs <vsz...@redhat.com>
>>>>>> wrote:
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> - Original Message -
>>>>>>> From: "Barak Korren" <bkor...@redhat.com>
>>>>>>> To: "Brian Proffitt" <bprof...@redhat.com>
>>>>>>> Cc: "Michal Skrivanek" <mskri...@redhat.com>, bo...@ovirt.org, "devel"
>>>>>>> <
>>>>>> devel@ovirt.org>
>>>>>>> Sent: Monday, November 21, 2016 7:01:08 PM
>>>>>>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt
>>>>>>> Project
>>>>>>> 
>>>>>>> -1
>>> 
>>> I wonder if 8x +1 beats one -1 :)
>> 
>> 9X :-)
> 
> adding my obviously biased +1, so not sure if it counts...
> 
>> 
>> +1 for including the project as is.
>> 
>> If someone wants to run the project test or build it, the right way
>> to vote is by sending patches and making it happen.
>> 
>> I think we should get out of our gerrit silo and move all ovirt
>> projects to github. This will give ovirt much better visibility.
>> 
>> Here are some projects developed on github:
>> https://github.com/systemd/systemd <https://github.com/systemd/systemd>
>> https://github.com/rust-lang/rust/ <https://github.com/rust-lang/rust/>
>> https://github.com/kubernetes/kubernetes 
>> <https://github.com/kubernetes/kubernetes>
> 
> I would add also https://github.com/ManageIQ/ <https://github.com/ManageIQ/> 
> which we as oVirt devels are contributing to regularly.

https://github.com/cockpit-project/cockpit 
<https://github.com/cockpit-project/cockpit>
https://github.com/OpenShift <https://github.com/OpenShift>


> 
>> 
>> Nir
>> 
>>> 
>>>>>>> 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
>>>>>>> mean:
>>>>>>> 1. Have the code in the oVirt Gerrit
>>> 
>>> 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...
>>> 
>>>>>>> 2. Have tests and builds running on oVirt's CI system.
>>> 
>>> Can we run mobile testing on current infra?
> 
> We are using travis for this. Our complete config file is:
> language: android
> script: "./gradlew build"
> android:
>  components:
>- platforms-tools
>- tools
>- build-tools-21.1.2
>- android-21
> 
> We don't have any additional tooling developed or anything like that.
> If we will start thinking about doing some custom/complicated stuff, we
> may consider moving to ovirt's CI. Currently, I don't see a r

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-22 Thread Tomas Jelinek 


- Original Message -
> From: "Nir Soffer" <nsof...@redhat.com>
> To: "Michal Skrivanek" <mskri...@redhat.com>
> Cc: "devel" <devel@ovirt.org>, "board" <bo...@ovirt.org>
> Sent: Monday, November 21, 2016 10:00:05 PM
> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
> 
> On Mon, Nov 21, 2016 at 9:52 PM, Michal Skrivanek <mskri...@redhat.com>
> wrote:
> >
> >
> >> On 21 Nov 2016, at 19:48, Vojtech Szocs <vsz...@redhat.com> wrote:
> >>
> >>
> >>
> >> - Original Message -
> >>> From: "Eyal Edri" <ee...@redhat.com>
> >>> To: "Vojtech Szocs" <vsz...@redhat.com>
> >>> Cc: "Barak Korren" <bkor...@redhat.com>, "devel" <devel@ovirt.org>,
> >>> "board" <bo...@ovirt.org>, "Michal Skrivanek"
> >>> <mskri...@redhat.com>
> >>> Sent: Monday, November 21, 2016 7:23:44 PM
> >>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
> >>>
> >>>> On Mon, Nov 21, 2016 at 8:17 PM, Vojtech Szocs <vsz...@redhat.com>
> >>>> wrote:
> >>>>
> >>>>
> >>>>
> >>>> - Original Message -
> >>>>> From: "Barak Korren" <bkor...@redhat.com>
> >>>>> To: "Brian Proffitt" <bprof...@redhat.com>
> >>>>> Cc: "Michal Skrivanek" <mskri...@redhat.com>, bo...@ovirt.org, "devel"
> >>>>> <
> >>>> devel@ovirt.org>
> >>>>> Sent: Monday, November 21, 2016 7:01:08 PM
> >>>>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt
> >>>>> Project
> >>>>>
> >>>>> -1
> >
> > I wonder if 8x +1 beats one -1 :)
> 
> 9X :-)

adding my obviously biased +1, so not sure if it counts...

> 
> +1 for including the project as is.
> 
> If someone wants to run the project test or build it, the right way
> to vote is by sending patches and making it happen.
> 
> I think we should get out of our gerrit silo and move all ovirt
> projects to github. This will give ovirt much better visibility.
> 
> Here are some projects developed on github:
> https://github.com/systemd/systemd
> https://github.com/rust-lang/rust/
> https://github.com/kubernetes/kubernetes

I would add also https://github.com/ManageIQ/ which we as oVirt devels are 
contributing to regularly.

> 
> Nir
> 
> >
> >>>>> 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
> >>>>> mean:
> >>>>> 1. Have the code in the oVirt Gerrit
> >
> > 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...
> >
> >>>>> 2. Have tests and builds running on oVirt's CI system.
> >
> > Can we run mobile testing on current infra?

We are using travis for this. Our complete config file is:
language: android
script: "./gradlew build"
android:
  components:
- platforms-tools
- tools
- build-tools-21.1.2
- android-21

We don't have any additional tooling developed or anything like that.
If we will start thinking about doing some custom/complicated stuff, we
may consider moving to ovirt's CI. Currently, I don't see a reason.

> >
> >>>>> 3. Have artefacts served from oVirt's mirrors.
> >
> > What artifacts? The final APK? Why? It's not a yum repo.

We need to serve them using google play store so it will reach the users 
easily. 
We could serve also RPM packaged APKs 
or even create our alternative "something like play store" but Im not sure what 
benefits 
it would bring us.

> >
> >>>>> 4. Have bugs tracked in oVirt's bugzilla.
> >
> > No
> > 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

+1

Well, long story short, moVirt is a simple small tool developed by a very small 
team
and occasionall

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-22 Thread Vinzenz Feenstra 
+1

> On Nov 21, 2016, at 6:07 PM, Brian Proffitt  wrote:
> 
> All:
> 
> The moVirt Project was initially accepted as an oVirt incubator project in 
> February 2015. It has been a successful subproject for quite some time and it 
> is well due for being accepted as a full oVirt project. I believe it is 
> appropriate to post a Call for Vote on the Devel and Board lists. 
> 
> http://www.ovirt.org/develop/projects/project-movirt/ 
> 
> 
> A “healthy” project, as determined by the oVirt Board, can be found at 
> http://www.ovirt.org/develop/projects/adding-a-new-project/ 
> 
> 
> 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:
> 
> +1
> 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 system(s).
> 
> ±0
> 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 abstain.
> 
> -1
> 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
> @TheTechScribe
> 574.383.9BKP
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-22 Thread Francesco Romani 

- Original Message -
> From: "Nir Soffer" <nsof...@redhat.com>
> To: "Michal Skrivanek" <mskri...@redhat.com>
> Cc: "devel" <devel@ovirt.org>, "board" <bo...@ovirt.org>
> Sent: Monday, November 21, 2016 10:00:05 PM
> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
> 
> On Mon, Nov 21, 2016 at 9:52 PM, Michal Skrivanek <mskri...@redhat.com>
> wrote:
> >
> >
> >> On 21 Nov 2016, at 19:48, Vojtech Szocs <vsz...@redhat.com> wrote:
> >>
> >>
> >>
> >> - Original Message -
> >>> From: "Eyal Edri" <ee...@redhat.com>
> >>> To: "Vojtech Szocs" <vsz...@redhat.com>
> >>> Cc: "Barak Korren" <bkor...@redhat.com>, "devel" <devel@ovirt.org>,
> >>> "board" <bo...@ovirt.org>, "Michal Skrivanek"
> >>> <mskri...@redhat.com>
> >>> Sent: Monday, November 21, 2016 7:23:44 PM
> >>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
> >>>
> >>>> On Mon, Nov 21, 2016 at 8:17 PM, Vojtech Szocs <vsz...@redhat.com>
> >>>> wrote:
> >>>>
> >>>>
> >>>>
> >>>> - Original Message -
> >>>>> From: "Barak Korren" <bkor...@redhat.com>
> >>>>> To: "Brian Proffitt" <bprof...@redhat.com>
> >>>>> Cc: "Michal Skrivanek" <mskri...@redhat.com>, bo...@ovirt.org, "devel"
> >>>>> <
> >>>> devel@ovirt.org>
> >>>>> Sent: Monday, November 21, 2016 7:01:08 PM
> >>>>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt
> >>>>> Project
> >>>>>
> >>>>> -1
> >
> > I wonder if 8x +1 beats one -1 :)
> 
> 9X :-)
> 
> +1 for including the project as is.

Same, +1 for moVirt
 
> If someone wants to run the project test or build it, the right way
> to vote is by sending patches and making it happen.
> 
> I think we should get out of our gerrit silo and move all ovirt
> projects to github. This will give ovirt much better visibility.
> 
> Here are some projects developed on github:
> https://github.com/systemd/systemd
> https://github.com/rust-lang/rust/
> https://github.com/kubernetes/kubernetes

I have a very similar opinion. *Development* could move more towards github.
If nothing else, this gives much better visibility and lowers the barrier to 
contribution.

This doesn't mean we should shut down the existing infra: it fully makes sense 
to have CI,
releases and final docs on ovirt.org, though.

-- 
Francesco Romani
Red Hat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Nir Soffer 
On Mon, Nov 21, 2016 at 9:52 PM, Michal Skrivanek <mskri...@redhat.com> wrote:
>
>
>> On 21 Nov 2016, at 19:48, Vojtech Szocs <vsz...@redhat.com> wrote:
>>
>>
>>
>> - Original Message -
>>> From: "Eyal Edri" <ee...@redhat.com>
>>> To: "Vojtech Szocs" <vsz...@redhat.com>
>>> Cc: "Barak Korren" <bkor...@redhat.com>, "devel" <devel@ovirt.org>, "board" 
>>> <bo...@ovirt.org>, "Michal Skrivanek"
>>> <mskri...@redhat.com>
>>> Sent: Monday, November 21, 2016 7:23:44 PM
>>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
>>>
>>>> On Mon, Nov 21, 2016 at 8:17 PM, Vojtech Szocs <vsz...@redhat.com> wrote:
>>>>
>>>>
>>>>
>>>> - Original Message -----
>>>>> From: "Barak Korren" <bkor...@redhat.com>
>>>>> To: "Brian Proffitt" <bprof...@redhat.com>
>>>>> Cc: "Michal Skrivanek" <mskri...@redhat.com>, bo...@ovirt.org, "devel" <
>>>> devel@ovirt.org>
>>>>> Sent: Monday, November 21, 2016 7:01:08 PM
>>>>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
>>>>>
>>>>> -1
>
> I wonder if 8x +1 beats one -1 :)

9X :-)

+1 for including the project as is.

If someone wants to run the project test or build it, the right way
to vote is by sending patches and making it happen.

I think we should get out of our gerrit silo and move all ovirt
projects to github. This will give ovirt much better visibility.

Here are some projects developed on github:
https://github.com/systemd/systemd
https://github.com/rust-lang/rust/
https://github.com/kubernetes/kubernetes

Nir

>
>>>>> 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
>>>>> mean:
>>>>> 1. Have the code in the oVirt Gerrit
>
> 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...
>
>>>>> 2. Have tests and builds running on oVirt's CI system.
>
> Can we run mobile testing on current infra?
>
>>>>> 3. Have artefacts served from oVirt's mirrors.
>
> What artifacts? The final APK? Why? It's not a yum repo.
>
>>>>> 4. Have bugs tracked in oVirt's bugzilla.
>
> No
> 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
>
>>>>
>>>> For 1 and 4, I feel that the benefit of allowing some projects to be hosted
>>>> on GitHub (attract & involve community through GitHub's public service)
>>>> does
>>>> out-weigh the rule of strict consistency (have everything in oVirt Gerrit).
>>>>
>>>>
>>> Any project in oVirt gerrit can be mirrored to GitHub, and most of them are
>>> ( see github.com/oVirt )
>
> 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
>
>>>
>>>
>>>> Although, not sure how hard would it be to modify oVirt CI system to allow
>>>> building GitHub hosted projects.
>>>>
>>>
>>> We are supporting it, Lago is an example of such project.
>>>
>>>
>>>>
>>>> The guidelines should be clear about whether a project must be hosted via
>>>> oVirt Gerrit, whether it must have its bugs tracked via oVirt Bugzilla,
>>>> etc.
>>>>
>>>
>>> I don't think its a must, but its highly recommended IMO, and will help the
>>> project grow.
>>> Imagine this scenario:
>>>
>>> the project grows and uses its own CI/testing frameworks and reaches a
>>> point it wants to join the oVirt eco-system,
>>> At that point it will be much harder to integrate it if at all, assuming
>>> the tools he's been using were not aligned with
>>> the tooling other projects are using.
>>>
>>> Also - in terms of release process, its will be very hard to include it in
>>

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Michal Skrivanek 


> On 21 Nov 2016, at 21:09, Eyal Edri <ee...@redhat.com> wrote:
> 
> 
> 
>> On Mon, Nov 21, 2016 at 9:52 PM, Michal Skrivanek <mskri...@redhat.com> 
>> wrote:
>> 
>> 
>> > On 21 Nov 2016, at 19:48, Vojtech Szocs <vsz...@redhat.com> wrote:
>> >
>> >
>> >
>> > - Original Message -
>> >> From: "Eyal Edri" <ee...@redhat.com>
>> >> To: "Vojtech Szocs" <vsz...@redhat.com>
>> >> Cc: "Barak Korren" <bkor...@redhat.com>, "devel" <devel@ovirt.org>, 
>> >> "board" <bo...@ovirt.org>, "Michal Skrivanek"
>> >> <mskri...@redhat.com>
>> >> Sent: Monday, November 21, 2016 7:23:44 PM
>> >> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
>> >>
>> >>> On Mon, Nov 21, 2016 at 8:17 PM, Vojtech Szocs <vsz...@redhat.com> wrote:
>> >>>
>> >>>
>> >>>
>> >>> - Original Message -
>> >>>> From: "Barak Korren" <bkor...@redhat.com>
>> >>>> To: "Brian Proffitt" <bprof...@redhat.com>
>> >>>> Cc: "Michal Skrivanek" <mskri...@redhat.com>, bo...@ovirt.org, "devel" <
>> >>> devel@ovirt.org>
>> >>>> Sent: Monday, November 21, 2016 7:01:08 PM
>> >>>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt 
>> >>>> Project
>> >>>>
>> >>>> -1
>> 
>> I wonder if 8x +1 beats one -1 :)
>> 
>> >>>> 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
>> >>>> mean:
>> >>>> 1. Have the code in the oVirt Gerrit
>> 
>> 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...
>> 
>> >>>> 2. Have tests and builds running on oVirt's CI system.
>> 
>> Can we run mobile testing on current infra?
> 
> We won't know until we'll try right? fact is no one asked for it until now..

True. Though...I do appreciate the offer to look into it(I hope I didn't 
misunderstand:), but honestly there are more urgent things to resolve with lago 
stability...that is way more important at the moment IMHO

>  
>> 
>> >>>> 3. Have artefacts served from oVirt's mirrors.
>> 
>> What artifacts? The final APK? Why? It's not a yum repo.
> 
> 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.
> I'm sure we can find a way if the project owner wants it. 

It is surely doable, but it doesn't give us much. The availability as a github 
release is good enough for development, and the "official" package is delivered 
through google play anyway

>  
>> 
>> >>>> 4. Have bugs tracked in oVirt's bugzilla.
>> 
>> No
>> 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
> 
> 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 )

I'm not sure, I do think we will want to move off for more and more parts of 
ovirt. How to keep a unified approach is to be seen indeed, we certainly don't 
want to diverse too much

>  
>> 
>> >>>
>> >>> For 1 and 4, I feel that the benefit of allowing some projects to be 
>> >>> hosted
>> >>> on GitHub (attract & involve community through GitHub's public service)
>> >>> does
>> >>> out-weigh the rule of strict consistency (have everything in oVirt 
>> >>> Gerrit).
>> >>>
>> >>>
>> >> Any project in oVirt gerrit can be mirrored to GitHub, and most of them 
>> >> are
>> >> ( see github.com/oVirt )
>>

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Eyal Edri 
On Mon, Nov 21, 2016 at 9:52 PM, Michal Skrivanek <mskri...@redhat.com>
wrote:

>
>
> > On 21 Nov 2016, at 19:48, Vojtech Szocs <vsz...@redhat.com> wrote:
> >
> >
> >
> > - Original Message -
> >> From: "Eyal Edri" <ee...@redhat.com>
> >> To: "Vojtech Szocs" <vsz...@redhat.com>
> >> Cc: "Barak Korren" <bkor...@redhat.com>, "devel" <devel@ovirt.org>,
> "board" <bo...@ovirt.org>, "Michal Skrivanek"
> >> <mskri...@redhat.com>
> >> Sent: Monday, November 21, 2016 7:23:44 PM
> >> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt
> Project
> >>
> >>> On Mon, Nov 21, 2016 at 8:17 PM, Vojtech Szocs <vsz...@redhat.com>
> wrote:
> >>>
> >>>
> >>>
> >>> - Original Message -
> >>>> From: "Barak Korren" <bkor...@redhat.com>
> >>>> To: "Brian Proffitt" <bprof...@redhat.com>
> >>>> Cc: "Michal Skrivanek" <mskri...@redhat.com>, bo...@ovirt.org,
> "devel" <
> >>> devel@ovirt.org>
> >>>> Sent: Monday, November 21, 2016 7:01:08 PM
> >>>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt
> Project
> >>>>
> >>>> -1
>
> I wonder if 8x +1 beats one -1 :)
>
> >>>> 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
> >>>> mean:
> >>>> 1. Have the code in the oVirt Gerrit
>
> 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...
>
> >>>> 2. Have tests and builds running on oVirt's CI system.
>
> Can we run mobile testing on current infra?
>

We won't know until we'll try right? fact is no one asked for it until now..


>
> >>>> 3. Have artefacts served from oVirt's mirrors.
>
> What artifacts? The final APK? Why? It's not a yum repo.
>

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.
I'm sure we can find a way if the project owner wants it.


>
> >>>> 4. Have bugs tracked in oVirt's bugzilla.
>
> No
> 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
>

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 )


>
> >>>
> >>> For 1 and 4, I feel that the benefit of allowing some projects to be
> hosted
> >>> on GitHub (attract & involve community through GitHub's public service)
> >>> does
> >>> out-weigh the rule of strict consistency (have everything in oVirt
> Gerrit).
> >>>
> >>>
> >> Any project in oVirt gerrit can be mirrored to GitHub, and most of them
> are
> >> ( see github.com/oVirt )
>
> 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
>
> >>
> >>
> >>> Although, not sure how hard would it be to modify oVirt CI system to
> allow
> >>> building GitHub hosted projects.
> >>>
> >>
> >> We are supporting it, Lago is an example of such project.
> >>
> >>
> >>>
> >>> The guidelines should be clear about whether a project must be hosted
> via
> >>> oVirt Gerrit, whether it must have its bugs tracked via oVirt Bugzilla,
> >>> etc.
> >>>
> >>
> >> I don't think its a must, but its highly recommended IMO, and will help
> the
> >> project grow.
> >> Imagine this scenario:
> >>
> >> the project grows and uses its own CI/testing frameworks and reaches a
> >> point it wants to join the oVirt eco-system,
> >> At that point it will be much harder to integrate it if at all, assuming
> >> the t

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Vojtech Szocs 


- Original Message -
> From: "Eyal Edri" <ee...@redhat.com>
> To: "Vojtech Szocs" <vsz...@redhat.com>
> Cc: "Barak Korren" <bkor...@redhat.com>, "devel" <devel@ovirt.org>, "board" 
> <bo...@ovirt.org>, "Michal Skrivanek"
> <mskri...@redhat.com>
> Sent: Monday, November 21, 2016 7:23:44 PM
> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
> 
> On Mon, Nov 21, 2016 at 8:17 PM, Vojtech Szocs <vsz...@redhat.com> wrote:
> 
> >
> >
> > - Original Message -
> > > From: "Barak Korren" <bkor...@redhat.com>
> > > To: "Brian Proffitt" <bprof...@redhat.com>
> > > Cc: "Michal Skrivanek" <mskri...@redhat.com>, bo...@ovirt.org, "devel" <
> > devel@ovirt.org>
> > > Sent: Monday, November 21, 2016 7:01:08 PM
> > > Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
> > >
> > > -1
> > > 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
> > > mean:
> > > 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.
> >
> > For 1 and 4, I feel that the benefit of allowing some projects to be hosted
> > on GitHub (attract & involve community through GitHub's public service)
> > does
> > out-weigh the rule of strict consistency (have everything in oVirt Gerrit).
> >
> >
> Any project in oVirt gerrit can be mirrored to GitHub, and most of them are
> ( see github.com/oVirt )
> 
> 
> > Although, not sure how hard would it be to modify oVirt CI system to allow
> > building GitHub hosted projects.
> >
> 
> We are supporting it, Lago is an example of such project.
> 
> 
> >
> > The guidelines should be clear about whether a project must be hosted via
> > oVirt Gerrit, whether it must have its bugs tracked via oVirt Bugzilla,
> > etc.
> >
> 
> I don't think its a must, but its highly recommended IMO, and will help the
> project grow.
> Imagine this scenario:
> 
> the project grows and uses its own CI/testing frameworks and reaches a
> point it wants to join the oVirt eco-system,
> At that point it will be much harder to integrate it if at all, assuming
> the tools he's been using were not aligned with
> the tooling other projects are using.
> 
> Also - in terms of release process, its will be very hard to include it in
> an official oVirt release if he wishes to do so,
> as all oVirt projects are built in the current infra and shipped as a
> single repository.

Eyal, I agree with your points.

I just wanted to point out the possibility of hosting project's
sources on GitHub (point 1 from Barak's list). And as you wrote,
Lago is a good example of such project.

Using standard oVirt CI infra & tools (points 2 & 3 from Barak's
list) should be mandatory for all oVirt projects, to keep things
manageable from build/release perspective. Full agreement here.

As for bug tracking (point 4 from Barak's list), I see Lago using
GitHub's issue tracking interface, so this should be OK too..

In general, I'd say that moVirt maintainers should clearly voice
their vision on converging (or not) towards points 1,2,3,4 that
Barak has mentioned in his email.

For me, having source code & issues on GitHub, but using standard
oVirt CI infra & tools, is still acceptable for an oVirt project,
but it's just my own opinion.

> 
> 
> >
> > >
> > > On 21 November 2016 at 19:07, Brian Proffitt <bprof...@redhat.com>
> > wrote:
> > > > All:
> > > >
> > > > The moVirt Project was initially accepted as an oVirt incubator
> > project in
> > > > February 2015. It has been a successful subproject for quite some time
> > and
> > > > it is well due for being accepted as a full oVirt project. I believe
> > it is
> > > > appropriate to post a Call for Vote on the Devel and Board lists.
> > > >
> > > > http://www.ovirt.org/develop/projects/project-movirt/
> > > >
> > > > A “healthy” project, as determined by the oVirt Board, can be found at
> > > > http://www.ovirt.org/develop/projects/adding-a-new-project/
> > > >
> > > > Voting will be open until 1200 UTC Nov. 30, 20

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Eyal Edri 
On Mon, Nov 21, 2016 at 8:17 PM, Vojtech Szocs <vsz...@redhat.com> wrote:

>
>
> - Original Message -
> > From: "Barak Korren" <bkor...@redhat.com>
> > To: "Brian Proffitt" <bprof...@redhat.com>
> > Cc: "Michal Skrivanek" <mskri...@redhat.com>, bo...@ovirt.org, "devel" <
> devel@ovirt.org>
> > Sent: Monday, November 21, 2016 7:01:08 PM
> > Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
> >
> > -1
> > 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
> > mean:
> > 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.
>
> For 1 and 4, I feel that the benefit of allowing some projects to be hosted
> on GitHub (attract & involve community through GitHub's public service)
> does
> out-weigh the rule of strict consistency (have everything in oVirt Gerrit).
>
>
Any project in oVirt gerrit can be mirrored to GitHub, and most of them are
( see github.com/oVirt )


> Although, not sure how hard would it be to modify oVirt CI system to allow
> building GitHub hosted projects.
>

We are supporting it, Lago is an example of such project.


>
> The guidelines should be clear about whether a project must be hosted via
> oVirt Gerrit, whether it must have its bugs tracked via oVirt Bugzilla,
> etc.
>

I don't think its a must, but its highly recommended IMO, and will help the
project grow.
Imagine this scenario:

the project grows and uses its own CI/testing frameworks and reaches a
point it wants to join the oVirt eco-system,
At that point it will be much harder to integrate it if at all, assuming
the tools he's been using were not aligned with
the tooling other projects are using.

Also - in terms of release process, its will be very hard to include it in
an official oVirt release if he wishes to do so,
as all oVirt projects are built in the current infra and shipped as a
single repository.


>
> >
> > On 21 November 2016 at 19:07, Brian Proffitt <bprof...@redhat.com>
> wrote:
> > > All:
> > >
> > > The moVirt Project was initially accepted as an oVirt incubator
> project in
> > > February 2015. It has been a successful subproject for quite some time
> and
> > > it is well due for being accepted as a full oVirt project. I believe
> it is
> > > appropriate to post a Call for Vote on the Devel and Board lists.
> > >
> > > http://www.ovirt.org/develop/projects/project-movirt/
> > >
> > > A “healthy” project, as determined by the oVirt Board, can be found at
> > > http://www.ovirt.org/develop/projects/adding-a-new-project/
> > >
> > > 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:
> > >
> > > +1
> > > 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
> > > system(s).
> > >
> > > ±0
> > > 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
> > > abstain.
> > >
> > > -1
> > > 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
> > > @TheTechScribe
> > > 574.383.9BKP
> > >
> > > ___
> > > Devel mailing list
> > > Devel@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/devel
> >
> >
> >
> > --
> > Barak Korren
> > bkor...@redhat.com
> > RHEV-CI Team
> > ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>


-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Vojtech Szocs 


- Original Message -
> From: "Barak Korren" <bkor...@redhat.com>
> To: "Brian Proffitt" <bprof...@redhat.com>
> Cc: "Michal Skrivanek" <mskri...@redhat.com>, bo...@ovirt.org, "devel" 
> <devel@ovirt.org>
> Sent: Monday, November 21, 2016 7:01:08 PM
> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
> 
> -1
> 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
> mean:
> 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.

For 1 and 4, I feel that the benefit of allowing some projects to be hosted
on GitHub (attract & involve community through GitHub's public service) does
out-weigh the rule of strict consistency (have everything in oVirt Gerrit).

Although, not sure how hard would it be to modify oVirt CI system to allow
building GitHub hosted projects.

The guidelines should be clear about whether a project must be hosted via
oVirt Gerrit, whether it must have its bugs tracked via oVirt Bugzilla, etc.

> 
> On 21 November 2016 at 19:07, Brian Proffitt <bprof...@redhat.com> wrote:
> > All:
> >
> > The moVirt Project was initially accepted as an oVirt incubator project in
> > February 2015. It has been a successful subproject for quite some time and
> > it is well due for being accepted as a full oVirt project. I believe it is
> > appropriate to post a Call for Vote on the Devel and Board lists.
> >
> > http://www.ovirt.org/develop/projects/project-movirt/
> >
> > A “healthy” project, as determined by the oVirt Board, can be found at
> > http://www.ovirt.org/develop/projects/adding-a-new-project/
> >
> > 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:
> >
> > +1
> > 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
> > system(s).
> >
> > ±0
> > 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
> > abstain.
> >
> > -1
> > 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
> > @TheTechScribe
> > 574.383.9BKP
> >
> > ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> 
> 
> 
> --
> Barak Korren
> bkor...@redhat.com
> RHEV-CI Team
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Eyal Edri 
On Mon, Nov 21, 2016 at 8:01 PM, Barak Korren  wrote:

> -1
> 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
> mean:
> 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  wrote:
> > All:
> >
> > The moVirt Project was initially accepted as an oVirt incubator project
> in
> > February 2015. It has been a successful subproject for quite some time
> and
> > it is well due for being accepted as a full oVirt project. I believe it
> is
> > appropriate to post a Call for Vote on the Devel and Board lists.
> >
> > http://www.ovirt.org/develop/projects/project-movirt/
> >
> > A “healthy” project, as determined by the oVirt Board, can be found at
> > http://www.ovirt.org/develop/projects/adding-a-new-project/
> >
> > 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:
> >
> > +1
> > 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
> > system(s).
> >
> > ±0
> > 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
> > abstain.
> >
> > -1
> > 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
> > @TheTechScribe
> > 574.383.9BKP
> >
> > ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
>
>
>
> --
> Barak Korren
> bkor...@redhat.com
> RHEV-CI Team
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>


-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Barak Korren 
-1
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
mean:
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.

On 21 November 2016 at 19:07, Brian Proffitt  wrote:
> All:
>
> The moVirt Project was initially accepted as an oVirt incubator project in
> February 2015. It has been a successful subproject for quite some time and
> it is well due for being accepted as a full oVirt project. I believe it is
> appropriate to post a Call for Vote on the Devel and Board lists.
>
> http://www.ovirt.org/develop/projects/project-movirt/
>
> A “healthy” project, as determined by the oVirt Board, can be found at
> http://www.ovirt.org/develop/projects/adding-a-new-project/
>
> 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:
>
> +1
> 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
> system(s).
>
> ±0
> 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
> abstain.
>
> -1
> 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
> @TheTechScribe
> 574.383.9BKP
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel



-- 
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Paul Dyer 
+1, I use it often.

On Mon, Nov 21, 2016 at 11:35 AM, Sphoorti Joglekar <
sphoorti.jogle...@gmail.com> wrote:

> +1
> The project has made tremendous progress.
> On Nov 21, 2016 12:21, "Martin Betak" <mbe...@redhat.com> wrote:
>
>> +1 Albeit obviously biased :-), I think given the continuously growing
>> user base and stability, it is well deserved.
>>
>> - Original Message -
>> > From: "Brian Proffitt" <bprof...@redhat.com>
>> > To: "devel" <devel@ovirt.org>, bo...@ovirt.org
>> > Cc: "Michal Skrivanek" <mskri...@redhat.com>
>> > Sent: Monday, November 21, 2016 6:07:11 PM
>> > Subject: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
>> >
>> > All:
>> >
>> > The moVirt Project was initially accepted as an oVirt incubator project
>> in
>> > February 2015. It has been a successful subproject for quite some time
>> and
>> > it is well due for being accepted as a full oVirt project. I believe it
>> is
>> > appropriate to post a Call for Vote on the Devel and Board lists.
>> >
>> > http://www.ovirt.org/develop/projects/project-movirt/
>> >
>> > A “healthy” project, as determined by the oVirt Board, can be found at
>> > http://www.ovirt.org/develop/projects/adding-a-new-project/
>> >
>> > 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:
>> >
>> > +1
>> > 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
>> system(s).
>> >
>> > ±0
>> > 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
>> > abstain.
>> >
>> > -1
>> > 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
>> > @TheTechScribe
>> > 574.383.9BKP
>> >
>> > ___
>> > Devel mailing list
>> > Devel@ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/devel
>> ___
>> Devel mailing list
>> Devel@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>



-- 
Paul Dyer,
Mercury Consulting Group, RHCE
504-302-8750
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Sphoorti Joglekar 
+1
The project has made tremendous progress.
On Nov 21, 2016 12:21, "Martin Betak" <mbe...@redhat.com> wrote:

> +1 Albeit obviously biased :-), I think given the continuously growing
> user base and stability, it is well deserved.
>
> - Original Message -
> > From: "Brian Proffitt" <bprof...@redhat.com>
> > To: "devel" <devel@ovirt.org>, bo...@ovirt.org
> > Cc: "Michal Skrivanek" <mskri...@redhat.com>
> > Sent: Monday, November 21, 2016 6:07:11 PM
> > Subject: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
> >
> > All:
> >
> > The moVirt Project was initially accepted as an oVirt incubator project
> in
> > February 2015. It has been a successful subproject for quite some time
> and
> > it is well due for being accepted as a full oVirt project. I believe it
> is
> > appropriate to post a Call for Vote on the Devel and Board lists.
> >
> > http://www.ovirt.org/develop/projects/project-movirt/
> >
> > A “healthy” project, as determined by the oVirt Board, can be found at
> > http://www.ovirt.org/develop/projects/adding-a-new-project/
> >
> > 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:
> >
> > +1
> > 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
> system(s).
> >
> > ±0
> > 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
> > abstain.
> >
> > -1
> > 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
> > @TheTechScribe
> > 574.383.9BKP
> >
> > ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Martin Betak 
+1 Albeit obviously biased :-), I think given the continuously growing user 
base and stability, it is well deserved.

- Original Message -
> From: "Brian Proffitt" <bprof...@redhat.com>
> To: "devel" <devel@ovirt.org>, bo...@ovirt.org
> Cc: "Michal Skrivanek" <mskri...@redhat.com>
> Sent: Monday, November 21, 2016 6:07:11 PM
> Subject: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project
> 
> All:
> 
> The moVirt Project was initially accepted as an oVirt incubator project in
> February 2015. It has been a successful subproject for quite some time and
> it is well due for being accepted as a full oVirt project. I believe it is
> appropriate to post a Call for Vote on the Devel and Board lists.
> 
> http://www.ovirt.org/develop/projects/project-movirt/
> 
> A “healthy” project, as determined by the oVirt Board, can be found at
> http://www.ovirt.org/develop/projects/adding-a-new-project/
> 
> 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:
> 
> +1
> 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 system(s).
> 
> ±0
> 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
> abstain.
> 
> -1
> 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
> @TheTechScribe
> 574.383.9BKP
> 
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Martin Perina 
+1


On Mon, Nov 21, 2016 at 6:07 PM, Brian Proffitt  wrote:

> All:
>
> The moVirt Project was initially accepted as an oVirt incubator project in
> February 2015. It has been a successful subproject for quite some time and
> it is well due for being accepted as a full oVirt project. I believe it
> is appropriate to post a Call for Vote on the Devel and Board lists.
>
> http://www.ovirt.org/develop/projects/project-movirt/
>
> A “healthy” project, as determined by the oVirt Board, can be found at
> http://www.ovirt.org/develop/projects/adding-a-new-project/
>
> 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:
>
> +1
> 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
> system(s).
>
> ±0
> 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
> abstain.
>
> -1
> 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
> @TheTechScribe
> 574.383.9BKP
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Martin Sivak 
+1

--
Martin Sivak
SLA / oVirt

On Mon, Nov 21, 2016 at 6:07 PM, Brian Proffitt  wrote:
> All:
>
> The moVirt Project was initially accepted as an oVirt incubator project in
> February 2015. It has been a successful subproject for quite some time and
> it is well due for being accepted as a full oVirt project. I believe it is
> appropriate to post a Call for Vote on the Devel and Board lists.
>
> http://www.ovirt.org/develop/projects/project-movirt/
>
> A “healthy” project, as determined by the oVirt Board, can be found at
> http://www.ovirt.org/develop/projects/adding-a-new-project/
>
> 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:
>
> +1
> 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
> system(s).
>
> ±0
> 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
> abstain.
>
> -1
> 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
> @TheTechScribe
> 574.383.9BKP
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [Call for Vote] moVirt as a Full oVirt Project

2016-11-21 Thread Brian Proffitt 
All:

The moVirt Project was initially accepted as an oVirt incubator project in
February 2015. It has been a successful subproject for quite some time and
it is well due for being accepted as a full oVirt project. I believe it is
appropriate to post a Call for Vote on the Devel and Board lists.

http://www.ovirt.org/develop/projects/project-movirt/

A “healthy” project, as determined by the oVirt Board, can be found at
http://www.ovirt.org/develop/projects/adding-a-new-project/

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:

+1
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
system(s).

±0
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
abstain.

-1
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
@TheTechScribe
574.383.9BKP
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel