11:07 a.m.
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
11:11 a.m.
+1
--
Martin Sivak
SLA / oVirt
On Mon, Nov 21, 2016 at 6:07 PM, Brian Proffitt <bproffit(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
11:14 a.m.
+1
On Mon, Nov 21, 2016 at 6:07 PM, Brian Proffitt <bproffit(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
11:15 a.m.
Il 21/Nov/2016 18:07, "Brian Proffitt" <bproffit(a)redhat.com> ha scritto:
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.
+1 moVirt is a great project, happy to wrlcome it in the oVirt family!
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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
11:21 a.m.
+1 Albeit obviously biased :-), I think given the continuously growing user base and
stability, it is well deserved.
----- Original Message -----
From: "Brian Proffitt" <bproffit(a)redhat.com>
To: "devel" <devel(a)ovirt.org>, board(a)ovirt.org
Cc: "Michal Skrivanek" <mskrivan(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
11:35 a.m.
+1
The project has made tremendous progress.
On Nov 21, 2016 12:21, "Martin Betak" <mbetak(a)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" <bproffit(a)redhat.com>
> To: "devel" <devel(a)ovirt.org>, board(a)ovirt.org
> Cc: "Michal Skrivanek" <mskrivan(a)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(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
11:59 a.m.
+1, I use it often.
On Mon, Nov 21, 2016 at 11:35 AM, Sphoorti Joglekar <
sphoorti.joglekar(a)gmail.com> wrote:
+1
The project has made tremendous progress.
On Nov 21, 2016 12:21, "Martin Betak" <mbetak(a)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" <bproffit(a)redhat.com>
> > To: "devel" <devel(a)ovirt.org>, board(a)ovirt.org
> > Cc: "Michal Skrivanek" <mskrivan(a)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(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
Paul Dyer,
Mercury Consulting Group, RHCE
504-302-8750
12:01 p.m.
-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 <bproffit(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
Barak Korren
bkorren(a)redhat.com
RHEV-CI Team
12:09 p.m.
On Mon, Nov 21, 2016 at 8:01 PM, Barak Korren <bkorren(a)redhat.com> 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 <bproffit(a)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(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
--
Barak Korren
bkorren(a)redhat.com
RHEV-CI Team
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
12:17 p.m.
----- Original Message -----
From: "Barak Korren" <bkorren(a)redhat.com>
To: "Brian Proffitt" <bproffit(a)redhat.com>
Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>, board(a)ovirt.org,
"devel" <devel(a)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 <bproffit(a)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(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
--
Barak Korren
bkorren(a)redhat.com
RHEV-CI Team
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
12:23 p.m.
On Mon, Nov 21, 2016 at 8:17 PM, Vojtech Szocs <vszocs(a)redhat.com> wrote:
----- Original Message -----
> From: "Barak Korren" <bkorren(a)redhat.com>
> To: "Brian Proffitt" <bproffit(a)redhat.com>
> Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>, board(a)ovirt.org,
"devel" <
devel(a)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 <bproffit(a)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(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
>
>
>
> --
> Barak Korren
> bkorren(a)redhat.com
> RHEV-CI Team
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
12:48 p.m.
----- Original Message -----
From: "Eyal Edri" <eedri(a)redhat.com>
To: "Vojtech Szocs" <vszocs(a)redhat.com>
Cc: "Barak Korren" <bkorren(a)redhat.com>, "devel"
<devel(a)ovirt.org>, "board" <board(a)ovirt.org>, "Michal
Skrivanek"
<mskrivan(a)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 <vszocs(a)redhat.com> wrote:
>
>
> ----- Original Message -----
> > From: "Barak Korren" <bkorren(a)redhat.com>
> > To: "Brian Proffitt" <bproffit(a)redhat.com>
> > Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>, board(a)ovirt.org,
"devel" <
> devel(a)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 <bproffit(a)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(a)ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/devel
> >
> >
> >
> > --
> > Barak Korren
> > bkorren(a)redhat.com
> > RHEV-CI Team
> > _______________________________________________
> > Devel mailing list
> > Devel(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>
--
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
1:52 p.m.
On 21 Nov 2016, at 19:48, Vojtech Szocs <vszocs(a)redhat.com>
wrote:
----- Original Message -----
> From: "Eyal Edri" <eedri(a)redhat.com>
> To: "Vojtech Szocs" <vszocs(a)redhat.com>
> Cc: "Barak Korren" <bkorren(a)redhat.com>, "devel"
<devel(a)ovirt.org>, "board" <board(a)ovirt.org>, "Michal
Skrivanek"
> <mskrivan(a)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 <vszocs(a)redhat.com> wrote:
>>
>>
>>
>> ----- Original Message -----
>>> From: "Barak Korren" <bkorren(a)redhat.com>
>>> To: "Brian Proffitt" <bproffit(a)redhat.com>
>>> Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>,
board(a)ovirt.org, "devel" <
>> devel(a)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?
>>> 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
> 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.
You're missing the point it's not a yum repo.
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.
I would say no. And that is fine
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.
I agree we can mix and match, though in this case I'm not sure how realistic is to run
CI for an APK
>
>
>>
>>>
>>> On 21 November 2016 at 19:07, Brian Proffitt <bproffit(a)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(a)ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>
>>>
>>>
>>> --
>>> Barak Korren
>>> bkorren(a)redhat.com
>>> RHEV-CI Team
>>> _______________________________________________
>>> Devel mailing list
>>> Devel(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
>> _______________________________________________
>> Devel mailing list
>> Devel(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>>
>>
>
>
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
2:08 p.m.
On Mon, Nov 21, 2016 at 9:52 PM, Michal Skrivanek <mskrivan(a)redhat.com>
wrote:
> On 21 Nov 2016, at 19:48, Vojtech Szocs <vszocs(a)redhat.com> wrote:
>
>
>
> ----- Original Message -----
>> From: "Eyal Edri" <eedri(a)redhat.com>
>> To: "Vojtech Szocs" <vszocs(a)redhat.com>
>> Cc: "Barak Korren" <bkorren(a)redhat.com>, "devel"
<devel(a)ovirt.org>,
"board" <board(a)ovirt.org>, "Michal Skrivanek"
>> <mskrivan(a)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 <vszocs(a)redhat.com>
wrote:
>>>
>>>
>>>
>>> ----- Original Message -----
>>>> From: "Barak Korren" <bkorren(a)redhat.com>
>>>> To: "Brian Proffitt" <bproffit(a)redhat.com>
>>>> Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>,
board(a)ovirt.org,
"devel" <
>>> devel(a)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 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.
You're missing the point it's not a yum repo.
See my comments above on supporting other artifacts than rpms.
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 ),
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).
>
> 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.
I would say no. And that is fine
>
> 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.
I agree we can mix and match, though in this case I'm not sure how
realistic is to run CI for an APK
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.
I tend not to rule out anything I haven't verified possible before.
>
>>
>>
>>>
>>>>
>>>> On 21 November 2016 at 19:07, Brian Proffitt
<bproffit(a)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(a)ovirt.org
>>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>
>>>>
>>>>
>>>> --
>>>> Barak Korren
>>>> bkorren(a)redhat.com
>>>> RHEV-CI Team
>>>> _______________________________________________
>>>> Devel mailing list
>>>> Devel(a)ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>> _______________________________________________
>>> Devel mailing list
>>> Devel(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>
>>>
>>>
>>
>>
>> --
>> Eyal Edri
>> Associate Manager
>> RHV DevOps
>> EMEA ENG Virtualization R&D
>> Red Hat Israel
>>
>> phone: +972-9-7692018
>> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>>
--
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
2:56 p.m.
--Apple-Mail-ACF64B2F-A96E-4378-AC26-CB1DD2165EDA
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: base64
DQoNCj4gT24gMjEgTm92IDIwMTYsIGF0IDIxOjA5LCBFeWFsIEVkcmkgPGVlZHJpQHJlZGhhdC5j
b20+IHdyb3RlOg0KPiANCj4gDQo+IA0KPj4gT24gTW9uLCBOb3YgMjEsIDIwMTYgYXQgOTo1MiBQ
TSwgTWljaGFsIFNrcml2YW5layA8bXNrcml2YW5AcmVkaGF0LmNvbT4gd3JvdGU6DQo+PiANCj4+
IA0KPj4gPiBPbiAyMSBOb3YgMjAxNiwgYXQgMTk6NDgsIFZvanRlY2ggU3pvY3MgPHZzem9jc0By
ZWRoYXQuY29tPiB3cm90ZToNCj4+ID4NCj4+ID4NCj4+ID4NCj4+ID4gLS0tLS0gT3JpZ2luYWwg
TWVzc2FnZSAtLS0tLQ0KPj4gPj4gRnJvbTogIkV5YWwgRWRyaSIgPGVlZHJpQHJlZGhhdC5jb20+
DQo+PiA+PiBUbzogIlZvanRlY2ggU3pvY3MiIDx2c3pvY3NAcmVkaGF0LmNvbT4NCj4+ID4+IENj
OiAiQmFyYWsgS29ycmVuIiA8YmtvcnJlbkByZWRoYXQuY29tPiwgImRldmVsIiA8ZGV2ZWxAb3Zp
cnQub3JnPiwgImJvYXJkIiA8Ym9hcmRAb3ZpcnQub3JnPiwgIk1pY2hhbCBTa3JpdmFuZWsiDQo+
PiA+PiA8bXNrcml2YW5AcmVkaGF0LmNvbT4NCj4+ID4+IFNlbnQ6IE1vbmRheSwgTm92ZW1iZXIg
MjEsIDIwMTYgNzoyMzo0NCBQTQ0KPj4gPj4gU3ViamVjdDogUmU6IFtvdmlydC1kZXZlbF0gW0Nh
bGwgZm9yIFZvdGVdIG1vVmlydCBhcyBhIEZ1bGwgb1ZpcnQgUHJvamVjdA0KPj4gPj4NCj4+ID4+
PiBPbiBNb24sIE5vdiAyMSwgMjAxNiBhdCA4OjE3IFBNLCBWb2p0ZWNoIFN6b2NzIDx2c3pvY3NA
cmVkaGF0LmNvbT4gd3JvdGU6DQo+PiA+Pj4NCj4+ID4+Pg0KPj4gPj4+DQo+PiA+Pj4gLS0tLS0g
T3JpZ2luYWwgTWVzc2FnZSAtLS0tLQ0KPj4gPj4+PiBGcm9tOiAiQmFyYWsgS29ycmVuIiA8Ymtv
cnJlbkByZWRoYXQuY29tPg0KPj4gPj4+PiBUbzogIkJyaWFuIFByb2ZmaXR0IiA8YnByb2ZmaXRA
cmVkaGF0LmNvbT4NCj4+ID4+Pj4gQ2M6ICJNaWNoYWwgU2tyaXZhbmVrIiA8bXNrcml2YW5AcmVk
aGF0LmNvbT4sIGJvYXJkQG92aXJ0Lm9yZywgImRldmVsIiA8DQo+PiA+Pj4gZGV2ZWxAb3ZpcnQu
b3JnPg0KPj4gPj4+PiBTZW50OiBNb25kYXksIE5vdmVtYmVyIDIxLCAyMDE2IDc6MDE6MDggUE0N
Cj4+ID4+Pj4gU3ViamVjdDogUmU6IFtvdmlydC1kZXZlbF0gW0NhbGwgZm9yIFZvdGVdIG1vVmly
dCBhcyBhIEZ1bGwgb1ZpcnQgUHJvamVjdA0KPj4gPj4+Pg0KPj4gPj4+PiAtMQ0KPj4gDQo+PiBJ
IHdvbmRlciBpZiA4eCArMSBiZWF0cyBvbmUgLTEgOikNCj4+IA0KPj4gPj4+PiBOb3QgYmVjYXVz
ZSBvZiBhbnl0aGluZyB3aXRoIHRoZSBwcm9qZWN0IGl0c2VsZiAtIEkgdGhpbmsgaXQgaXMNCj4+
ID4+Pj4gZ2VudWluZWx5IGF3ZXNvbWUsIGJ1dCBiZWNhdXNlIEkgZXhwZWN0IGEgcHJvamVjdCB0
aGF0IGVtZXJnZXMgb3V0IG9mDQo+PiA+Pj4+IHRoZSBpbmN1YmF0aW9uIHByb2Nlc3MgdG8gImxv
b2siIGxpa2UgYW4gb1ZpcnQgcHJvamVjdCwgYnkgd2hpY2ggSQ0KPj4gPj4+PiBtZWFuOg0KPj4g
Pj4+PiAxLiBIYXZlIHRoZSBjb2RlIGluIHRoZSBvVmlydCBHZXJyaXQNCj4+IA0KPj4gSSB3b25k
ZXIgd2h5IHRoYXQgd291bGQgYmUgcmVxdWlyZWQuIFdlIGV4cGVyaW1lbnRlZCB3aXRoIG90aGVy
IHByb2plY3RzIGJlaW5nIG9mZiBnZXJyaXQgYXMgd2VsbChlLmcuIGNvY2twaXQtb3ZpcnQpIGFu
ZCBidWcgdHJhY2tpbmcgb3V0IG9mIHJlZGhhdCBidWd6aWxsYSBhbmQgZm9yIGNlcnRhaW4gcHJv
amN0cyBpdCBtYWtlcyBzZW5zZS4gV2l0aCBtb3JlIGludGVncmF0aW9uIHdpdGggb3RoZXIgdXBz
dHJlYW0gcHJvamVjdHMgSSBzZWUgdXMgbW92aW5nIHRvIGdpdGh1YiBldmVuIG1vcmUuLi4NCj4+
IA0KPj4gPj4+PiAyLiBIYXZlIHRlc3RzIGFuZCBidWlsZHMgcnVubmluZyBvbiBvVmlydCdzIENJ
IHN5c3RlbS4NCj4+IA0KPj4gQ2FuIHdlIHJ1biBtb2JpbGUgdGVzdGluZyBvbiBjdXJyZW50IGlu
ZnJhPw0KPiANCj4gV2Ugd29uJ3Qga25vdyB1bnRpbCB3ZSdsbCB0cnkgcmlnaHQ/IGZhY3QgaXMg
bm8gb25lIGFza2VkIGZvciBpdCB1bnRpbCBub3cuLg0KDQpUcnVlLiBUaG91Z2guLi5JIGRvIGFw
cHJlY2lhdGUgdGhlIG9mZmVyIHRvIGxvb2sgaW50byBpdChJIGhvcGUgSSBkaWRuJ3QgbWlzdW5k
ZXJzdGFuZDopLCBidXQgaG9uZXN0bHkgdGhlcmUgYXJlIG1vcmUgdXJnZW50IHRoaW5ncyB0byBy
ZXNvbHZlIHdpdGggbGFnbyBzdGFiaWxpdHkuLi50aGF0IGlzIHdheSBtb3JlIGltcG9ydGFudCBh
dCB0aGUgbW9tZW50IElNSE8NCg0KPiAgDQo+PiANCj4+ID4+Pj4gMy4gSGF2ZSBhcnRlZmFjdHMg
c2VydmVkIGZyb20gb1ZpcnQncyBtaXJyb3JzLg0KPj4gDQo+PiBXaGF0IGFydGlmYWN0cz8gVGhl
IGZpbmFsIEFQSz8gV2h5PyBJdCdzIG5vdCBhIHl1bSByZXBvLg0KPiANCj4gVGhlIGZhY3Qgd2Un
cmUgb25seSBob3N0aW5nIFJQTXMgKG5vdCBlbnRpcmVseSByaWdodCwgd2UgaG9zdCBpbWFnZXMg
YXMgd2VsbCkgZG9lc24ndCBtZWFuIHdlIGNhbid0IGhvc3QgYW55dGhpbmcgZWxzZSwgd2UncmUg
YWN0dWFsbHkgd29ya2luZyBvbiBzdXBwb3J0IGZvciBidWlsZGluZy9kZXBsb3lpbmcgY29udGFp
bmVycy4NCj4gSSdtIHN1cmUgd2UgY2FuIGZpbmQgYSB3YXkgaWYgdGhlIHByb2plY3Qgb3duZXIg
d2FudHMgaXQuIA0KDQpJdCBpcyBzdXJlbHkgZG9hYmxlLCBidXQgaXQgZG9lc24ndCBnaXZlIHVz
IG11Y2guIFRoZSBhdmFpbGFiaWxpdHkgYXMgYSBnaXRodWIgcmVsZWFzZSBpcyBnb29kIGVub3Vn
aCBmb3IgZGV2ZWxvcG1lbnQsIGFuZCB0aGUgIm9mZmljaWFsIiBwYWNrYWdlIGlzIGRlbGl2ZXJl
ZCB0aHJvdWdoIGdvb2dsZSBwbGF5IGFueXdheQ0KDQo+ICANCj4+IA0KPj4gPj4+PiA0LiBIYXZl
IGJ1Z3MgdHJhY2tlZCBpbiBvVmlydCdzIGJ1Z3ppbGxhLg0KPj4gDQo+PiBObw0KPj4gVGhhdCBz
aG91bGQgbmV2ZXIgYmUgaW1wb3NlZCBvbiBhbnkgbmV3IHByb2plY3QuIElmIHNvbWVvbmUgbG92
ZXMgc2xvdyBvdXRkYXRlZCB0b29scywgc28gYmUgaXQsIGJ1dCBmb3IgbmV3IHByb2plY3RzIEkg
YWdhaW4gZG8gbm90IHNlZSB1cyBwcm9tb3RpbmcgaXQgaW4gZnV0dXJlDQo+IA0KPiBJIGFncmVl
IHRoaXMgcG9pbnQgaXMgbGVzcyByZWxldmFudCwgYW5kIGVhY2ggcHJvamVjdCBjYW4gaGFuZGxl
IGhpcyBvd24gdHJhY2tpbmcgKCBidXQgYWdhaW4sIGlmIGhlIHdpbGwgd2FudCB0byBiZSByZWxl
YXNlZCBhcyBwYXJ0IG9mIG9WaXJ0IGFuZCBub3QgaW5kZXBlbmRlbnRseSwgdGhlbiBJJ20gbm90
IHN1cmUgaGUnbGwgaGF2ZSBhIGNob2ljZSBidXQgdG8gYWxpZ24gKQ0KDQpJJ20gbm90IHN1cmUs
IEkgZG8gdGhpbmsgd2Ugd2lsbCB3YW50IHRvIG1vdmUgb2ZmIGZvciBtb3JlIGFuZCBtb3JlIHBh
cnRzIG9mIG92aXJ0LiBIb3cgdG8ga2VlcCBhIHVuaWZpZWQgYXBwcm9hY2ggaXMgdG8gYmUgc2Vl
biBpbmRlZWQsIHdlIGNlcnRhaW5seSBkb24ndCB3YW50IHRvIGRpdmVyc2UgdG9vIG11Y2guLi4u
DQoNCj4gIA0KPj4gDQo+PiA+Pj4NCj4+ID4+PiBGb3IgMSBhbmQgNCwgSSBmZWVsIHRoYXQgdGhl
IGJlbmVmaXQgb2YgYWxsb3dpbmcgc29tZSBwcm9qZWN0cyB0byBiZSBob3N0ZWQNCj4+ID4+PiBv
biBHaXRIdWIgKGF0dHJhY3QgJiBpbnZvbHZlIGNvbW11bml0eSB0aHJvdWdoIEdpdEh1YidzIHB1
YmxpYyBzZXJ2aWNlKQ0KPj4gPj4+IGRvZXMNCj4+ID4+PiBvdXQtd2VpZ2ggdGhlIHJ1bGUgb2Yg
c3RyaWN0IGNvbnNpc3RlbmN5IChoYXZlIGV2ZXJ5dGhpbmcgaW4gb1ZpcnQgR2Vycml0KS4NCj4+
ID4+Pg0KPj4gPj4+DQo+PiA+PiBBbnkgcHJvamVjdCBpbiBvVmlydCBnZXJyaXQgY2FuIGJlIG1p
cnJvcmVkIHRvIEdpdEh1YiwgYW5kIG1vc3Qgb2YgdGhlbSBhcmUNCj4+ID4+ICggc2VlIGdpdGh1
Yi5jb20vb1ZpcnQgKQ0KPj4gDQo+PiBXZSBkbyBtaXJyb3IgaXQgSUlSQyAob3IgaXQgbWF5IGhh
dmUgYmVlbiBjb2NrcGl0LW92aXJ0KSwgaXQncyBqdXN0IHRoZSBvdGhlciB3YXkgYXJvdW5kIC0g
dGhlIG1hc3RlciBjb3B5IGlzIGF0IGdpdGh1Yg0KPj4gDQo+PiA+Pg0KPj4gPj4NCj4+ID4+PiBB
bHRob3VnaCwgbm90IHN1cmUgaG93IGhhcmQgd291bGQgaXQgYmUgdG8gbW9kaWZ5IG9WaXJ0IENJ
IHN5c3RlbSB0byBhbGxvdw0KPj4gPj4+IGJ1aWxkaW5nIEdpdEh1YiBob3N0ZWQgcHJvamVjdHMu
DQo+PiA+Pj4NCj4+ID4+DQo+PiA+PiBXZSBhcmUgc3VwcG9ydGluZyBpdCwgTGFnbyBpcyBhbiBl
eGFtcGxlIG9mIHN1Y2ggcHJvamVjdC4NCj4+ID4+DQo+PiA+Pg0KPj4gPj4+DQo+PiA+Pj4gVGhl
IGd1aWRlbGluZXMgc2hvdWxkIGJlIGNsZWFyIGFib3V0IHdoZXRoZXIgYSBwcm9qZWN0IG11c3Qg
YmUgaG9zdGVkIHZpYQ0KPj4gPj4+IG9WaXJ0IEdlcnJpdCwgd2hldGhlciBpdCBtdXN0IGhhdmUg
aXRzIGJ1Z3MgdHJhY2tlZCB2aWEgb1ZpcnQgQnVnemlsbGEsDQo+PiA+Pj4gZXRjLg0KPj4gPj4+
DQo+PiA+Pg0KPj4gPj4gSSBkb24ndCB0aGluayBpdHMgYSBtdXN0LCBidXQgaXRzIGhpZ2hseSBy
ZWNvbW1lbmRlZCBJTU8sIGFuZCB3aWxsIGhlbHAgdGhlDQo+PiA+PiBwcm9qZWN0IGdyb3cuDQo+
PiA+PiBJbWFnaW5lIHRoaXMgc2NlbmFyaW86DQo+PiA+Pg0KPj4gPj4gdGhlIHByb2plY3QgZ3Jv
d3MgYW5kIHVzZXMgaXRzIG93biBDSS90ZXN0aW5nIGZyYW1ld29ya3MgYW5kIHJlYWNoZXMgYQ0K
Pj4gPj4gcG9pbnQgaXQgd2FudHMgdG8gam9pbiB0aGUgb1ZpcnQgZWNvLXN5c3RlbSwNCj4+ID4+
IEF0IHRoYXQgcG9pbnQgaXQgd2lsbCBiZSBtdWNoIGhhcmRlciB0byBpbnRlZ3JhdGUgaXQgaWYg
YXQgYWxsLCBhc3N1bWluZw0KPj4gPj4gdGhlIHRvb2xzIGhlJ3MgYmVlbiB1c2luZyB3ZXJlIG5v
dCBhbGlnbmVkIHdpdGgNCj4+ID4+IHRoZSB0b29saW5nIG90aGVyIHByb2plY3RzIGFyZSB1c2lu
Zy4NCj4+ID4+DQo+PiA+PiBBbHNvIC0gaW4gdGVybXMgb2YgcmVsZWFzZSBwcm9jZXNzLCBpdHMg
d2lsbCBiZSB2ZXJ5IGhhcmQgdG8gaW5jbHVkZSBpdCBpbg0KPj4gPj4gYW4gb2ZmaWNpYWwgb1Zp
cnQgcmVsZWFzZSBpZiBoZSB3aXNoZXMgdG8gZG8gc28sDQo+PiA+PiBhcyBhbGwgb1ZpcnQgcHJv
amVjdHMgYXJlIGJ1aWx0IGluIHRoZSBjdXJyZW50IGluZnJhIGFuZCBzaGlwcGVkIGFzIGENCj4+
ID4+IHNpbmdsZSByZXBvc2l0b3J5Lg0KPj4gDQo+PiBZb3UncmUgbWlzc2luZyB0aGUgcG9pbnQg
aXQncyBub3QgYSB5dW0gcmVwby4NCj4gDQo+IFNlZSBteSBjb21tZW50cyBhYm92ZSBvbiBzdXBw
b3J0aW5nIG90aGVyIGFydGlmYWN0cyB0aGFuIHJwbXMuIA0KPiANCj4gSSB0aGluayB5b3UncmUg
bWlzc2luZyB0aGUgcG9pbnQgb2YgdGhlIGFkdmFudGFnZXMgc3VjaCBhIHByb2plY3QgY2FuIGdl
dCBieSBqb2luaW5nLCBpbnN0ZWFkIG9mIG1hbmFnaW5nIGl0cyBpbmZyYSBoaW1zZWxmICggaWYg
aXQgaGFzIGFueSApLA0KPiBJdCBnZXRzIGEgbWFzc2l2ZSBDSS9DRCBpbmZyYXN0cnVjdHVyZSBh
bHJlYWR5IGJ1aWx0IGFuZCB3b3JraW5nLCBhbmQgd2lsbCBiZSBhYmxlIHRvIGRvIGludGVncmF0
aW9uIC8gdGVzdGluZyB3aXRoIGEgcmVhbCBvVmlydCBpbnN0YW5jZSAodXNpbmcgT1NUIGZvciBl
LmcpLg0KDQpJIGRvIG5vdCBzZWUgYSBwcm9ibGVtIHRvIGRvIHRoYXQgb25jZSB3ZSBnZXQgdGhh
dCBmYXIuICBJIHJlYWxseSBkb24ndCwgYnV0IGN1cnJlbnRseSBpdCdzIHByZW1hdHVyZS4gV2Ug
ZG8gbm90IGhhdmUgYSBzdXBwb3J0LCB3ZSBkbyBub3QgaGF2ZSBzdWNoIHRlc3RzLi4uDQoNClRo
YW5rcywNCm1pY2hhbA0KDQo+ICANCj4+IA0KPj4gPg0KPj4gPiBFeWFsLCBJIGFncmVlIHdpdGgg
eW91ciBwb2ludHMuDQo+PiA+DQo+PiA+IEkganVzdCB3YW50ZWQgdG8gcG9pbnQgb3V0IHRoZSBw
b3NzaWJpbGl0eSBvZiBob3N0aW5nIHByb2plY3Qncw0KPj4gPiBzb3VyY2VzIG9uIEdpdEh1YiAo
cG9pbnQgMSBmcm9tIEJhcmFrJ3MgbGlzdCkuIEFuZCBhcyB5b3Ugd3JvdGUsDQo+PiA+IExhZ28g
aXMgYSBnb29kIGV4YW1wbGUgb2Ygc3VjaCBwcm9qZWN0Lg0KPj4gPg0KPj4gPiBVc2luZyBzdGFu
ZGFyZCBvVmlydCBDSSBpbmZyYSAmIHRvb2xzIChwb2ludHMgMiAmIDMgZnJvbSBCYXJhaydzDQo+
PiA+IGxpc3QpIHNob3VsZCBiZSBtYW5kYXRvcnkgZm9yIGFsbCBvVmlydCBwcm9qZWN0cywgdG8g
a2VlcCB0aGluZ3MNCj4+ID4gbWFuYWdlYWJsZSBmcm9tIGJ1aWxkL3JlbGVhc2UgcGVyc3BlY3Rp
dmUuIEZ1bGwgYWdyZWVtZW50IGhlcmUuDQo+PiA+DQo+PiA+IEFzIGZvciBidWcgdHJhY2tpbmcg
KHBvaW50IDQgZnJvbSBCYXJhaydzIGxpc3QpLCBJIHNlZSBMYWdvIHVzaW5nDQo+PiA+IEdpdEh1
YidzIGlzc3VlIHRyYWNraW5nIGludGVyZmFjZSwgc28gdGhpcyBzaG91bGQgYmUgT0sgdG9vLi4N
Cj4+ID4NCj4+ID4gSW4gZ2VuZXJhbCwgSSdkIHNheSB0aGF0IG1vVmlydCBtYWludGFpbmVycyBz
aG91bGQgY2xlYXJseSB2b2ljZQ0KPj4gPiB0aGVpciB2aXNpb24gb24gY29udmVyZ2luZyAob3Ig
bm90KSB0b3dhcmRzIHBvaW50cyAxLDIsMyw0IHRoYXQNCj4+ID4gQmFyYWsgaGFzIG1lbnRpb25l
ZCBpbiBoaXMgZW1haWwuDQo+PiANCj4+IEkgd291bGQgc2F5IG5vLiBBbmQgdGhhdCBpcyBmaW5l
DQo+PiANCj4+ID4NCj4+ID4gRm9yIG1lLCBoYXZpbmcgc291cmNlIGNvZGUgJiBpc3N1ZXMgb24g
R2l0SHViLCBidXQgdXNpbmcgc3RhbmRhcmQNCj4+ID4gb1ZpcnQgQ0kgaW5mcmEgJiB0b29scywg
aXMgc3RpbGwgYWNjZXB0YWJsZSBmb3IgYW4gb1ZpcnQgcHJvamVjdCwNCj4+ID4gYnV0IGl0J3Mg
anVzdCBteSBvd24gb3Bpbmlvbi4NCj4+IA0KPj4gSSBhZ3JlZSB3ZSBjYW4gbWl4IGFuZCBtYXRj
aCwgdGhvdWdoIGluIHRoaXMgY2FzZSBJJ20gbm90IHN1cmUgaG93IHJlYWxpc3RpYyBpcyB0byBy
dW4gQ0kgZm9yIGFuIEFQSw0KPiANCj4gSSdtIHByZXR0eSBzdXJlIHRoYXQgaWYgd2Ugd2FudGVk
IHRvIGNoZWNrIHRoYXQgb3B0aW9uLCBpdCB3aWxsIGJlIHBvc3NpYmxlIGV2ZW4gaWYgYnkgdXNp
bmcgZW11bGF0b3JzLCBidXQgbm8gb25lIGZyb20gdGhlIHByb2plY3QgaGFzIGV2ZXIgYXBwcm9h
Y2hlZCB1cyBzbyBJIGNhbid0IHJlYWxseSBzYXkgYW55dGhpbmcgYmVmb3JlIEkgc2VlIHJlcXVp
cmVtZW50cy4NCj4gSSB0ZW5kIG5vdCB0byBydWxlIG91dCBhbnl0aGluZyBJIGhhdmVuJ3QgdmVy
aWZpZWQgcG9zc2libGUgYmVmb3JlLg0KPiANCj4gIA0KPj4gPg0KPj4gPj4NCj4+ID4+DQo+PiA+
Pj4NCj4+ID4+Pj4NCj4+ID4+Pj4gT24gMjEgTm92ZW1iZXIgMjAxNiBhdCAxOTowNywgQnJpYW4g
UHJvZmZpdHQgPGJwcm9mZml0QHJlZGhhdC5jb20+DQo+PiA+Pj4gd3JvdGU6DQo+PiA+Pj4+PiBB
bGw6DQo+PiA+Pj4+Pg0KPj4gPj4+Pj4gVGhlIG1vVmlydCBQcm9qZWN0IHdhcyBpbml0aWFsbHkg
YWNjZXB0ZWQgYXMgYW4gb1ZpcnQgaW5jdWJhdG9yDQo+PiA+Pj4gcHJvamVjdCBpbg0KPj4gPj4+
Pj4gRmVicnVhcnkgMjAxNS4gSXQgaGFzIGJlZW4gYSBzdWNjZXNzZnVsIHN1YnByb2plY3QgZm9y
IHF1aXRlIHNvbWUgdGltZQ0KPj4gPj4+IGFuZA0KPj4gPj4+Pj4gaXQgaXMgd2VsbCBkdWUgZm9y
IGJlaW5nIGFjY2VwdGVkIGFzIGEgZnVsbCBvVmlydCBwcm9qZWN0LiBJIGJlbGlldmUNCj4+ID4+
PiBpdCBpcw0KPj4gPj4+Pj4gYXBwcm9wcmlhdGUgdG8gcG9zdCBhIENhbGwgZm9yIFZvdGUgb24g
dGhlIERldmVsIGFuZCBCb2FyZCBsaXN0cy4NCj4+ID4+Pj4+DQo+PiA+Pj4+PiBodHRwOi8vd3d3
Lm92aXJ0Lm9yZy9kZXZlbG9wL3Byb2plY3RzL3Byb2plY3QtbW92aXJ0Lw0KPj4gPj4+Pj4NCj4+
ID4+Pj4+IEEg4oCcaGVhbHRoeeKAnSBwcm9qZWN0LCBhcyBkZXRlcm1pbmVkIGJ5IHRoZSBvVmly
dCBCb2FyZCwgY2FuIGJlIGZvdW5kIGF0DQo+PiA+Pj4+PiBodHRwOi8vd3d3Lm92aXJ0Lm9yZy9k
ZXZlbG9wL3Byb2plY3RzL2FkZGluZy1hLW5ldy1wcm9qZWN0Lw0KPj4gPj4+Pj4NCj4+ID4+Pj4+
IFZvdGluZyB3aWxsIGJlIG9wZW4gdW50aWwgMTIwMCBVVEMgTm92LiAzMCwgMjAxNi4gQSBuZXQg
dG90YWwgb2YgKzcNCj4+ID4+PiB2b3Rlcw0KPj4gPj4+Pj4gc2hvdWxkIGJlIHJlY2VpdmVkIHRv
IGZvcm1hbGl6ZSB0aGlzIHByb2plY3QgYXMgYW4gZnVsbCBvVmlydCBwcm9qZWN0Lg0KPj4gPj4+
Pj4gUGxlYXNlIHVzZSB0aGUgZm9sbG93aW5nIHZvdGUgcHJvY2VzczoNCj4+ID4+Pj4+DQo+PiA+
Pj4+PiArMQ0KPj4gPj4+Pj4gWWVzLCBhZ3JlZSwgb3IgdGhlIGFjdGlvbiBzaG91bGQgYmUgcGVy
Zm9ybWVkLiBPbiBzb21lIGlzc3VlcywgdGhpcw0KPj4gPj4+IHZvdGUNCj4+ID4+Pj4+IG11c3Qg
b25seSBiZSBnaXZlbiBhZnRlciB0aGUgdm90ZXIgaGFzIHRlc3RlZCB0aGUgYWN0aW9uIG9uIHRo
ZWlyIG93bg0KPj4gPj4+Pj4gc3lzdGVtKHMpLg0KPj4gPj4+Pj4NCj4+ID4+Pj4+IMKxMA0KPj4g
Pj4+Pj4gQWJzdGFpbiwgbm8gb3Bpbmlvbiwgb3IgSSBhbSBoYXBweSB0byBsZXQgdGhlIG90aGVy
IGdyb3VwIG1lbWJlcnMNCj4+ID4+PiBkZWNpZGUNCj4+ID4+Pj4+IHRoaXMgaXNzdWUuIEFuIGFi
c3RlbnRpb24gbWF5IGhhdmUgZGV0cmltZW50YWwgYWZmZWN0cyBpZiB0b28gbWFueQ0KPj4gPj4+
IHBlb3BsZQ0KPj4gPj4+Pj4gYWJzdGFpbi4NCj4+ID4+Pj4+DQo+PiA+Pj4+PiAtMQ0KPj4gPj4+
Pj4gTm8sIEkgdmV0byB0aGlzIGFjdGlvbi4gQWxsIHZldG9zIG11c3QgaW5jbHVkZSBhbiBleHBs
YW5hdGlvbiBvZiB3aHkNCj4+ID4+PiB0aGUNCj4+ID4+Pj4+IHZldG8gaXMgYXBwcm9wcmlhdGUu
IEEgdmV0byB3aXRoIG5vIGV4cGxhbmF0aW9uIGlzIHZvaWQuDQo+PiA+Pj4+Pg0KPj4gPj4+Pj4g
VGhhbmsgeW91IQ0KPj4gPj4+Pj4NCj4+ID4+Pj4+IEJyaWFuIFByb2ZmaXR0DQo+PiA+Pj4+PiBQ
cmluY2lwYWwgQ29tbXVuaXR5IEFuYWx5c3QNCj4+ID4+Pj4+IE9wZW4gU291cmNlIGFuZCBTdGFu
ZGFyZHMNCj4+ID4+Pj4+IEBUaGVUZWNoU2NyaWJlDQo+PiA+Pj4+PiA1NzQuMzgzLjlCS1ANCj4+
ID4+Pj4+DQo+PiA+Pj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KPj4gPj4+Pj4gRGV2ZWwgbWFpbGluZyBsaXN0DQo+PiA+Pj4+PiBEZXZlbEBvdmly
dC5vcmcNCj4+ID4+Pj4+IGh0dHA6Ly9saXN0cy5vdmlydC5vcmcvbWFpbG1hbi9saXN0aW5mby9k
ZXZlbA0KPj4gPj4+Pg0KPj4gPj4+Pg0KPj4gPj4+Pg0KPj4gPj4+PiAtLQ0KPj4gPj4+PiBCYXJh
ayBLb3JyZW4NCj4+ID4+Pj4gYmtvcnJlbkByZWRoYXQuY29tDQo+PiA+Pj4+IFJIRVYtQ0kgVGVh
bQ0KPj4gPj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPj4gPj4+PiBEZXZlbCBtYWlsaW5nIGxpc3QNCj4+ID4+Pj4gRGV2ZWxAb3ZpcnQub3JnDQo+
PiA+Pj4+IGh0dHA6Ly9saXN0cy5vdmlydC5vcmcvbWFpbG1hbi9saXN0aW5mby9kZXZlbA0KPj4g
Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiA+
Pj4gRGV2ZWwgbWFpbGluZyBsaXN0DQo+PiA+Pj4gRGV2ZWxAb3ZpcnQub3JnDQo+PiA+Pj4gaHR0
cDovL2xpc3RzLm92aXJ0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RldmVsDQo+PiA+Pj4NCj4+ID4+
Pg0KPj4gPj4+DQo+PiA+Pg0KPj4gPj4NCj4+ID4+IC0tDQo+PiA+PiBFeWFsIEVkcmkNCj4+ID4+
IEFzc29jaWF0ZSBNYW5hZ2VyDQo+PiA+PiBSSFYgRGV2T3BzDQo+PiA+PiBFTUVBIEVORyBWaXJ0
dWFsaXphdGlvbiBSJkQNCj4+ID4+IFJlZCBIYXQgSXNyYWVsDQo+PiA+Pg0KPj4gPj4gcGhvbmU6
ICs5NzItOS03NjkyMDE4DQo+PiA+PiBpcmM6IGVlZHJpIChvbiAjdGx2ICNyaGV2LWRldiAjcmhl
di1pbnRlZykNCj4+ID4+DQo+IA0KPiANCj4gDQo+IC0tIA0KPiBFeWFsIEVkcmkNCj4gQXNzb2Np
YXRlIE1hbmFnZXINCj4gUkhWIERldk9wcw0KPiBFTUVBIEVORyBWaXJ0dWFsaXphdGlvbiBSJkQN
Cj4gUmVkIEhhdCBJc3JhZWwNCj4gDQo+IHBob25lOiArOTcyLTktNzY5MjAxOA0KPiBpcmM6IGVl
ZHJpIChvbiAjdGx2ICNyaGV2LWRldiAjcmhldi1pbnRlZykNCg==
--Apple-Mail-ACF64B2F-A96E-4378-AC26-CB1DD2165EDA
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: base64
PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iY29udGVudC10eXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPjwvaGVhZD48Ym9keSBkaXI9ImF1dG8iPjxkaXY+PC9kaXY+
PGRpdj48YnI+PC9kaXY+PGRpdj48YnI+T24gMjEgTm92IDIwMTYsIGF0IDIxOjA5LCBFeWFsIEVk
cmkgJmx0OzxhIGhyZWY9Im1haWx0bzplZWRyaUByZWRoYXQuY29tIj5lZWRyaUByZWRoYXQuY29t
PC9hPiZndDsgd3JvdGU6PGJyPjxicj48L2Rpdj48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48ZGl2
PjxkaXYgZGlyPSJsdHIiPjxicj48ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+PGJyPjxkaXYgY2xh
c3M9ImdtYWlsX3F1b3RlIj5PbiBNb24sIE5vdiAyMSwgMjAxNiBhdCA5OjUyIFBNLCBNaWNoYWwg
U2tyaXZhbmVrIDxzcGFuIGRpcj0ibHRyIj4mbHQ7PGEgaHJlZj0ibWFpbHRvOm1za3JpdmFuQHJl
ZGhhdC5jb20iIHRhcmdldD0iX2JsYW5rIj5tc2tyaXZhbkByZWRoYXQuY29tPC9hPiZndDs8L3Nw
YW4+IHdyb3RlOjxicj48YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJn
aW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4
Ij48c3BhbiBjbGFzcz0iIj48YnI+DQo8YnI+DQomZ3Q7IE9uIDIxIE5vdiAyMDE2LCBhdCAxOTo0
OCwgVm9qdGVjaCBTem9jcyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnZzem9jc0ByZWRoYXQuY29tIj52
c3pvY3NAcmVkaGF0LmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0K
Jmd0Ozxicj4NCiZndDsgLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLTxicj4NCiZndDsmZ3Q7
IEZyb206ICJFeWFsIEVkcmkiICZsdDs8YSBocmVmPSJtYWlsdG86ZWVkcmlAcmVkaGF0LmNvbSI+
ZWVkcmlAcmVkaGF0LmNvbTwvYT4mZ3Q7PGJyPg0KJmd0OyZndDsgVG86ICJWb2p0ZWNoIFN6b2Nz
IiAmbHQ7PGEgaHJlZj0ibWFpbHRvOnZzem9jc0ByZWRoYXQuY29tIj52c3pvY3NAcmVkaGF0LmNv
bTwvYT4mZ3Q7PGJyPg0KJmd0OyZndDsgQ2M6ICJCYXJhayBLb3JyZW4iICZsdDs8YSBocmVmPSJt
YWlsdG86YmtvcnJlbkByZWRoYXQuY29tIj5ia29ycmVuQHJlZGhhdC5jb208L2E+Jmd0OywgImRl
dmVsIiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRldmVsQG92aXJ0Lm9yZyI+ZGV2ZWxAb3ZpcnQub3Jn
PC9hPiZndDssICJib2FyZCIgJmx0OzxhIGhyZWY9Im1haWx0bzpib2FyZEBvdmlydC5vcmciPmJv
YXJkQG92aXJ0Lm9yZzwvYT4mZ3Q7LCAiTWljaGFsIFNrcml2YW5layI8YnI+DQomZ3Q7Jmd0OyAm
bHQ7PGEgaHJlZj0ibWFpbHRvOm1za3JpdmFuQHJlZGhhdC5jb20iPm1za3JpdmFuQHJlZGhhdC5j
b208L2E+Jmd0Ozxicj4NCiZndDsmZ3Q7IFNlbnQ6IE1vbmRheSwgTm92ZW1iZXIgMjEsIDIwMTYg
NzoyMzo0NCBQTTxicj4NCiZndDsmZ3Q7IFN1YmplY3Q6IFJlOiBbb3ZpcnQtZGV2ZWxdIFtDYWxs
IGZvciBWb3RlXSBtb1ZpcnQgYXMgYSBGdWxsIG9WaXJ0IFByb2plY3Q8YnI+DQomZ3Q7Jmd0Ozxi
cj4NCiZndDsmZ3Q7Jmd0OyBPbiBNb24sIE5vdiAyMSwgMjAxNiBhdCA4OjE3IFBNLCBWb2p0ZWNo
IFN6b2NzICZsdDs8YSBocmVmPSJtYWlsdG86dnN6b2NzQHJlZGhhdC5jb20iPnZzem9jc0ByZWRo
YXQuY29tPC9hPiZndDsgd3JvdGU6PGJyPg0KJmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7
PGJyPg0KJmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7IC0tLS0tIE9yaWdpbmFsIE1lc3Nh
Z2UgLS0tLS08YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IEZyb206ICJCYXJhayBLb3JyZW4iICZsdDs8
YSBocmVmPSJtYWlsdG86YmtvcnJlbkByZWRoYXQuY29tIj5ia29ycmVuQHJlZGhhdC5jb208L2E+
Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgVG86ICJCcmlhbiBQcm9mZml0dCIgJmx0OzxhIGhy
ZWY9Im1haWx0bzpicHJvZmZpdEByZWRoYXQuY29tIj5icHJvZmZpdEByZWRoYXQuY29tPC9hPiZn
dDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IENjOiAiTWljaGFsIFNrcml2YW5layIgJmx0OzxhIGhy
ZWY9Im1haWx0bzptc2tyaXZhbkByZWRoYXQuY29tIj5tc2tyaXZhbkByZWRoYXQuY29tPC9hPiZn
dDssIDxhIGhyZWY9Im1haWx0bzpib2FyZEBvdmlydC5vcmciPmJvYXJkQG92aXJ0Lm9yZzwvYT4s
ICJkZXZlbCIgJmx0Ozxicj4NCiZndDsmZ3Q7Jmd0OyA8YSBocmVmPSJtYWlsdG86ZGV2ZWxAb3Zp
cnQub3JnIj5kZXZlbEBvdmlydC5vcmc8L2E+Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgU2Vu
dDogTW9uZGF5LCBOb3ZlbWJlciAyMSwgMjAxNiA3OjAxOjA4IFBNPGJyPg0KJmd0OyZndDsmZ3Q7
Jmd0OyBTdWJqZWN0OiBSZTogW292aXJ0LWRldmVsXSBbQ2FsbCBmb3IgVm90ZV0gbW9WaXJ0IGFz
IGEgRnVsbCBvVmlydCBQcm9qZWN0PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7
Jmd0OyZndDsgLTE8YnI+DQo8YnI+DQo8L3NwYW4+SSB3b25kZXIgaWYgOHggKzEgYmVhdHMgb25l
IC0xIDopPGJyPg0KPHNwYW4gY2xhc3M9IiI+PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyBOb3QgYmVj
YXVzZSBvZiBhbnl0aGluZyB3aXRoIHRoZSBwcm9qZWN0IGl0c2VsZiAtIEkgdGhpbmsgaXQgaXM8
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IGdlbnVpbmVseSBhd2Vzb21lLCBidXQgYmVjYXVzZSBJIGV4
cGVjdCBhIHByb2plY3QgdGhhdCBlbWVyZ2VzIG91dCBvZjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsg
dGhlIGluY3ViYXRpb24gcHJvY2VzcyB0byAibG9vayIgbGlrZSBhbiBvVmlydCBwcm9qZWN0LCBi
eSB3aGljaCBJPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyBtZWFuOjxicj4NCiZndDsmZ3Q7Jmd0OyZn
dDsgMS4gSGF2ZSB0aGUgY29kZSBpbiB0aGUgb1ZpcnQgR2Vycml0PGJyPg0KPGJyPg0KPC9zcGFu
Pkkgd29uZGVyIHdoeSB0aGF0IHdvdWxkIGJlIHJlcXVpcmVkLiBXZSBleHBlcmltZW50ZWQgd2l0
aCBvdGhlciBwcm9qZWN0cyBiZWluZyBvZmYgZ2Vycml0IGFzIHdlbGwoZS5nLiBjb2NrcGl0LW92
aXJ0KSBhbmQgYnVnIHRyYWNraW5nIG91dCBvZiByZWRoYXQgYnVnemlsbGEgYW5kIGZvciBjZXJ0
YWluIHByb2pjdHMgaXQgbWFrZXMgc2Vuc2UuIFdpdGggbW9yZSBpbnRlZ3JhdGlvbiB3aXRoIG90
aGVyIHVwc3RyZWFtIHByb2plY3RzIEkgc2VlIHVzIG1vdmluZyB0byBnaXRodWIgZXZlbiBtb3Jl
Li4uPGJyPg0KPHNwYW4gY2xhc3M9IiI+PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyAyLiBIYXZlIHRl
c3RzIGFuZCBidWlsZHMgcnVubmluZyBvbiBvVmlydCdzIENJIHN5c3RlbS48YnI+DQo8YnI+DQo8
L3NwYW4+Q2FuIHdlIHJ1biBtb2JpbGUgdGVzdGluZyBvbiBjdXJyZW50IGluZnJhPzxicj48L2Js
b2NrcXVvdGU+PGRpdj48YnI+PC9kaXY+PGRpdj5XZSB3b24ndCBrbm93IHVudGlsIHdlJ2xsIHRy
eSByaWdodD8gZmFjdCBpcyBubyBvbmUgYXNrZWQgZm9yIGl0IHVudGlsIG5vdy4uPC9kaXY+PC9k
aXY+PC9kaXY+PC9kaXY+PC9kaXY+PC9ibG9ja3F1b3RlPjxkaXY+PGJyPjwvZGl2PlRydWUuIFRo
b3VnaC4uLkkgZG8gYXBwcmVjaWF0ZSB0aGUgb2ZmZXIgdG8gbG9vayBpbnRvIGl0KEkgaG9wZSBJ
IGRpZG4ndCBtaXN1bmRlcnN0YW5kOiksIGJ1dCBob25lc3RseSB0aGVyZSBhcmUgbW9yZSB1cmdl
bnQgdGhpbmdzIHRvIHJlc29sdmUgd2l0aCBsYWdvIHN0YWJpbGl0eS4uLnRoYXQgaXMgd2F5IG1v
cmUgaW1wb3J0YW50IGF0IHRoZSBtb21lbnQgSU1ITzxkaXY+PGJyPjxibG9ja3F1b3RlIHR5cGU9
ImNpdGUiPjxkaXY+PGRpdiBkaXI9Imx0ciI+PGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPjxkaXYg
Y2xhc3M9ImdtYWlsX3F1b3RlIj48ZGl2PiZuYnNwOzwvZGl2PjxibG9ja3F1b3RlIGNsYXNzPSJn
bWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2Nj
IHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0KPHNwYW4gY2xhc3M9IiI+PGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyAzLiBIYXZlIGFydGVmYWN0cyBzZXJ2ZWQgZnJvbSBvVmlydCdzIG1pcnJvcnMuPGJy
Pg0KPGJyPg0KPC9zcGFuPldoYXQgYXJ0aWZhY3RzPyBUaGUgZmluYWwgQVBLPyBXaHk/IEl0J3Mg
bm90IGEgeXVtIHJlcG8uPGJyPjwvYmxvY2txdW90ZT48ZGl2Pjxicj48L2Rpdj48ZGl2PlRoZSBm
YWN0IHdlJ3JlIG9ubHkgaG9zdGluZyBSUE1zIChub3QgZW50aXJlbHkgcmlnaHQsIHdlIGhvc3Qg
aW1hZ2VzIGFzIHdlbGwpIGRvZXNuJ3QgbWVhbiB3ZSBjYW4ndCBob3N0IGFueXRoaW5nIGVsc2Us
IHdlJ3JlIGFjdHVhbGx5IHdvcmtpbmcgb24gc3VwcG9ydCBmb3IgYnVpbGRpbmcvZGVwbG95aW5n
IGNvbnRhaW5lcnMuPC9kaXY+PGRpdj5JJ20gc3VyZSB3ZSBjYW4gZmluZCBhIHdheSBpZiB0aGUg
cHJvamVjdCBvd25lciB3YW50cyBpdC4mbmJzcDs8L2Rpdj48L2Rpdj48L2Rpdj48L2Rpdj48L2Rp
dj48L2Jsb2NrcXVvdGU+PGRpdj48YnI+PC9kaXY+SXQgaXMgc3VyZWx5IGRvYWJsZSwgYnV0IGl0
IGRvZXNuJ3QgZ2l2ZSB1cyBtdWNoLiBUaGUgYXZhaWxhYmlsaXR5IGFzIGEgZ2l0aHViIHJlbGVh
c2UgaXMgZ29vZCBlbm91Z2ggZm9yIGRldmVsb3BtZW50LCBhbmQgdGhlICJvZmZpY2lhbCIgcGFj
a2FnZSBpcyBkZWxpdmVyZWQgdGhyb3VnaCBnb29nbGUgcGxheSBhbnl3YXk8L2Rpdj48ZGl2Pjxi
cj48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48ZGl2PjxkaXYgZGlyPSJsdHIiPjxkaXYgY2xhc3M9
ImdtYWlsX2V4dHJhIj48ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+PGRpdj4mbmJzcDs8L2Rpdj48
YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDti
b3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjxzcGFuIGNsYXNz
PSIiPjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgNC4gSGF2ZSBidWdzIHRyYWNrZWQgaW4gb1ZpcnQn
cyBidWd6aWxsYS48YnI+DQo8YnI+DQo8L3NwYW4+Tm88YnI+DQpUaGF0IHNob3VsZCBuZXZlciBi
ZSBpbXBvc2VkIG9uIGFueSBuZXcgcHJvamVjdC4gSWYgc29tZW9uZSBsb3ZlcyBzbG93IG91dGRh
dGVkIHRvb2xzLCBzbyBiZSBpdCwgYnV0IGZvciBuZXcgcHJvamVjdHMgSSBhZ2FpbiBkbyBub3Qg
c2VlIHVzIHByb21vdGluZyBpdCBpbiBmdXR1cmU8YnI+PC9ibG9ja3F1b3RlPjxkaXY+PGJyPjwv
ZGl2PjxkaXY+SSBhZ3JlZSB0aGlzIHBvaW50IGlzIGxlc3MgcmVsZXZhbnQsIGFuZCBlYWNoIHBy
b2plY3QgY2FuIGhhbmRsZSBoaXMgb3duIHRyYWNraW5nICggYnV0IGFnYWluLCBpZiBoZSB3aWxs
IHdhbnQgdG8gYmUgcmVsZWFzZWQgYXMgcGFydCBvZiBvVmlydCBhbmQgbm90IGluZGVwZW5kZW50
bHksIHRoZW4gSSdtIG5vdCBzdXJlIGhlJ2xsIGhhdmUgYSBjaG9pY2UgYnV0IHRvIGFsaWduICk8
L2Rpdj48L2Rpdj48L2Rpdj48L2Rpdj48L2Rpdj48L2Jsb2NrcXVvdGU+PGRpdj48YnI+PC9kaXY+
SSdtIG5vdCBzdXJlLCBJIGRvIHRoaW5rIHdlIHdpbGwgd2FudCB0byBtb3ZlIG9mZiBmb3IgbW9y
ZSBhbmQgbW9yZSBwYXJ0cyBvZiBvdmlydC4gSG93IHRvIGtlZXAgYSB1bmlmaWVkIGFwcHJvYWNo
IGlzIHRvIGJlIHNlZW4gaW5kZWVkLCB3ZSBjZXJ0YWlubHkgZG9uJ3Qgd2FudCB0byBkaXZlcnNl
IHRvbyBtdWNoLi4uLjwvZGl2PjxkaXY+PGJyPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxkaXY+
PGRpdiBkaXI9Imx0ciI+PGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPjxkaXYgY2xhc3M9ImdtYWls
X3F1b3RlIj48ZGl2PiZuYnNwOzwvZGl2PjxibG9ja3F1b3RlIGNsYXNzPSJnbWFpbF9xdW90ZSIg
c3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRp
bmctbGVmdDoxZXgiPg0KPHNwYW4gY2xhc3M9IiI+PGJyPg0KJmd0OyZndDsmZ3Q7PGJyPg0KJmd0
OyZndDsmZ3Q7IEZvciAxIGFuZCA0LCBJIGZlZWwgdGhhdCB0aGUgYmVuZWZpdCBvZiBhbGxvd2lu
ZyBzb21lIHByb2plY3RzIHRvIGJlIGhvc3RlZDxicj4NCiZndDsmZ3Q7Jmd0OyBvbiBHaXRIdWIg
KGF0dHJhY3QgJmFtcDsgaW52b2x2ZSBjb21tdW5pdHkgdGhyb3VnaCBHaXRIdWIncyBwdWJsaWMg
c2VydmljZSk8YnI+DQomZ3Q7Jmd0OyZndDsgZG9lczxicj4NCiZndDsmZ3Q7Jmd0OyBvdXQtd2Vp
Z2ggdGhlIHJ1bGUgb2Ygc3RyaWN0IGNvbnNpc3RlbmN5IChoYXZlIGV2ZXJ5dGhpbmcgaW4gb1Zp
cnQgR2Vycml0KS48YnI+DQomZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7
Jmd0OyBBbnkgcHJvamVjdCBpbiBvVmlydCBnZXJyaXQgY2FuIGJlIG1pcnJvcmVkIHRvIEdpdEh1
YiwgYW5kIG1vc3Qgb2YgdGhlbSBhcmU8YnI+DQomZ3Q7Jmd0OyAoIHNlZSA8YSBocmVmPSJodHRw
Oi8vZ2l0aHViLmNvbS9vVmlydCIgcmVsPSJub3JlZmVycmVyIiB0YXJnZXQ9Il9ibGFuayI+Z2l0
aHViLmNvbS9vVmlydDwvYT4gKTxicj4NCjxicj4NCjwvc3Bhbj5XZSBkbyBtaXJyb3IgaXQgSUlS
QyAob3IgaXQgbWF5IGhhdmUgYmVlbiBjb2NrcGl0LW92aXJ0KSwgaXQncyBqdXN0IHRoZSBvdGhl
ciB3YXkgYXJvdW5kIC0gdGhlIG1hc3RlciBjb3B5IGlzIGF0IGdpdGh1Yjxicj4NCjxzcGFuIGNs
YXNzPSIiPjxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsgQWx0
aG91Z2gsIG5vdCBzdXJlIGhvdyBoYXJkIHdvdWxkIGl0IGJlIHRvIG1vZGlmeSBvVmlydCBDSSBz
eXN0ZW0gdG8gYWxsb3c8YnI+DQomZ3Q7Jmd0OyZndDsgYnVpbGRpbmcgR2l0SHViIGhvc3RlZCBw
cm9qZWN0cy48YnI+DQomZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IFdl
IGFyZSBzdXBwb3J0aW5nIGl0LCBMYWdvIGlzIGFuIGV4YW1wbGUgb2Ygc3VjaCBwcm9qZWN0Ljxi
cj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0
OyZndDsgVGhlIGd1aWRlbGluZXMgc2hvdWxkIGJlIGNsZWFyIGFib3V0IHdoZXRoZXIgYSBwcm9q
ZWN0IG11c3QgYmUgaG9zdGVkIHZpYTxicj4NCiZndDsmZ3Q7Jmd0OyBvVmlydCBHZXJyaXQsIHdo
ZXRoZXIgaXQgbXVzdCBoYXZlIGl0cyBidWdzIHRyYWNrZWQgdmlhIG9WaXJ0IEJ1Z3ppbGxhLDxi
cj4NCiZndDsmZ3Q7Jmd0OyBldGMuPGJyPg0KJmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+
DQomZ3Q7Jmd0OyBJIGRvbid0IHRoaW5rIGl0cyBhIG11c3QsIGJ1dCBpdHMgaGlnaGx5IHJlY29t
bWVuZGVkIElNTywgYW5kIHdpbGwgaGVscCB0aGU8YnI+DQomZ3Q7Jmd0OyBwcm9qZWN0IGdyb3cu
PGJyPg0KJmd0OyZndDsgSW1hZ2luZSB0aGlzIHNjZW5hcmlvOjxicj4NCiZndDsmZ3Q7PGJyPg0K
Jmd0OyZndDsgdGhlIHByb2plY3QgZ3Jvd3MgYW5kIHVzZXMgaXRzIG93biBDSS90ZXN0aW5nIGZy
YW1ld29ya3MgYW5kIHJlYWNoZXMgYTxicj4NCiZndDsmZ3Q7IHBvaW50IGl0IHdhbnRzIHRvIGpv
aW4gdGhlIG9WaXJ0IGVjby1zeXN0ZW0sPGJyPg0KJmd0OyZndDsgQXQgdGhhdCBwb2ludCBpdCB3
aWxsIGJlIG11Y2ggaGFyZGVyIHRvIGludGVncmF0ZSBpdCBpZiBhdCBhbGwsIGFzc3VtaW5nPGJy
Pg0KJmd0OyZndDsgdGhlIHRvb2xzIGhlJ3MgYmVlbiB1c2luZyB3ZXJlIG5vdCBhbGlnbmVkIHdp
dGg8YnI+DQomZ3Q7Jmd0OyB0aGUgdG9vbGluZyBvdGhlciBwcm9qZWN0cyBhcmUgdXNpbmcuPGJy
Pg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyBBbHNvIC0gaW4gdGVybXMgb2YgcmVsZWFzZSBwcm9j
ZXNzLCBpdHMgd2lsbCBiZSB2ZXJ5IGhhcmQgdG8gaW5jbHVkZSBpdCBpbjxicj4NCiZndDsmZ3Q7
IGFuIG9mZmljaWFsIG9WaXJ0IHJlbGVhc2UgaWYgaGUgd2lzaGVzIHRvIGRvIHNvLDxicj4NCiZn
dDsmZ3Q7IGFzIGFsbCBvVmlydCBwcm9qZWN0cyBhcmUgYnVpbHQgaW4gdGhlIGN1cnJlbnQgaW5m
cmEgYW5kIHNoaXBwZWQgYXMgYTxicj4NCiZndDsmZ3Q7IHNpbmdsZSByZXBvc2l0b3J5Ljxicj4N
Cjxicj4NCjwvc3Bhbj5Zb3UncmUgbWlzc2luZyB0aGUgcG9pbnQgaXQncyBub3QgYSB5dW0gcmVw
by48YnI+PC9ibG9ja3F1b3RlPjxkaXY+PGJyPjwvZGl2PjxkaXY+U2VlIG15IGNvbW1lbnRzIGFi
b3ZlIG9uIHN1cHBvcnRpbmcgb3RoZXIgYXJ0aWZhY3RzIHRoYW4gcnBtcy4mbmJzcDs8L2Rpdj48
ZGl2Pjxicj48L2Rpdj48ZGl2PkkgdGhpbmsgeW91J3JlIG1pc3NpbmcgdGhlIHBvaW50IG9mIHRo
ZSBhZHZhbnRhZ2VzIHN1Y2ggYSBwcm9qZWN0IGNhbiBnZXQgYnkgam9pbmluZywgaW5zdGVhZCBv
ZiBtYW5hZ2luZyBpdHMgaW5mcmEgaGltc2VsZiAoIGlmIGl0IGhhcyBhbnkgKSw8L2Rpdj48ZGl2
Pkl0IGdldHMgYSBtYXNzaXZlIENJL0NEIGluZnJhc3RydWN0dXJlIGFscmVhZHkgYnVpbHQgYW5k
IHdvcmtpbmcsIGFuZCB3aWxsIGJlIGFibGUgdG8gZG8gaW50ZWdyYXRpb24gLyB0ZXN0aW5nIHdp
dGggYSByZWFsIG9WaXJ0IGluc3RhbmNlICh1c2luZyBPU1QgZm9yIGUuZykuPC9kaXY+PC9kaXY+
PC9kaXY+PC9kaXY+PC9kaXY+PC9ibG9ja3F1b3RlPjxkaXY+PGJyPjwvZGl2PkkgZG8gbm90IHNl
ZSBhIHByb2JsZW0gdG8gZG8gdGhhdCBvbmNlIHdlIGdldCB0aGF0IGZhci4gJm5ic3A7SSByZWFs
bHkgZG9uJ3QsIGJ1dCBjdXJyZW50bHkgaXQncyBwcmVtYXR1cmUuIFdlIGRvIG5vdCBoYXZlIGEg
c3VwcG9ydCwgd2UgZG8gbm90IGhhdmUgc3VjaCB0ZXN0cy4uLjwvZGl2PjxkaXY+PGJyPjwvZGl2
PjxkaXY+VGhhbmtzLDwvZGl2PjxkaXY+bWljaGFsPC9kaXY+PGRpdj48YnI+PGJsb2NrcXVvdGUg
dHlwZT0iY2l0ZSI+PGRpdj48ZGl2IGRpcj0ibHRyIj48ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+
PGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPjxkaXY+Jm5ic3A7PC9kaXY+PGJsb2NrcXVvdGUgY2xh
c3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4
ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+DQo8c3BhbiBjbGFzcz0iIj48YnI+DQomZ3Q7
PGJyPg0KJmd0OyBFeWFsLCBJIGFncmVlIHdpdGggeW91ciBwb2ludHMuPGJyPg0KJmd0Ozxicj4N
CiZndDsgSSBqdXN0IHdhbnRlZCB0byBwb2ludCBvdXQgdGhlIHBvc3NpYmlsaXR5IG9mIGhvc3Rp
bmcgcHJvamVjdCdzPGJyPg0KJmd0OyBzb3VyY2VzIG9uIEdpdEh1YiAocG9pbnQgMSBmcm9tIEJh
cmFrJ3MgbGlzdCkuIEFuZCBhcyB5b3Ugd3JvdGUsPGJyPg0KJmd0OyBMYWdvIGlzIGEgZ29vZCBl
eGFtcGxlIG9mIHN1Y2ggcHJvamVjdC48YnI+DQomZ3Q7PGJyPg0KJmd0OyBVc2luZyBzdGFuZGFy
ZCBvVmlydCBDSSBpbmZyYSAmYW1wOyB0b29scyAocG9pbnRzIDIgJmFtcDsgMyBmcm9tIEJhcmFr
J3M8YnI+DQomZ3Q7IGxpc3QpIHNob3VsZCBiZSBtYW5kYXRvcnkgZm9yIGFsbCBvVmlydCBwcm9q
ZWN0cywgdG8ga2VlcCB0aGluZ3M8YnI+DQomZ3Q7IG1hbmFnZWFibGUgZnJvbSBidWlsZC9yZWxl
YXNlIHBlcnNwZWN0aXZlLiBGdWxsIGFncmVlbWVudCBoZXJlLjxicj4NCiZndDs8YnI+DQomZ3Q7
IEFzIGZvciBidWcgdHJhY2tpbmcgKHBvaW50IDQgZnJvbSBCYXJhaydzIGxpc3QpLCBJIHNlZSBM
YWdvIHVzaW5nPGJyPg0KJmd0OyBHaXRIdWIncyBpc3N1ZSB0cmFja2luZyBpbnRlcmZhY2UsIHNv
IHRoaXMgc2hvdWxkIGJlIE9LIHRvby4uPGJyPg0KJmd0Ozxicj4NCiZndDsgSW4gZ2VuZXJhbCwg
SSdkIHNheSB0aGF0IG1vVmlydCBtYWludGFpbmVycyBzaG91bGQgY2xlYXJseSB2b2ljZTxicj4N
CiZndDsgdGhlaXIgdmlzaW9uIG9uIGNvbnZlcmdpbmcgKG9yIG5vdCkgdG93YXJkcyBwb2ludHMg
MSwyLDMsNCB0aGF0PGJyPg0KJmd0OyBCYXJhayBoYXMgbWVudGlvbmVkIGluIGhpcyBlbWFpbC48
YnI+DQo8YnI+DQo8L3NwYW4+SSB3b3VsZCBzYXkgbm8uIEFuZCB0aGF0IGlzIGZpbmU8YnI+DQo8
c3BhbiBjbGFzcz0iIj48YnI+DQomZ3Q7PGJyPg0KJmd0OyBGb3IgbWUsIGhhdmluZyBzb3VyY2Ug
Y29kZSAmYW1wOyBpc3N1ZXMgb24gR2l0SHViLCBidXQgdXNpbmcgc3RhbmRhcmQ8YnI+DQomZ3Q7
IG9WaXJ0IENJIGluZnJhICZhbXA7IHRvb2xzLCBpcyBzdGlsbCBhY2NlcHRhYmxlIGZvciBhbiBv
VmlydCBwcm9qZWN0LDxicj4NCiZndDsgYnV0IGl0J3MganVzdCBteSBvd24gb3Bpbmlvbi48YnI+
DQo8YnI+DQo8L3NwYW4+SSBhZ3JlZSB3ZSBjYW4gbWl4IGFuZCBtYXRjaCwgdGhvdWdoIGluIHRo
aXMgY2FzZSBJJ20gbm90IHN1cmUgaG93IHJlYWxpc3RpYyBpcyB0byBydW4gQ0kgZm9yIGFuIEFQ
Szxicj4NCjxkaXYgY2xhc3M9IkhPRW5aYiI+PGRpdiBjbGFzcz0iaDUiPjxicj48L2Rpdj48L2Rp
dj48L2Jsb2NrcXVvdGU+PGRpdj48YnI+PC9kaXY+PGRpdj5JJ20gcHJldHR5IHN1cmUgdGhhdCBp
ZiB3ZSB3YW50ZWQgdG8gY2hlY2sgdGhhdCBvcHRpb24sIGl0IHdpbGwgYmUgcG9zc2libGUgZXZl
biBpZiBieSB1c2luZyBlbXVsYXRvcnMsIGJ1dCBubyBvbmUgZnJvbSB0aGUgcHJvamVjdCBoYXMg
ZXZlciBhcHByb2FjaGVkIHVzIHNvIEkgY2FuJ3QgcmVhbGx5IHNheSBhbnl0aGluZyBiZWZvcmUg
SSBzZWUgcmVxdWlyZW1lbnRzLjwvZGl2PjxkaXY+SSB0ZW5kIG5vdCB0byBydWxlIG91dCBhbnl0
aGluZyBJIGhhdmVuJ3QgdmVyaWZpZWQgcG9zc2libGUgYmVmb3JlLjwvZGl2PjxkaXY+PGJyPjwv
ZGl2PjxkaXY+Jm5ic3A7PC9kaXY+PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHls
ZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1s
ZWZ0OjFleCI+PGRpdiBjbGFzcz0iSE9FblpiIj48ZGl2IGNsYXNzPSJoNSI+DQomZ3Q7PGJyPg0K
Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0
OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IE9uIDIxIE5vdmVtYmVyIDIwMTYgYXQgMTk6MDcs
IEJyaWFuIFByb2ZmaXR0ICZsdDs8YSBocmVmPSJtYWlsdG86YnByb2ZmaXRAcmVkaGF0LmNvbSI+
YnByb2ZmaXRAcmVkaGF0LmNvbTwvYT4mZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7IHdyb3RlOjxicj4N
CiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IEFsbDo8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4N
CiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFRoZSBtb1ZpcnQgUHJvamVjdCB3YXMgaW5pdGlhbGx5IGFj
Y2VwdGVkIGFzIGFuIG9WaXJ0IGluY3ViYXRvcjxicj4NCiZndDsmZ3Q7Jmd0OyBwcm9qZWN0IGlu
PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgRmVicnVhcnkgMjAxNS4gSXQgaGFzIGJlZW4gYSBz
dWNjZXNzZnVsIHN1YnByb2plY3QgZm9yIHF1aXRlIHNvbWUgdGltZTxicj4NCiZndDsmZ3Q7Jmd0
OyBhbmQ8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBpdCBpcyB3ZWxsIGR1ZSBmb3IgYmVpbmcg
YWNjZXB0ZWQgYXMgYSBmdWxsIG9WaXJ0IHByb2plY3QuIEkgYmVsaWV2ZTxicj4NCiZndDsmZ3Q7
Jmd0OyBpdCBpczxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGFwcHJvcHJpYXRlIHRvIHBvc3Qg
YSBDYWxsIGZvciBWb3RlIG9uIHRoZSBEZXZlbCBhbmQgQm9hcmQgbGlzdHMuPGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyA8YSBocmVmPSJodHRwOi8v
d3d3Lm92aXJ0Lm9yZy9kZXZlbG9wL3Byb2plY3RzL3Byb2plY3QtbW92aXJ0LyIgcmVsPSJub3Jl
ZmVycmVyIiB0YXJnZXQ9Il9ibGFuayI+aHR0cDovL3d3dy5vdmlydC5vcmcvZGV2ZWxvcC88d2Jy
PnByb2plY3RzL3Byb2plY3QtbW92aXJ0LzwvYT48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxi
cj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IEEg4oCcaGVhbHRoeeKAnSBwcm9qZWN0LCBhcyBkZXRl
cm1pbmVkIGJ5IHRoZSBvVmlydCBCb2FyZCwgY2FuIGJlIGZvdW5kIGF0PGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyZndDsgPGEgaHJlZj0iaHR0cDovL3d3dy5vdmlydC5vcmcvZGV2ZWxvcC9wcm9qZWN0
cy9hZGRpbmctYS1uZXctcHJvamVjdC8iIHJlbD0ibm9yZWZlcnJlciIgdGFyZ2V0PSJfYmxhbmsi
Pmh0dHA6Ly93d3cub3ZpcnQub3JnL2RldmVsb3AvPHdicj5wcm9qZWN0cy9hZGRpbmctYS1uZXct
cHJvamVjdC88L2E+PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyBWb3Rpbmcgd2lsbCBiZSBvcGVuIHVudGlsIDEyMDAgVVRDIE5vdi4gMzAsIDIwMTYu
IEEgbmV0IHRvdGFsIG9mICs3PGJyPg0KJmd0OyZndDsmZ3Q7IHZvdGVzPGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyZndDsgc2hvdWxkIGJlIHJlY2VpdmVkIHRvIGZvcm1hbGl6ZSB0aGlzIHByb2plY3Qg
YXMgYW4gZnVsbCBvVmlydCBwcm9qZWN0Ljxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFBsZWFz
ZSB1c2UgdGhlIGZvbGxvd2luZyB2b3RlIHByb2Nlc3M6PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZn
dDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyArMTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
IFllcywgYWdyZWUsIG9yIHRoZSBhY3Rpb24gc2hvdWxkIGJlIHBlcmZvcm1lZC4gT24gc29tZSBp
c3N1ZXMsIHRoaXM8YnI+DQomZ3Q7Jmd0OyZndDsgdm90ZTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7IG11c3Qgb25seSBiZSBnaXZlbiBhZnRlciB0aGUgdm90ZXIgaGFzIHRlc3RlZCB0aGUgYWN0
aW9uIG9uIHRoZWlyIG93bjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IHN5c3RlbShzKS48YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IMKxMDxicj4N
CiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IEFic3RhaW4sIG5vIG9waW5pb24sIG9yIEkgYW0gaGFwcHkg
dG8gbGV0IHRoZSBvdGhlciBncm91cCBtZW1iZXJzPGJyPg0KJmd0OyZndDsmZ3Q7IGRlY2lkZTxi
cj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IHRoaXMgaXNzdWUuIEFuIGFic3RlbnRpb24gbWF5IGhh
dmUgZGV0cmltZW50YWwgYWZmZWN0cyBpZiB0b28gbWFueTxicj4NCiZndDsmZ3Q7Jmd0OyBwZW9w
bGU8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBhYnN0YWluLjxicj4NCiZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgLTE8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyBObywgSSB2ZXRvIHRoaXMgYWN0aW9uLiBBbGwgdmV0b3MgbXVzdCBpbmNsdWRlIGFuIGV4
cGxhbmF0aW9uIG9mIHdoeTxicj4NCiZndDsmZ3Q7Jmd0OyB0aGU8YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyB2ZXRvIGlzIGFwcHJvcHJpYXRlLiBBIHZldG8gd2l0aCBubyBleHBsYW5hdGlvbiBp
cyB2b2lkLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZn
dDsgVGhhbmsgeW91ITxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7
Jmd0OyZndDsgQnJpYW4gUHJvZmZpdHQ8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBQcmluY2lw
YWwgQ29tbXVuaXR5IEFuYWx5c3Q8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBPcGVuIFNvdXJj
ZSBhbmQgU3RhbmRhcmRzPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgQFRoZVRlY2hTY3JpYmU8
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyA1NzQuMzgzLjlCS1A8YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXzx3YnI+X19fX19fX19fX19fX19fX188YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBE
ZXZlbCBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyA8YSBocmVmPSJtYWls
dG86RGV2ZWxAb3ZpcnQub3JnIj5EZXZlbEBvdmlydC5vcmc8L2E+PGJyPg0KJmd0OyZndDsmZ3Q7
Jmd0OyZndDsgPGEgaHJlZj0iaHR0cDovL2xpc3RzLm92aXJ0Lm9yZy9tYWlsbWFuL2xpc3RpbmZv
L2RldmVsIiByZWw9Im5vcmVmZXJyZXIiIHRhcmdldD0iX2JsYW5rIj5odHRwOi8vbGlzdHMub3Zp
cnQub3JnLzx3YnI+bWFpbG1hbi9saXN0aW5mby9kZXZlbDwvYT48YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7
Jmd0OyZndDsmZ3Q7IC0tPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyBCYXJhayBLb3JyZW48YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7IDxhIGhyZWY9Im1haWx0bzpia29ycmVuQHJlZGhhdC5jb20iPmJrb3Jy
ZW5AcmVkaGF0LmNvbTwvYT48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IFJIRVYtQ0kgVGVhbTxicj4N
CiZndDsmZ3Q7Jmd0OyZndDsgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPHdicj5fX19f
X19fX19fX19fX19fXzxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgRGV2ZWwgbWFpbGluZyBsaXN0PGJy
Pg0KJmd0OyZndDsmZ3Q7Jmd0OyA8YSBocmVmPSJtYWlsdG86RGV2ZWxAb3ZpcnQub3JnIj5EZXZl
bEBvdmlydC5vcmc8L2E+PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyA8YSBocmVmPSJodHRwOi8vbGlz
dHMub3ZpcnQub3JnL21haWxtYW4vbGlzdGluZm8vZGV2ZWwiIHJlbD0ibm9yZWZlcnJlciIgdGFy
Z2V0PSJfYmxhbmsiPmh0dHA6Ly9saXN0cy5vdmlydC5vcmcvPHdicj5tYWlsbWFuL2xpc3RpbmZv
L2RldmVsPC9hPjxicj4NCiZndDsmZ3Q7Jmd0OyBfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X188d2JyPl9fX19fX19fX19fX19fX19fPGJyPg0KJmd0OyZndDsmZ3Q7IERldmVsIG1haWxpbmcg
bGlzdDxicj4NCiZndDsmZ3Q7Jmd0OyA8YSBocmVmPSJtYWlsdG86RGV2ZWxAb3ZpcnQub3JnIj5E
ZXZlbEBvdmlydC5vcmc8L2E+PGJyPg0KJmd0OyZndDsmZ3Q7IDxhIGhyZWY9Imh0dHA6Ly9saXN0
cy5vdmlydC5vcmcvbWFpbG1hbi9saXN0aW5mby9kZXZlbCIgcmVsPSJub3JlZmVycmVyIiB0YXJn
ZXQ9Il9ibGFuayI+aHR0cDovL2xpc3RzLm92aXJ0Lm9yZy88d2JyPm1haWxtYW4vbGlzdGluZm8v
ZGV2ZWw8L2E+PGJyPg0KJmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZn
dDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IC0tPGJyPg0K
Jmd0OyZndDsgRXlhbCBFZHJpPGJyPg0KJmd0OyZndDsgQXNzb2NpYXRlIE1hbmFnZXI8YnI+DQom
Z3Q7Jmd0OyBSSFYgRGV2T3BzPGJyPg0KJmd0OyZndDsgRU1FQSBFTkcgVmlydHVhbGl6YXRpb24g
UiZhbXA7RDxicj4NCiZndDsmZ3Q7IFJlZCBIYXQgSXNyYWVsPGJyPg0KJmd0OyZndDs8YnI+DQom
Z3Q7Jmd0OyBwaG9uZTogPGEgaHJlZj0idGVsOiUyQjk3Mi05LTc2OTIwMTgiIHZhbHVlPSIrOTcy
OTc2OTIwMTgiPis5NzItOS03NjkyMDE4PC9hPjxicj4NCiZndDsmZ3Q7IGlyYzogZWVkcmkgKG9u
ICN0bHYgI3JoZXYtZGV2ICNyaGV2LWludGVnKTxicj4NCiZndDsmZ3Q7PGJyPg0KPC9kaXY+PC9k
aXY+PC9ibG9ja3F1b3RlPjwvZGl2Pjxicj48YnIgY2xlYXI9ImFsbCI+PGRpdj48YnI+PC9kaXY+
LS0gPGJyPjxkaXYgY2xhc3M9ImdtYWlsX3NpZ25hdHVyZSIgZGF0YS1zbWFydG1haWw9ImdtYWls
X3NpZ25hdHVyZSI+PGRpdiBkaXI9Imx0ciI+PGRpdj48ZGl2IGRpcj0ibHRyIj48ZGl2PjxkaXYg
ZGlyPSJsdHIiPjxkaXY+RXlhbCBFZHJpPGJyPkFzc29jaWF0ZSBNYW5hZ2VyPC9kaXY+PGRpdj5S
SFYgRGV2T3BzPGJyPkVNRUEgRU5HIFZpcnR1YWxpemF0aW9uIFImYW1wO0Q8YnI+UmVkIEhhdCBJ
c3JhZWw8YnI+PGJyPnBob25lOiArOTcyLTktNzY5MjAxODxicj5pcmM6IGVlZHJpIChvbiAjdGx2
ICNyaGV2LWRldiAjcmhldi1pbnRlZyk8L2Rpdj48L2Rpdj48L2Rpdj48L2Rpdj48L2Rpdj48L2Rp
dj48L2Rpdj4NCjwvZGl2PjwvZGl2Pg0KPC9kaXY+PC9ibG9ja3F1b3RlPjwvZGl2PjwvYm9keT48
L2h0bWw+
--Apple-Mail-ACF64B2F-A96E-4378-AC26-CB1DD2165EDA--
3 p.m.
On Mon, Nov 21, 2016 at 9:52 PM, Michal Skrivanek <mskrivan(a)redhat.com> wrote:
> On 21 Nov 2016, at 19:48, Vojtech Szocs <vszocs(a)redhat.com> wrote:
>
>
>
> ----- Original Message -----
>> From: "Eyal Edri" <eedri(a)redhat.com>
>> To: "Vojtech Szocs" <vszocs(a)redhat.com>
>> Cc: "Barak Korren" <bkorren(a)redhat.com>, "devel"
<devel(a)ovirt.org>, "board" <board(a)ovirt.org>, "Michal
Skrivanek"
>> <mskrivan(a)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 <vszocs(a)redhat.com>
wrote:
>>>
>>>
>>>
>>> ----- Original Message -----
>>>> From: "Barak Korren" <bkorren(a)redhat.com>
>>>> To: "Brian Proffitt" <bproffit(a)redhat.com>
>>>> Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>,
board(a)ovirt.org, "devel" <
>>> devel(a)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
>> 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.
You're missing the point it's not a yum repo.
>
> 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.
I would say no. And that is fine
>
> 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.
I agree we can mix and match, though in this case I'm not sure how realistic is to
run CI for an APK
>
>>
>>
>>>
>>>>
>>>> On 21 November 2016 at 19:07, Brian Proffitt <bproffit(a)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(a)ovirt.org
>>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>
>>>>
>>>>
>>>> --
>>>> Barak Korren
>>>> bkorren(a)redhat.com
>>>> RHEV-CI Team
>>>> _______________________________________________
>>>> Devel mailing list
>>>> Devel(a)ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>> _______________________________________________
>>> Devel mailing list
>>> Devel(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>
>>>
>>>
>>
>>
>> --
>> Eyal Edri
>> Associate Manager
>> RHV DevOps
>> EMEA ENG Virtualization R&D
>> Red Hat Israel
>>
>> phone: +972-9-7692018
>> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>>
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
2:08 a.m.
----- Original Message -----
From: "Nir Soffer" <nsoffer(a)redhat.com>
To: "Michal Skrivanek" <mskrivan(a)redhat.com>
Cc: "devel" <devel(a)ovirt.org>, "board" <board(a)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 <mskrivan(a)redhat.com>
wrote:
>
>
>> On 21 Nov 2016, at 19:48, Vojtech Szocs <vszocs(a)redhat.com> wrote:
>>
>>
>>
>> ----- Original Message -----
>>> From: "Eyal Edri" <eedri(a)redhat.com>
>>> To: "Vojtech Szocs" <vszocs(a)redhat.com>
>>> Cc: "Barak Korren" <bkorren(a)redhat.com>, "devel"
<devel(a)ovirt.org>,
>>> "board" <board(a)ovirt.org>, "Michal Skrivanek"
>>> <mskrivan(a)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
<vszocs(a)redhat.com>
>>>> wrote:
>>>>
>>>>
>>>>
>>>> ----- Original Message -----
>>>>> From: "Barak Korren" <bkorren(a)redhat.com>
>>>>> To: "Brian Proffitt" <bproffit(a)redhat.com>
>>>>> Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>,
board(a)ovirt.org, "devel"
>>>>> <
>>>> devel(a)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
2:12 a.m.
----- Original Message -----
From: "Nir Soffer" <nsoffer(a)redhat.com>
To: "Michal Skrivanek" <mskrivan(a)redhat.com>
Cc: "devel" <devel(a)ovirt.org>, "board" <board(a)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 <mskrivan(a)redhat.com>
wrote:
>
>
>> On 21 Nov 2016, at 19:48, Vojtech Szocs <vszocs(a)redhat.com> wrote:
>>
>>
>>
>> ----- Original Message -----
>>> From: "Eyal Edri" <eedri(a)redhat.com>
>>> To: "Vojtech Szocs" <vszocs(a)redhat.com>
>>> Cc: "Barak Korren" <bkorren(a)redhat.com>, "devel"
<devel(a)ovirt.org>,
>>> "board" <board(a)ovirt.org>, "Michal Skrivanek"
>>> <mskrivan(a)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
<vszocs(a)redhat.com>
>>>> wrote:
>>>>
>>>>
>>>>
>>>> ----- Original Message -----
>>>>> From: "Barak Korren" <bkorren(a)redhat.com>
>>>>> To: "Brian Proffitt" <bproffit(a)redhat.com>
>>>>> Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>,
board(a)ovirt.org, "devel"
>>>>> <
>>>> devel(a)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 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 combination of github for code and issue tracking + travis for simple CI
served us fantastically. I'm quite against moving to other place just because it may
bring
some benefits in the 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
>>> 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.
>
> You're missing the point it's not a yum repo.
>
>>
>> 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.
>
> I would say no. And that is fine
>
>>
>> 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.
>
> I agree we can mix and match, though in this case I'm not sure how
> realistic is to run CI for an APK
>
>>
>>>
>>>
>>>>
>>>>>
>>>>> On 21 November 2016 at 19:07, Brian Proffitt
<bproffit(a)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(a)ovirt.org
>>>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Barak Korren
>>>>> bkorren(a)redhat.com
>>>>> RHEV-CI Team
>>>>> _______________________________________________
>>>>> Devel mailing list
>>>>> Devel(a)ovirt.org
>>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>> _______________________________________________
>>>> Devel mailing list
>>>> Devel(a)ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Eyal Edri
>>> Associate Manager
>>> RHV DevOps
>>> EMEA ENG Virtualization R&D
>>> Red Hat Israel
>>>
>>> phone: +972-9-7692018
>>> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>>>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
2:18 a.m.
--Apple-Mail=_CD53A2B2-6F1F-4442-A54B-8A1D40B0D7BC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
On Nov 22, 2016, at 9:12 AM, Tomas Jelinek
<tjelinek(a)redhat.com> =
wrote:
=20
=20
=20
----- Original Message -----
> From: "Nir Soffer" <nsoffer(a)redhat.com>
> To: "Michal Skrivanek" <mskrivan(a)redhat.com>
> Cc: "devel" <devel(a)ovirt.org>, "board"
<board(a)ovirt.org>
> Sent: Monday, November 21, 2016 10:00:05 PM
> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt =
Project
>=20
> On Mon, Nov 21, 2016 at 9:52 PM, Michal Skrivanek =
<mskrivan(a)redhat.com>
> wrote:
>>=20
>>=20
>>> On 21 Nov 2016, at 19:48, Vojtech Szocs <vszocs(a)redhat.com> wrote:
>>>=20
>>>=20
>>>=20
>>> ----- Original Message -----
>>>> From: "Eyal Edri" <eedri(a)redhat.com>
>>>> To: "Vojtech Szocs" <vszocs(a)redhat.com>
>>>> Cc: "Barak Korren" <bkorren(a)redhat.com>,
"devel" =
<devel(a)ovirt.org>,
>>>> "board" <board(a)ovirt.org>,
"Michal Skrivanek"
>>>> <mskrivan(a)redhat.com>
>>>> Sent: Monday, November 21, 2016 7:23:44 PM
>>>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full oVirt =
Project
>>>>=20
>>>>> On Mon, Nov 21, 2016 at 8:17 PM, Vojtech Szocs =
<vszocs(a)redhat.com>
>>>>> wrote:
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> ----- Original Message -----
>>>>>> From: "Barak Korren" <bkorren(a)redhat.com>
>>>>>> To: "Brian Proffitt" <bproffit(a)redhat.com>
>>>>>> Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>,
board(a)ovirt.org, =
"devel"
>>>>>> <
>>>>> devel(a)ovirt.org>
>>>>>> Sent: Monday, November 21, 2016 7:01:08 PM
>>>>>> Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full =
oVirt
>>>>>> Project
>>>>>>=20
>>>>>> -1
>>=20
>> I wonder if 8x +1 beats one -1 :)
>=20
> 9X :-)
=20
adding my obviously biased +1, so not sure if it counts...
=20
>=20
> +1 for including the project as is.
>=20
> If someone wants to run the project test or build it, the right way
> to vote is by sending patches and making it happen.
>=20
> I think we should get out of our gerrit silo and move all ovirt
> projects to github. This will give ovirt much better visibility.
>=20
> 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/kubernetes/kubernetes>
=20
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>
=20
>=20
> Nir
>=20
>>=20
>>>>>> 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
>>=20
>> 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...
>>=20
>>>>>> 2. Have tests and builds running on oVirt's CI system.
>>=20
>> Can we run mobile testing on current infra?
=20
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
=20
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.
=20
>>=20
>>>>>> 3. Have artefacts served from oVirt's mirrors.
>>=20
>> What artifacts? The final APK? Why? It's not a yum repo.
=20
We need to serve them using google play store so it will reach the =
users
easily.=20
We could serve also RPM packaged APKs=20
or even create our alternative "something like play store" but Im not =
sure what benefits=20
it would bring us.
=20
>>=20
>>>>>> 4. Have bugs tracked in oVirt's bugzilla.
>>=20
>> 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
=20
+1
=20
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).=20
It needs a swift, stable, minimal and well known tooling around which
=
does exactly what we need.
The current combination of github for code and issue tracking +
travis =
for simple CI=20
served us fantastically. I'm quite against moving to other place
just =
because it may bring=20
some benefits in the future.
=20
>>=20
>>>>>=20
>>>>> 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).
>>>>>=20
>>>>>=20
>>>> Any project in oVirt gerrit can be mirrored to GitHub, and most of =
them
>>>> are
>>>> ( see github.com/oVirt )
>>=20
>> 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
>>=20
>>>>=20
>>>>=20
>>>>> Although, not sure how hard would it be to modify oVirt CI system =
to
>>>>> allow
>>>>> building GitHub hosted projects.
>>>>>=20
>>>>=20
>>>> We are supporting it, Lago is an example of such project.
>>>>=20
>>>>=20
>>>>>=20
>>>>> 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.
>>>>>=20
>>>>=20
>>>> I don't think its a must, but its highly recommended IMO, and will =
help
>>>> the
>>>> project grow.
>>>> Imagine this scenario:
>>>>=20
>>>> 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.
>>>>=20
>>>> 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.
>>=20
>> You're missing the point it's not a yum repo.
>>=20
>>>=20
>>> Eyal, I agree with your points.
>>>=20
>>> 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.
>>>=20
>>> 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.
>>>=20
>>> 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..
>>>=20
>>> 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.
>>=20
>> I would say no. And that is fine
>>=20
>>>=20
>>> 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.
>>=20
>> I agree we can mix and match, though in this case I'm not sure how
>> realistic is to run CI for an APK
>>=20
>>>=20
>>>>=20
>>>>=20
>>>>>=20
>>>>>>=20
>>>>>> On 21 November 2016 at 19:07, Brian Proffitt =
<bproffit(a)redhat.com>
>>>>> wrote:
>>>>>>> All:
>>>>>>>=20
>>>>>>> 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.
>>>>>>>=20
>>>>>>> http://www.ovirt.org/develop/projects/project-movirt/
>>>>>>>=20
>>>>>>> A =E2=80=9Chealthy=E2=80=9D project, as determined by the
oVirt =
Board, can be found at
>>>>>>>
http://www.ovirt.org/develop/projects/adding-a-new-project/
>>>>>>>=20
>>>>>>> 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:
>>>>>>>=20
>>>>>>> +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).
>>>>>>>=20
>>>>>>> =C2=B10
>>>>>>> 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.
>>>>>>>=20
>>>>>>> -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.
>>>>>>>=20
>>>>>>> Thank you!
>>>>>>>=20
>>>>>>> Brian Proffitt
>>>>>>> Principal Community Analyst
>>>>>>> Open Source and Standards
>>>>>>> @TheTechScribe
>>>>>>> 574.383.9BKP
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> Devel mailing list
>>>>>>> Devel(a)ovirt.org
>>>>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> --
>>>>>> Barak Korren
>>>>>> bkorren(a)redhat.com
>>>>>> RHEV-CI Team
>>>>>> _______________________________________________
>>>>>> Devel mailing list
>>>>>> Devel(a)ovirt.org
>>>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>> _______________________________________________
>>>>> Devel mailing list
>>>>> Devel(a)ovirt.org
>>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>>=20
>>>>>=20
>>>>>=20
>>>>=20
>>>>=20
>>>> --
>>>> Eyal Edri
>>>> Associate Manager
>>>> RHV DevOps
>>>> EMEA ENG Virtualization R&D
>>>> Red Hat Israel
>>>>=20
>>>> phone: +972-9-7692018
>>>> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>>>>=20
>> _______________________________________________
>> Devel mailing list
>> Devel(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel =
<http://lists.ovirt.org/mailman/listinfo/devel>
_______________________________________________
Devel mailing list
Devel(a)ovirt.org <mailto:Devel@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/devel =
<http://lists.ovirt.org/mailman/listinfo/devel>
--Apple-Mail=_CD53A2B2-6F1F-4442-A54B-8A1D40B0D7BC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"Content-Type"
content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote
type=3D"cite" class=3D""><div =
class=3D"">On Nov 22, 2016, at 9:12 AM, Tomas Jelinek <<a =
href=3D"mailto:tjelinek@redhat.com"
class=3D"">tjelinek(a)redhat.com</a>&gt;=
wrote:</div><br class=3D"Apple-interchange-newline"><div
class=3D""><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica;
font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">----- Original Message
-----</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><blockquote
type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">From: "Nir Soffer" <<a
href=3D"mailto:nsoffer@redhat.com" =
class=3D"">nsoffer(a)redhat.com</a>&gt;<br
class=3D"">To: "Michal =
Skrivanek" <<a href=3D"mailto:mskrivan@redhat.com" =
class=3D"">mskrivan(a)redhat.com</a>&gt;<br
class=3D"">Cc: "devel" <<a =
href=3D"mailto:devel@ovirt.org"
class=3D"">devel(a)ovirt.org</a>&gt;, =
"board" <<a href=3D"mailto:board@ovirt.org" =
class=3D"">board(a)ovirt.org</a>&gt;<br
class=3D"">Sent: Monday, November =
21, 2016 10:00:05 PM<br class=3D"">Subject: Re: [ovirt-devel] [Call for =
Vote] moVirt as a Full oVirt Project<br class=3D""><br
class=3D"">On =
Mon, Nov 21, 2016 at 9:52 PM, Michal Skrivanek <<a =
href=3D"mailto:mskrivan@redhat.com" =
class=3D"">mskrivan(a)redhat.com</a>&gt;<br
class=3D"">wrote:<br =
class=3D""><blockquote type=3D"cite"
class=3D""><br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">On
21 Nov 2016, at =
19:48, Vojtech Szocs <<a href=3D"mailto:vszocs@redhat.com" =
class=3D"">vszocs(a)redhat.com</a>&gt; wrote:<br
class=3D""><br =
class=3D""><br class=3D""><br
class=3D"">----- Original Message -----<br =
class=3D""><blockquote type=3D"cite"
class=3D"">From: "Eyal Edri" <<a =
href=3D"mailto:eedri@redhat.com"
class=3D"">eedri(a)redhat.com</a>&gt;<br =
class=3D"">To: "Vojtech Szocs" <<a
href=3D"mailto:vszocs@redhat.com" =
class=3D"">vszocs(a)redhat.com</a>&gt;<br
class=3D"">Cc: "Barak Korren" =
<<a href=3D"mailto:bkorren@redhat.com" =
class=3D"">bkorren(a)redhat.com</a>&gt;, "devel"
<<a =
href=3D"mailto:devel@ovirt.org"
class=3D"">devel(a)ovirt.org</a>&gt;,<br =
class=3D"">"board" <<a
href=3D"mailto:board@ovirt.org" =
class=3D"">board(a)ovirt.org</a>&gt;, "Michal
Skrivanek"<br =
class=3D""><<a href=3D"mailto:mskrivan@redhat.com" =
class=3D"">mskrivan(a)redhat.com</a>&gt;<br
class=3D"">Sent: Monday, =
November 21, 2016 7:23:44 PM<br class=3D"">Subject: Re: [ovirt-devel] =
[Call for Vote] moVirt as a Full oVirt Project<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">On
Mon, Nov 21, 2016 at =
8:17 PM, Vojtech Szocs <<a href=3D"mailto:vszocs@redhat.com" =
class=3D"">vszocs(a)redhat.com</a>&gt;<br
class=3D"">wrote:<br =
class=3D""><br class=3D""><br
class=3D""><br class=3D"">----- Original =
Message -----<br class=3D""><blockquote type=3D"cite"
class=3D"">From: =
"Barak Korren" <<a href=3D"mailto:bkorren@redhat.com" =
class=3D"">bkorren(a)redhat.com</a>&gt;<br
class=3D"">To: "Brian Proffitt" =
<<a href=3D"mailto:bproffit@redhat.com" =
class=3D"">bproffit(a)redhat.com</a>&gt;<br
class=3D"">Cc: "Michal =
Skrivanek" <<a href=3D"mailto:mskrivan@redhat.com" =
class=3D"">mskrivan(a)redhat.com</a>&gt;, <a
href=3D"mailto:board@ovirt.org"=
class=3D"">board(a)ovirt.org</a>, "devel"<br
class=3D""><<br =
class=3D""></blockquote><a href=3D"mailto:devel@ovirt.org"
=
class=3D"">devel(a)ovirt.org</a>&gt;<br
class=3D""><blockquote type=3D"cite"=
class=3D"">Sent: Monday, November 21, 2016 7:01:08 PM<br =
class=3D"">Subject: Re: [ovirt-devel] [Call for Vote] moVirt as a Full =
oVirt<br class=3D"">Project<br class=3D""><br
class=3D"">-1<br =
class=3D""></blockquote></blockquote></blockquote></blockquote><br
=
class=3D"">I wonder if 8x +1 beats one -1 :)<br =
class=3D""></blockquote><br class=3D"">9X :-)<br =
class=3D""></blockquote><br style=3D"font-family: Helvetica;
font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"
class=3D""><span=
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">adding my obviously biased +1, so not sure if it
=
counts...</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><blockquote
type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D""><br class=3D"">+1 for including the project as
is.<br =
class=3D""><br class=3D"">If someone wants to run the project
test or =
build it, the right way<br class=3D"">to vote is by sending patches and =
making it happen.<br class=3D""><br class=3D"">I think we
should get out =
of our gerrit silo and move all ovirt<br class=3D"">projects to github. =
This will give ovirt much better visibility.<br class=3D""><br =
class=3D"">Here are some projects developed on github:<br
class=3D""><a =
href=3D"https://github.com/systemd/systemd" =
class=3D"">https://github.com/systemd/systemd</a><br
class=3D""><a =
href=3D"https://github.com/rust-lang/rust/" =
class=3D"">https://github.com/rust-lang/rust/</a><br
class=3D""><a =
href=3D"https://github.com/kubernetes/kubernetes" =
class=3D"">https://github.com/kubernetes/kubernetes</a>... =
class=3D""></blockquote><br style=3D"font-family: Helvetica;
font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"
class=3D""><span=
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">I would add also<span =
class=3D"Apple-converted-space"> </span></span><a =
href=3D"https://github.com/ManageIQ/" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://github.com/ManageIQ/</a><span
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D""><span =
class=3D"Apple-converted-space"> </span>which we as oVirt
devels =
are contributing to regularly.</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""></div></blockquote><div><br
class=3D""></div><div><a =
href=3D"https://github.com/cockpit-project/cockpit" =
class=3D"">https://github.com/cockpit-project/cockpit</a&...
=
href=3D"https://github.com/OpenShift" =
class=3D"">https://github.com/OpenShift</a></div>...
=
class=3D""></div><br class=3D""><blockquote
type=3D"cite" class=3D""><div =
class=3D""><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;"
class=3D""><blockquote=
type=3D"cite" style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D""><br
class=3D"">Nir<br =
class=3D""><br class=3D""><blockquote
type=3D"cite" class=3D""><br =
class=3D""><blockquote type=3D"cite"
class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite"
class=3D""><blockquote type=3D"cite" =
class=3D"">Not because of anything with the project itself - I think it =
is<br class=3D"">genuinely awesome, but because I expect a project that =
emerges out of<br class=3D"">the incubation process to "look"
like an =
oVirt project, by which I<br class=3D"">mean:<br
class=3D"">1. Have the =
code in the oVirt Gerrit<br =
class=3D""></blockquote></blockquote></blockquote></blockquote><br
=
class=3D"">I wonder why that would be required. We experimented with =
other projects<br class=3D"">being off gerrit as well(e.g. =
cockpit-ovirt) and bug tracking out of<br class=3D"">redhat bugzilla and
=
for certain projcts it makes sense. With more<br class=3D"">integration =
with other upstream projects I see us moving to github even<br =
class=3D"">more...<br class=3D""><br
class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite"
class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">2.
Have tests and builds =
running on oVirt's CI system.<br =
class=3D""></blockquote></blockquote></blockquote></blockquote><br
=
class=3D"">Can we run mobile testing on current infra?<br =
class=3D""></blockquote></blockquote><br
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica;
font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">We are using travis for this. Our =
complete config file is:</span><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">language: android</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">script:
"./gradlew =
build"</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span
=
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">android:</span><br
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica;
font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D""> components:</span><br
=
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;"
class=3D""> - =
platforms-tools</span><br style=3D"font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"
class=3D""><span=
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D""> -
tools</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;"
class=3D""> - =
build-tools-21.1.2</span><br style=3D"font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"
class=3D""><span=
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D""> -
android-21</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica;
font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">We don't have any additional tooling
=
developed or anything like that.</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica;
font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">If we will start thinking about doing =
some custom/complicated stuff, we</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica;
font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">may consider moving to ovirt's CI. =
Currently, I don't see a reason.</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><br style=3D"font-family: Helvetica; font-size:
12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;"
class=3D""><blockquote=
type=3D"cite" style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D""><blockquote
type=3D"cite" =
class=3D""><br class=3D""><blockquote
type=3D"cite" class=3D""><blockquote=
type=3D"cite" class=3D""><blockquote type=3D"cite"
class=3D""><blockquote=
type=3D"cite" class=3D"">3. Have artefacts served from oVirt's
=
mirrors.<br =
class=3D""></blockquote></blockquote></blockquote></blockquote><br
=
class=3D"">What artifacts? The final APK? Why? It's not a yum repo.<br
=
class=3D""></blockquote></blockquote><br
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica;
font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">We need to serve them using google play
=
store so it will reach the users easily.<span =
class=3D"Apple-converted-space"> </span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">We could serve also
=
RPM packaged APKs<span =
class=3D"Apple-converted-space"> </span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">or even create our
=
alternative "something like play store" but Im not sure what =
benefits<span
class=3D"Apple-converted-space"> </span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">it would bring =
us.</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><blockquote
type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite"
class=3D""><br class=3D""><blockquote=
type=3D"cite" class=3D""><blockquote type=3D"cite"
class=3D""><blockquote=
type=3D"cite" class=3D""><blockquote type=3D"cite"
class=3D"">4. Have =
bugs tracked in oVirt's bugzilla.<br =
class=3D""></blockquote></blockquote></blockquote></blockquote><br
=
class=3D"">No<br class=3D"">That should never be imposed on
any new =
project. If someone loves slow<br class=3D"">outdated tools, so be it, =
but for new projects I again do not see us<br class=3D"">promoting it in
=
future<br class=3D""></blockquote></blockquote><br
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica;
font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">+1</span><br
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><br style=3D"font-family: Helvetica; font-size:
12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span
=
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Well, long story short, moVirt is a simple small
=
tool developed by a very small team</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica;
font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">and occasionally contributed by community
=
(mostly as outreachy interns or intern candidates).<span =
class=3D"Apple-converted-space"> </span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">It needs a swift,
=
stable, minimal and well known tooling around which does exactly what we =
need.</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span
=
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">The current combination of github for code and
=
issue tracking + travis for simple CI<span =
class=3D"Apple-converted-space"> </span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">served us =
fantastically. I'm quite against moving to other place just because it =
may bring<span
class=3D"Apple-converted-space"> </span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">some benefits in =
the future.</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><blockquote
type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite"
class=3D""><br class=3D""><blockquote=
type=3D"cite" class=3D""><blockquote type=3D"cite"
class=3D""><blockquote=
type=3D"cite" class=3D""><br class=3D"">For 1 and
4, I feel that the =
benefit of allowing some projects to be<br class=3D"">hosted<br =
class=3D"">on GitHub (attract & involve community through
GitHub's =
public service)<br class=3D"">does<br class=3D"">out-weigh
the rule of =
strict consistency (have everything in oVirt<br class=3D"">Gerrit).<br
=
class=3D""><br class=3D""><br
class=3D""></blockquote>Any project in =
oVirt gerrit can be mirrored to GitHub, and most of them<br =
class=3D"">are<br class=3D"">( see <a
href=3D"http://github.com/oVirt" =
class=3D"">github.com/oVirt</a> )<br =
class=3D""></blockquote></blockquote><br
class=3D"">We do mirror it IIRC =
(or it may have been cockpit-ovirt), it's just the<br class=3D"">other
=
way around - the master copy is at github<br class=3D""><br =
class=3D""><blockquote type=3D"cite"
class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D""><br
class=3D""><blockquote type=3D"cite" =
class=3D"">Although, not sure how hard would it be to modify oVirt CI =
system to<br class=3D"">allow<br class=3D"">building
GitHub hosted =
projects.<br class=3D""><br
class=3D""></blockquote><br class=3D"">We =
are supporting it, Lago is an example of such project.<br
class=3D""><br =
class=3D""><br class=3D""><blockquote
type=3D"cite" class=3D""><br =
class=3D"">The guidelines should be clear about whether a project must =
be hosted<br class=3D"">via<br class=3D"">oVirt Gerrit,
whether it must =
have its bugs tracked via oVirt Bugzilla,<br class=3D"">etc.<br =
class=3D""><br class=3D""></blockquote><br
class=3D"">I don't think its =
a must, but its highly recommended IMO, and will help<br
class=3D"">the<br=
class=3D"">project grow.<br class=3D"">Imagine this
scenario:<br =
class=3D""><br class=3D"">the project grows and uses its own
CI/testing =
frameworks and reaches a<br class=3D"">point it wants to join the oVirt =
eco-system,<br class=3D"">At that point it will be much harder to =
integrate it if at all, assuming<br class=3D"">the tools he's been
using =
were not aligned with<br class=3D"">the tooling other projects are =
using.<br class=3D""><br class=3D"">Also - in terms of
release process, =
its will be very hard to include it<br class=3D"">in<br
class=3D"">an =
official oVirt release if he wishes to do so,<br class=3D"">as all oVirt
=
projects are built in the current infra and shipped as a<br =
class=3D"">single repository.<br
class=3D""></blockquote></blockquote><br =
class=3D"">You're missing the point it's not a yum repo.<br
class=3D""><br=
class=3D""><blockquote type=3D"cite"
class=3D""><br class=3D"">Eyal, I =
agree with your points.<br class=3D""><br class=3D"">I
just wanted to =
point out the possibility of hosting project's<br class=3D"">sources
on =
GitHub (point 1 from Barak's list). And as you wrote,<br
class=3D"">Lago =
is a good example of such project.<br class=3D""><br
class=3D"">Using =
standard oVirt CI infra & tools (points 2 & 3 from Barak's<br =
class=3D"">list) should be mandatory for all oVirt projects, to keep =
things<br class=3D"">manageable from build/release perspective. Full =
agreement here.<br class=3D""><br class=3D"">As for bug
tracking (point =
4 from Barak's list), I see Lago using<br class=3D"">GitHub's
issue =
tracking interface, so this should be OK too..<br class=3D""><br =
class=3D"">In general, I'd say that moVirt maintainers should clearly =
voice<br class=3D"">their vision on converging (or not) towards points =
1,2,3,4 that<br class=3D"">Barak has mentioned in his email.<br =
class=3D""></blockquote><br class=3D"">I would say no.
And that is =
fine<br class=3D""><br class=3D""><blockquote
type=3D"cite" class=3D""><br=
class=3D"">For me, having source code & issues on GitHub, but using
=
standard<br class=3D"">oVirt CI infra & tools, is still acceptable
=
for an oVirt project,<br class=3D"">but it's just my own
opinion.<br =
class=3D""></blockquote><br class=3D"">I agree we can
mix and match, =
though in this case I'm not sure how<br class=3D"">realistic is to run
=
CI for an APK<br class=3D""><br class=3D""><blockquote
type=3D"cite" =
class=3D""><br class=3D""><blockquote
type=3D"cite" class=3D""><br =
class=3D""><br class=3D""><blockquote
type=3D"cite" class=3D""><br =
class=3D""><blockquote type=3D"cite"
class=3D""><br class=3D"">On 21 =
November 2016 at 19:07, Brian Proffitt <<a =
href=3D"mailto:bproffit@redhat.com" =
class=3D"">bproffit(a)redhat.com</a>&gt;<br =
class=3D""></blockquote>wrote:<br
class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite"
class=3D"">All:<br class=3D""><br =
class=3D"">The moVirt Project was initially accepted as an oVirt =
incubator<br class=3D""></blockquote></blockquote>project
in<br =
class=3D""><blockquote type=3D"cite"
class=3D""><blockquote type=3D"cite" =
class=3D"">February 2015. It has been a successful subproject for quite =
some time<br class=3D""></blockquote></blockquote>and<br =
class=3D""><blockquote type=3D"cite"
class=3D""><blockquote type=3D"cite" =
class=3D"">it is well due for being accepted as a full oVirt project. I =
believe<br class=3D""></blockquote></blockquote>it is<br =
class=3D""><blockquote type=3D"cite"
class=3D""><blockquote type=3D"cite" =
class=3D"">appropriate to post a Call for Vote on the Devel and Board =
lists.<br class=3D""><br class=3D""><a =
href=3D"http://www.ovirt.org/develop/projects/project-movirt/" =
class=3D"">http://www.ovirt.org/develop/projects/project-mov...
=
class=3D""><br class=3D"">A =E2=80=9Chealthy=E2=80=9D
project, as =
determined by the oVirt Board, can be found at<br =
class=3D"">http://www.ovirt.org/develop/projects/adding-a-ne...
=
class=3D""><br class=3D"">Voting will be open until 1200 UTC
Nov. 30, =
2016. A net total of +7<br
class=3D""></blockquote></blockquote>votes<br =
class=3D""><blockquote type=3D"cite"
class=3D""><blockquote type=3D"cite" =
class=3D"">should be received to formalize this project as an full oVirt =
project.<br class=3D"">Please use the following vote process:<br =
class=3D""><br class=3D"">+1<br
class=3D"">Yes, agree, or the action =
should be performed. On some issues, this<br =
class=3D""></blockquote></blockquote>vote<br
class=3D""><blockquote =
type=3D"cite" class=3D""><blockquote type=3D"cite"
class=3D"">must only =
be given after the voter has tested the action on their own<br =
class=3D"">system(s).<br class=3D""><br
class=3D"">=C2=B10<br =
class=3D"">Abstain, no opinion, or I am happy to let the other group =
members<br class=3D""></blockquote></blockquote>decide<br
=
class=3D""><blockquote type=3D"cite"
class=3D""><blockquote type=3D"cite" =
class=3D"">this issue. An abstention may have detrimental affects if too =
many<br class=3D""></blockquote></blockquote>people<br =
class=3D""><blockquote type=3D"cite"
class=3D""><blockquote type=3D"cite" =
class=3D"">abstain.<br class=3D""><br
class=3D"">-1<br class=3D"">No, I =
veto this action. All vetos must include an explanation of why<br =
class=3D""></blockquote></blockquote>the<br
class=3D""><blockquote =
type=3D"cite" class=3D""><blockquote type=3D"cite"
class=3D"">veto is =
appropriate. A veto with no explanation is void.<br class=3D""><br =
class=3D"">Thank you!<br class=3D""><br
class=3D"">Brian Proffitt<br =
class=3D"">Principal Community Analyst<br class=3D"">Open
Source and =
Standards<br class=3D"">@TheTechScribe<br
class=3D"">574.383.9BKP<br =
class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">Devel mailing list<br class=3D""><a =
href=3D"mailto:Devel@ovirt.org"
class=3D"">Devel(a)ovirt.org</a><br =
class=3D"">http://lists.ovirt.org/mailman/listinfo/devel<br =
class=3D""></blockquote><br class=3D""><br
class=3D""><br class=3D"">--<br=
class=3D"">Barak Korren<br class=3D""><a =
href=3D"mailto:bkorren@redhat.com"
class=3D"">bkorren(a)redhat.com</a><br =
class=3D"">RHEV-CI Team<br =
class=3D"">_______________________________________________<br =
class=3D"">Devel mailing list<br
class=3D"">Devel(a)ovirt.org<br =
class=3D"">http://lists.ovirt.org/mailman/listinfo/devel<br =
class=3D""></blockquote>_______________________________________________<br=
class=3D"">Devel mailing list<br class=3D""><a =
href=3D"mailto:Devel@ovirt.org"
class=3D"">Devel(a)ovirt.org</a><br =
class=3D"">http://lists.ovirt.org/mailman/listinfo/devel<br
class=3D""><br=
class=3D""><br class=3D""><br
class=3D""></blockquote><br class=3D""><br =
class=3D"">--<br class=3D"">Eyal Edri<br
class=3D"">Associate Manager<br =
class=3D"">RHV DevOps<br class=3D"">EMEA ENG Virtualization
R&D<br =
class=3D"">Red Hat Israel<br class=3D""><br
class=3D"">phone: =
+972-9-7692018<br class=3D"">irc: eedri (on #tlv #rhev-dev =
#rhev-integ)<br class=3D""><br =
class=3D""></blockquote></blockquote>_____________________________________=
__________<br class=3D"">Devel mailing list<br
class=3D""><a =
href=3D"mailto:Devel@ovirt.org"
class=3D"">Devel(a)ovirt.org</a><br =
class=3D"">http://lists.ovirt.org/mailman/listinfo/devel<br =
class=3D""></blockquote>_______________________________________________<br=
class=3D"">Devel mailing list<br class=3D""><a =
href=3D"mailto:Devel@ovirt.org"
class=3D"">Devel(a)ovirt.org</a><br =
class=3D""><a
href=3D"http://lists.ovirt.org/mailman/listinfo/devel" =
class=3D"">http://lists.ovirt.org/mailman/listinfo/devel<... =
class=3D""></blockquote><span style=3D"font-family: Helvetica;
=
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: =
none; display: inline !important;" =
class=3D"">_______________________________________________</span><br
=
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span
style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">Devel mailing =
list</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><a =
href=3D"mailto:Devel@ovirt.org" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;"
class=3D"">Devel(a)ovirt.org</a><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><a =
href=3D"http://lists.ovirt.org/mailman/listinfo/devel" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">http://lists.ovirt.org/mailman/listinfo/devel<...
uote></div><br class=3D""></body></html>=
--Apple-Mail=_CD53A2B2-6F1F-4442-A54B-8A1D40B0D7BC--
2:25 a.m.
+1
On Tue, Nov 22, 2016 at 9:18 AM, Vinzenz Feenstra <vfeenstr(a)redhat.com> wrote:
On Nov 22, 2016, at 9:12 AM, Tomas Jelinek <tjelinek(a)redhat.com> wrote:
----- Original Message -----
From: "Nir Soffer" <nsoffer(a)redhat.com>
To: "Michal Skrivanek" <mskrivan(a)redhat.com>
Cc: "devel" <devel(a)ovirt.org>, "board" <board(a)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 <mskrivan(a)redhat.com>
wrote:
On 21 Nov 2016, at 19:48, Vojtech Szocs <vszocs(a)redhat.com> wrote:
----- Original Message -----
From: "Eyal Edri" <eedri(a)redhat.com>
To: "Vojtech Szocs" <vszocs(a)redhat.com>
Cc: "Barak Korren" <bkorren(a)redhat.com>, "devel"
<devel(a)ovirt.org>,
"board" <board(a)ovirt.org>, "Michal Skrivanek"
<mskrivan(a)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 <vszocs(a)redhat.com>
wrote:
----- Original Message -----
From: "Barak Korren" <bkorren(a)redhat.com>
To: "Brian Proffitt" <bproffit(a)redhat.com>
Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>, board(a)ovirt.org,
"devel"
<
devel(a)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 combination of github for code and issue tracking + travis for
simple CI
served us fantastically. I'm quite against moving to other place just
because it may bring
some benefits in the 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
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.
You're missing the point it's not a yum repo.
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.
I would say no. And that is fine
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.
I agree we can mix and match, though in this case I'm not sure how
realistic is to run CI for an APK
On 21 November 2016 at 19:07, Brian Proffitt <bproffit(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
Barak Korren
bkorren(a)redhat.com
RHEV-CI Team
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
2:10 a.m.
--Apple-Mail=_D62EDD54-71A6-4B5C-B1FD-1996336D5FDE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
+1
On Nov 21, 2016, at 6:07 PM, Brian Proffitt
<bproffit(a)redhat.com> =
wrote:
=20
All:
=20
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.=20
<http://www.ovirt.org/develop/projects/project-movirt/>
=20
A =E2=80=9Chealthy=E2=80=9D project, as determined by the oVirt Board, =
can be
found at =
http://www.ovirt.org/develop/projects/adding-a-new-project/ =
<http://www.ovirt.org/develop/projects/adding-a-new-project/>
=20
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:
=20
+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).
=20
=C2=B10
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.
=20
-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.
=20
Thank you!
=20
Brian Proffitt
Principal Community Analyst
Open Source and Standards
@TheTechScribe
574.383.9BKP
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--Apple-Mail=_D62EDD54-71A6-4B5C-B1FD-1996336D5FDE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"Content-Type"
content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">+1<div class=3D""><br
class=3D""><div><blockquote type=3D"cite"=
class=3D""><div class=3D"">On Nov 21, 2016, at 6:07 PM,
Brian Proffitt =
<<a href=3D"mailto:bproffit@redhat.com" =
class=3D"">bproffit(a)redhat.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div
dir=3D"ltr" =
class=3D""><div class=3D""><span
style=3D"font-size:12.8px" =
class=3D"">All:</span></div><div
class=3D""><span =
style=3D"font-size:12.8px" class=3D""><br
class=3D""></span></div><div =
class=3D""><span style=3D"font-size:12.8px"
class=3D"">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 </span><span =
style=3D"font-size:12.8px" class=3D"">believe it is
appropriate to =
post a Call for Vote on the Devel and Board =
lists. </span></div><div class=3D""><span
style=3D"font-size:12.8px" =
class=3D""><br class=3D""></span></div><div
class=3D""><span =
style=3D"font-size:12.8px" class=3D""><a =
href=3D"http://www.ovirt.org/develop/projects/project-movirt/" =
class=3D"">http://www.ovirt.org/develop/projects/project-mov...
<br class=3D""></div><div
class=3D""><span style=3D"font-size:12.8px" =
class=3D""><br
class=3D""></span></div><div class=3D""><span
=
style=3D"font-size:12.8px" class=3D"">A =E2=80=9Chealthy=E2=80=9D
=
project, as determined by the oVirt Board, can be found at <a =
href=3D"http://www.ovirt.org/develop/projects/adding-a-new-project/&... =
class=3D"">http://www.ovirt.org/develop/projects/adding-a-ne...
<br class=3D""></span></div><div
class=3D""><span =
style=3D"font-size:12.8px" class=3D""><br
class=3D""></span></div><div =
class=3D""><span style=3D"font-size:12.8px"
class=3D"">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:</span></div><div
class=3D""><span =
style=3D"font-size:12.8px" class=3D""><br
class=3D""></span></div>+1<div =
class=3D"">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).<br class=3D""><br
class=3D"">=C2=B10</div><=
div class=3D"">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.<br class=3D""><br
class=3D"">-1</div><div =
class=3D"">No, I veto this action. All vetos must include an explanation =
of why the veto is appropriate. A veto with no explanation is =
void.</div><div class=3D""><br
class=3D""></div><div class=3D"">Thank =
you!</div><div class=3D""><br
class=3D""></div><div class=3D"">Brian =
Proffitt</div><div class=3D"gmail_signature"><div
dir=3D"ltr" =
class=3D""><div class=3D"">Principal Community
Analyst</div><div =
class=3D"">Open Source and Standards</div><div =
class=3D"">@TheTechScribe</div><div =
class=3D"">574.383.9BKP</div></div></div>
</div>
_______________________________________________<br class=3D"">Devel =
mailing list<br class=3D""><a href=3D"mailto:Devel@ovirt.org"
=
class=3D"">Devel(a)ovirt.org</a><br =
class=3D"">http://lists.ovirt.org/mailman/listinfo/devel<...
</div><br
class=3D""></div></body></html>=
--Apple-Mail=_D62EDD54-71A6-4B5C-B1FD-1996336D5FDE--
2:30 a.m.
+1
On Mon, Nov 21, 2016 at 6:07 PM, Brian Proffitt <bproffit(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
3:02 a.m.
+1
----- Original Message -----
From: "Roman Mohr" <rmohr(a)redhat.com>
To: "Brian Proffitt" <bproffit(a)redhat.com>
Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>, board(a)ovirt.org,
"devel" <devel(a)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 < bproffit(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
6:23 a.m.
Brian, Board, I think we have enough +1.
On Tue, Nov 22, 2016 at 10:02 AM, Jakub Niedermertl <jniederm(a)redhat.com>
wrote:
+1
----- Original Message -----
> From: "Roman Mohr" <rmohr(a)redhat.com>
> To: "Brian Proffitt" <bproffit(a)redhat.com>
> Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>, board(a)ovirt.org,
"devel" <
devel(a)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 < bproffit(a)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(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel(a)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
6:48 a.m.
+1
On Tue, Nov 29, 2016 at 2:23 PM, Sandro Bonazzola <sbonazzo(a)redhat.com>
wrote:
Brian, Board, I think we have enough +1.
On Tue, Nov 22, 2016 at 10:02 AM, Jakub Niedermertl <jniederm(a)redhat.com>
wrote:
> +1
>
> ----- Original Message -----
> > From: "Roman Mohr" <rmohr(a)redhat.com>
> > To: "Brian Proffitt" <bproffit(a)redhat.com>
> > Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>, board(a)ovirt.org,
"devel"
> <devel(a)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 < bproffit(a)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(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> >
> >
> > _______________________________________________
> > Devel mailing list
> > Devel(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> _______________________________________________
> Devel mailing list
> Devel(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
-Eldad
2704
days inactive
2712
days old
24 comments
19 participants
participants (19)
-
Barak Korren -
Brian Proffitt -
Eldad Marciano -
Eyal Edri -
Francesco Romani -
Jakub Niedermertl -
Martin Betak -
Martin Perina -
Martin Sivak -
Michal Skrivanek -
Nir Soffer -
Paul Dyer -
Piotr Kliczewski -
Roman Mohr -
Sandro Bonazzola -
Sphoorti Joglekar -
Tomas Jelinek -
Vinzenz Feenstra -
Vojtech Szocs