Re: [RESULT][VOTE] Primate as modern UI for CloudStack

2019-10-23 Thread Rohit Yadav
Andrei - please see the proposal: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
 and the discussion thread: https://markmail.org/message/z6fuvw4regig7aqb


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Andrei Mikhailovsky 
Sent: Wednesday, October 23, 2019 17:44
To: users 
Cc: dev ; priv...@cloudstack.apache.org 

Subject: Re: [RESULT][VOTE] Primate as modern UI for CloudStack

Rohit, when do you plan to add this interface to the release of ACS?

thanks
Andrei


rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

- Original Message -
> From: "Rohit Yadav" 
> To: "users" 
> Cc: "dev" , priv...@cloudstack.apache.org
> Sent: Tuesday, 22 October, 2019 09:24:07
> Subject: Re: [RESULT][VOTE] Primate as modern UI for CloudStack

> All,
>
> The repository is live - https://github.com/apache/cloudstack-primate and can
> accept pull requests now.
>
> Updates and pending items in this regard:
>
>  *   Get the Github repo's issues, wiki, projects etc. enabled. I've pinged 
> ASF
>  INFRA in that regard - https://issues.apache.org/jira/browse/INFRA-19274
>  *   I've added a contributing document:
>  https://github.com/apache/cloudstack-primate/blob/master/CONTRIBUTING.md
>  (kindly review)
>  *   Basic (work in progress) documentation section added:
>  https://github.com/apache/cloudstack-primate#documentation
>  *
> Once repository functions are fully enabled, I'll share a proper project
> progress/status update and details of the bi-weekly meeting on the Primate SIG
> thread.
>
> Thanks.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Andrija Panic 
> Sent: Monday, October 21, 2019 14:37
> To: users 
> Cc: dev@cloudstack.apache.org ;
> priv...@cloudstack.apache.org 
> Subject: Re: [RESULT][VOTE] Primate as modern UI for CloudStack
>
> (that seems like more +1s than for last few ACS releases altogether :) )
>
> Great work Rohit - thx!
>
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
> On Mon, 21 Oct 2019 at 08:57, Rohit Yadav  wrote:
>
>> All,
>>
>> After 2 weeks, the vote for accepting Primate as a CloudStack project [1]
>> *passes* with
>> 10 PMC + 11 non-PMC votes.
>>
>> +1 (PMC / binding)
>> 10 person (Mike, Simon, Andrija, Sven, Wido, Will, Syed, Gabriel, Giles,
>> Bruno)
>>
>> +1 (committer, non-binding/users)
>> 11 person (Nicolas, Nitin, Lucian, Ezequiel, Haijiao, Alex, Alessandro,
>> Marco, Anurag, Leonardo, KB Shiv)
>>
>> 0
>> none
>>
>> -1
>> none
>>
>>
>> I'll now request ASF INFRA [2] to help enable issues, pull requests, wiki,
>> projects for the new repository:
>>
>> https://github.com/apache/cloudstack-primate
>>
>>
>> The code will be donated and pushed in the next 24-48 hours from the old
>> repository [3] to the new repository under the Apache CloudStack project.
>>
>>
>> Thanks to everyone participating.
>>
>> [1] https://markmail.org/message/tblrbrtew6cvrusr
>>
>> [2] https://issues.apache.org/jira/browse/INFRA-19274
>>
>> [3] https://github.com/shapeblue/primate
>>
>> Regards,
>>
>> Rohit Yadav
>>
>> Software Architect, ShapeBlue
>>
>> https://www.shapeblue.com
>>
>> 
>>
>> rohit.ya...@shapeblue.com
>> www.shapeblue.com<http://www.shapeblue.com>
>> Amadeus House, Floral Street, London  WC2E 9DPUK
>> @shapeblue
>>
>>
>>
>> From: Rohit Yadav
>> Sent: Monday, October 7, 2019 17:01
>> To: dev@cloudstack.apache.org ;
>> us...@cloudstack.apache.org ;
>> priv...@cloudstack.apache.org 
>> Subject: [VOTE] Primate as modern UI for CloudStack
>>
>> All,
>>
>> The feedback and response has been positive on the proposal to use Primate
>> as the modern UI for CloudStack [1] [2]. Thank you all.
>>
>> I'm starting this vote (to):
>>
>>   *   Accept Primate codebase [3] as a project under Apache CloudStack
>> project
>>   *   Create and host a new repository (cloudstack-primate) and follow
>> Github based development workflow (issues, pull requests etc) as we do with
>> CloudStack
>>   *   Given this is a new project, to encourage cadence until its fea

Re: [RESULT][VOTE] Primate as modern UI for CloudStack

2019-10-23 Thread Andrei Mikhailovsky
Rohit, when do you plan to add this interface to the release of ACS?

thanks
Andrei

- Original Message -
> From: "Rohit Yadav" 
> To: "users" 
> Cc: "dev" , priv...@cloudstack.apache.org
> Sent: Tuesday, 22 October, 2019 09:24:07
> Subject: Re: [RESULT][VOTE] Primate as modern UI for CloudStack

> All,
> 
> The repository is live - https://github.com/apache/cloudstack-primate and can
> accept pull requests now.
> 
> Updates and pending items in this regard:
> 
>  *   Get the Github repo's issues, wiki, projects etc. enabled. I've pinged 
> ASF
>  INFRA in that regard - https://issues.apache.org/jira/browse/INFRA-19274
>  *   I've added a contributing document:
>  https://github.com/apache/cloudstack-primate/blob/master/CONTRIBUTING.md
>  (kindly review)
>  *   Basic (work in progress) documentation section added:
>  https://github.com/apache/cloudstack-primate#documentation
>  *
> Once repository functions are fully enabled, I'll share a proper project
> progress/status update and details of the bi-weekly meeting on the Primate SIG
> thread.
> 
> Thanks.
> 
> 
> Regards,
> 
> Rohit Yadav
> 
> Software Architect, ShapeBlue
> 
> https://www.shapeblue.com
> 
> 
> From: Andrija Panic 
> Sent: Monday, October 21, 2019 14:37
> To: users 
> Cc: dev@cloudstack.apache.org ;
> priv...@cloudstack.apache.org 
> Subject: Re: [RESULT][VOTE] Primate as modern UI for CloudStack
> 
> (that seems like more +1s than for last few ACS releases altogether :) )
> 
> Great work Rohit - thx!
> 
> 
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>  
> 
> 
> On Mon, 21 Oct 2019 at 08:57, Rohit Yadav  wrote:
> 
>> All,
>>
>> After 2 weeks, the vote for accepting Primate as a CloudStack project [1]
>> *passes* with
>> 10 PMC + 11 non-PMC votes.
>>
>> +1 (PMC / binding)
>> 10 person (Mike, Simon, Andrija, Sven, Wido, Will, Syed, Gabriel, Giles,
>> Bruno)
>>
>> +1 (committer, non-binding/users)
>> 11 person (Nicolas, Nitin, Lucian, Ezequiel, Haijiao, Alex, Alessandro,
>> Marco, Anurag, Leonardo, KB Shiv)
>>
>> 0
>> none
>>
>> -1
>> none
>>
>>
>> I'll now request ASF INFRA [2] to help enable issues, pull requests, wiki,
>> projects for the new repository:
>>
>> https://github.com/apache/cloudstack-primate
>>
>>
>> The code will be donated and pushed in the next 24-48 hours from the old
>> repository [3] to the new repository under the Apache CloudStack project.
>>
>>
>> Thanks to everyone participating.
>>
>> [1] https://markmail.org/message/tblrbrtew6cvrusr
>>
>> [2] https://issues.apache.org/jira/browse/INFRA-19274
>>
>> [3] https://github.com/shapeblue/primate
>>
>> Regards,
>>
>> Rohit Yadav
>>
>> Software Architect, ShapeBlue
>>
>> https://www.shapeblue.com
>>
>> 
>>
>> rohit.ya...@shapeblue.com
>> www.shapeblue.com<http://www.shapeblue.com>
>> Amadeus House, Floral Street, London  WC2E 9DPUK
>> @shapeblue
>>
>>
>>
>> From: Rohit Yadav
>> Sent: Monday, October 7, 2019 17:01
>> To: dev@cloudstack.apache.org ;
>> us...@cloudstack.apache.org ;
>> priv...@cloudstack.apache.org 
>> Subject: [VOTE] Primate as modern UI for CloudStack
>>
>> All,
>>
>> The feedback and response has been positive on the proposal to use Primate
>> as the modern UI for CloudStack [1] [2]. Thank you all.
>>
>> I'm starting this vote (to):
>>
>>   *   Accept Primate codebase [3] as a project under Apache CloudStack
>> project
>>   *   Create and host a new repository (cloudstack-primate) and follow
>> Github based development workflow (issues, pull requests etc) as we do with
>> CloudStack
>>   *   Given this is a new project, to encourage cadence until its feature
>> completeness the merge criteria is proposed as:
>>  *   Manual testing against each PR and/or with screenshots from the
>> author or testing contributor, integration with Travis is possible once we
>> get JS/UI tests
>>  *   At least 1 LGTM from any of the active contributors, we'll move
>> this to 2 LGTMs when the codebase reaches feature parity wrt the
>> existing/old CloudStack UI
>>  *   Squash and merge PRs
>>   *   Accept the proposed timeline [1][2] (subject to achievement of goals
>> wrt Primate technical release and GA)
>>  

Re: [RESULT][VOTE] Primate as modern UI for CloudStack

2019-10-22 Thread Rohit Yadav
All,

The repository is live - https://github.com/apache/cloudstack-primate and can 
accept pull requests now.

Updates and pending items in this regard:

  *   Get the Github repo's issues, wiki, projects etc. enabled. I've pinged 
ASF INFRA in that regard - https://issues.apache.org/jira/browse/INFRA-19274
  *   I've added a contributing document: 
https://github.com/apache/cloudstack-primate/blob/master/CONTRIBUTING.md 
(kindly review)
  *   Basic (work in progress) documentation section added: 
https://github.com/apache/cloudstack-primate#documentation
  *
Once repository functions are fully enabled, I'll share a proper project 
progress/status update and details of the bi-weekly meeting on the Primate SIG 
thread.

Thanks.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Andrija Panic 
Sent: Monday, October 21, 2019 14:37
To: users 
Cc: dev@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: Re: [RESULT][VOTE] Primate as modern UI for CloudStack

(that seems like more +1s than for last few ACS releases altogether :) )

Great work Rohit - thx!


rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

On Mon, 21 Oct 2019 at 08:57, Rohit Yadav  wrote:

> All,
>
> After 2 weeks, the vote for accepting Primate as a CloudStack project [1]
> *passes* with
> 10 PMC + 11 non-PMC votes.
>
> +1 (PMC / binding)
> 10 person (Mike, Simon, Andrija, Sven, Wido, Will, Syed, Gabriel, Giles,
> Bruno)
>
> +1 (committer, non-binding/users)
> 11 person (Nicolas, Nitin, Lucian, Ezequiel, Haijiao, Alex, Alessandro,
> Marco, Anurag, Leonardo, KB Shiv)
>
> 0
> none
>
> -1
> none
>
>
> I'll now request ASF INFRA [2] to help enable issues, pull requests, wiki,
> projects for the new repository:
>
> https://github.com/apache/cloudstack-primate
>
>
> The code will be donated and pushed in the next 24-48 hours from the old
> repository [3] to the new repository under the Apache CloudStack project.
>
>
> Thanks to everyone participating.
>
> [1] https://markmail.org/message/tblrbrtew6cvrusr
>
> [2] https://issues.apache.org/jira/browse/INFRA-19274
>
> [3] https://github.com/shapeblue/primate
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
> From: Rohit Yadav
> Sent: Monday, October 7, 2019 17:01
> To: dev@cloudstack.apache.org ;
> us...@cloudstack.apache.org ;
> priv...@cloudstack.apache.org 
> Subject: [VOTE] Primate as modern UI for CloudStack
>
> All,
>
> The feedback and response has been positive on the proposal to use Primate
> as the modern UI for CloudStack [1] [2]. Thank you all.
>
> I'm starting this vote (to):
>
>   *   Accept Primate codebase [3] as a project under Apache CloudStack
> project
>   *   Create and host a new repository (cloudstack-primate) and follow
> Github based development workflow (issues, pull requests etc) as we do with
> CloudStack
>   *   Given this is a new project, to encourage cadence until its feature
> completeness the merge criteria is proposed as:
>  *   Manual testing against each PR and/or with screenshots from the
> author or testing contributor, integration with Travis is possible once we
> get JS/UI tests
>  *   At least 1 LGTM from any of the active contributors, we'll move
> this to 2 LGTMs when the codebase reaches feature parity wrt the
> existing/old CloudStack UI
>  *   Squash and merge PRs
>   *   Accept the proposed timeline [1][2] (subject to achievement of goals
> wrt Primate technical release and GA)
>  *   the first technical preview targetted with the winter 2019 LTS
> release (~Q1 2020) and release to serve a deprecation notice wrt the older
> UI
>  *   define a release approach before winter LTS
>  *   stop taking feature FRs for old/existing UI after winter 2019 LTS
> release, work on upgrade path/documentation from old UI to Primate
>  *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019),
> but still ship old UI with a final deprecation notice
>  *   old UI codebase removed from codebase in winter 2020 LTS release
>
> The vote will be up for the next two weeks to give enough time for PMC and
> the community to gather consensus and still have room for questions,
> feedback and discussions. The results to be shared on/after 21th October
> 2019.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with th

Re: [RESULT][VOTE] Primate as modern UI for CloudStack

2019-10-21 Thread Andrija Panic
(that seems like more +1s than for last few ACS releases altogether :) )

Great work Rohit - thx!

On Mon, 21 Oct 2019 at 08:57, Rohit Yadav  wrote:

> All,
>
> After 2 weeks, the vote for accepting Primate as a CloudStack project [1]
> *passes* with
> 10 PMC + 11 non-PMC votes.
>
> +1 (PMC / binding)
> 10 person (Mike, Simon, Andrija, Sven, Wido, Will, Syed, Gabriel, Giles,
> Bruno)
>
> +1 (committer, non-binding/users)
> 11 person (Nicolas, Nitin, Lucian, Ezequiel, Haijiao, Alex, Alessandro,
> Marco, Anurag, Leonardo, KB Shiv)
>
> 0
> none
>
> -1
> none
>
>
> I'll now request ASF INFRA [2] to help enable issues, pull requests, wiki,
> projects for the new repository:
>
> https://github.com/apache/cloudstack-primate
>
>
> The code will be donated and pushed in the next 24-48 hours from the old
> repository [3] to the new repository under the Apache CloudStack project.
>
>
> Thanks to everyone participating.
>
> [1] https://markmail.org/message/tblrbrtew6cvrusr
>
> [2] https://issues.apache.org/jira/browse/INFRA-19274
>
> [3] https://github.com/shapeblue/primate
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
> From: Rohit Yadav
> Sent: Monday, October 7, 2019 17:01
> To: dev@cloudstack.apache.org ;
> us...@cloudstack.apache.org ;
> priv...@cloudstack.apache.org 
> Subject: [VOTE] Primate as modern UI for CloudStack
>
> All,
>
> The feedback and response has been positive on the proposal to use Primate
> as the modern UI for CloudStack [1] [2]. Thank you all.
>
> I'm starting this vote (to):
>
>   *   Accept Primate codebase [3] as a project under Apache CloudStack
> project
>   *   Create and host a new repository (cloudstack-primate) and follow
> Github based development workflow (issues, pull requests etc) as we do with
> CloudStack
>   *   Given this is a new project, to encourage cadence until its feature
> completeness the merge criteria is proposed as:
>  *   Manual testing against each PR and/or with screenshots from the
> author or testing contributor, integration with Travis is possible once we
> get JS/UI tests
>  *   At least 1 LGTM from any of the active contributors, we'll move
> this to 2 LGTMs when the codebase reaches feature parity wrt the
> existing/old CloudStack UI
>  *   Squash and merge PRs
>   *   Accept the proposed timeline [1][2] (subject to achievement of goals
> wrt Primate technical release and GA)
>  *   the first technical preview targetted with the winter 2019 LTS
> release (~Q1 2020) and release to serve a deprecation notice wrt the older
> UI
>  *   define a release approach before winter LTS
>  *   stop taking feature FRs for old/existing UI after winter 2019 LTS
> release, work on upgrade path/documentation from old UI to Primate
>  *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019),
> but still ship old UI with a final deprecation notice
>  *   old UI codebase removed from codebase in winter 2020 LTS release
>
> The vote will be up for the next two weeks to give enough time for PMC and
> the community to gather consensus and still have room for questions,
> feedback and discussions. The results to be shared on/after 21th October
> 2019.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> [1] Primate Proposal:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>
> [2] Email thread reference:
> https://markmail.org/message/z6fuvw4regig7aqb
>
> [3] Primate repo current location: https://github.com/shapeblue/primate
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>


-- 

Andrija Panić


[RESULT][VOTE] Primate as modern UI for CloudStack

2019-10-21 Thread Rohit Yadav
All,

After 2 weeks, the vote for accepting Primate as a CloudStack project [1] 
*passes* with
10 PMC + 11 non-PMC votes.

+1 (PMC / binding)
10 person (Mike, Simon, Andrija, Sven, Wido, Will, Syed, Gabriel, Giles, Bruno)

+1 (committer, non-binding/users)
11 person (Nicolas, Nitin, Lucian, Ezequiel, Haijiao, Alex, Alessandro, Marco, 
Anurag, Leonardo, KB Shiv)

0
none

-1
none


I'll now request ASF INFRA [2] to help enable issues, pull requests, wiki, 
projects for the new repository:

https://github.com/apache/cloudstack-primate


The code will be donated and pushed in the next 24-48 hours from the old 
repository [3] to the new repository under the Apache CloudStack project.


Thanks to everyone participating.

[1] https://markmail.org/message/tblrbrtew6cvrusr

[2] https://issues.apache.org/jira/browse/INFRA-19274

[3] https://github.com/shapeblue/primate

Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com



rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

From: Rohit Yadav
Sent: Monday, October 7, 2019 17:01
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: [VOTE] Primate as modern UI for CloudStack

All,

The feedback and response has been positive on the proposal to use Primate as 
the modern UI for CloudStack [1] [2]. Thank you all.

I'm starting this vote (to):

  *   Accept Primate codebase [3] as a project under Apache CloudStack project
  *   Create and host a new repository (cloudstack-primate) and follow Github 
based development workflow (issues, pull requests etc) as we do with CloudStack
  *   Given this is a new project, to encourage cadence until its feature 
completeness the merge criteria is proposed as:
 *   Manual testing against each PR and/or with screenshots from the author 
or testing contributor, integration with Travis is possible once we get JS/UI 
tests
 *   At least 1 LGTM from any of the active contributors, we'll move this 
to 2 LGTMs when the codebase reaches feature parity wrt the existing/old 
CloudStack UI
 *   Squash and merge PRs
  *   Accept the proposed timeline [1][2] (subject to achievement of goals wrt 
Primate technical release and GA)
 *   the first technical preview targetted with the winter 2019 LTS release 
(~Q1 2020) and release to serve a deprecation notice wrt the older UI
 *   define a release approach before winter LTS
 *   stop taking feature FRs for old/existing UI after winter 2019 LTS 
release, work on upgrade path/documentation from old UI to Primate
 *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019), but 
still ship old UI with a final deprecation notice
 *   old UI codebase removed from codebase in winter 2020 LTS release

The vote will be up for the next two weeks to give enough time for PMC and the 
community to gather consensus and still have room for questions, feedback and 
discussions. The results to be shared on/after 21th October 2019.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

[1] Primate Proposal:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI

[2] Email thread reference:
https://markmail.org/message/z6fuvw4regig7aqb

[3] Primate repo current location: https://github.com/shapeblue/primate


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


Re: [VOTE] Primate as modern UI for CloudStack

2019-10-16 Thread K B Shiv Kumar
+1 (binding)

On Mon, Oct 7, 2019 at 5:01 PM Rohit Yadav 
wrote:

> All,
>
> The feedback and response has been positive on the proposal to use Primate
> as the modern UI for CloudStack [1] [2]. Thank you all.
>
> I'm starting this vote (to):
>
>   *   Accept Primate codebase [3] as a project under Apache CloudStack
> project
>   *   Create and host a new repository (cloudstack-primate) and follow
> Github based development workflow (issues, pull requests etc) as we do with
> CloudStack
>   *   Given this is a new project, to encourage cadence until its feature
> completeness the merge criteria is proposed as:
>  *   Manual testing against each PR and/or with screenshots from the
> author or testing contributor, integration with Travis is possible once we
> get JS/UI tests
>  *   At least 1 LGTM from any of the active contributors, we'll move
> this to 2 LGTMs when the codebase reaches feature parity wrt the
> existing/old CloudStack UI
>  *   Squash and merge PRs
>   *   Accept the proposed timeline [1][2] (subject to achievement of goals
> wrt Primate technical release and GA)
>  *   the first technical preview targetted with the winter 2019 LTS
> release (~Q1 2020) and release to serve a deprecation notice wrt the older
> UI
>  *   define a release approach before winter LTS
>  *   stop taking feature FRs for old/existing UI after winter 2019 LTS
> release, work on upgrade path/documentation from old UI to Primate
>  *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019),
> but still ship old UI with a final deprecation notice
>  *   old UI codebase removed from codebase in winter 2020 LTS release
>
> The vote will be up for the next two weeks to give enough time for PMC and
> the community to gather consensus and still have room for questions,
> feedback and discussions. The results to be shared on/after 21th October
> 2019.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> [1] Primate Proposal:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>
> [2] Email thread reference:
> https://markmail.org/message/z6fuvw4regig7aqb
>
> [3] Primate repo current location: https://github.com/shapeblue/primate
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

-- 
Regards
Shiv


Re: [VOTE] Primate as modern UI for CloudStack

2019-10-14 Thread Rohit Yadav
Hi Ivan,

> Do you have your plan how to get best results from that? I mean can you 
> organize your time to get best of it? Of course it's possible to elaborate a 
> plan, etc. Let me know when you feel our efforts lead to the best 
> productivity and we plan the allocation.

Ivan - Primate is already functional in its current state, authentication, 
translation, and most of the list views and detail views work.

This week (and possibly next) we're aiming to get it structurally complete, 
which will be to add actions to most of the views (except for special actions 
that require a wizard or a special form). Thanks for offering your help, we 
would certainly need help with the QA effort, laying out the foundation, esp 
helping us with examples and docs on how to write and run UI tests (best 
practices, tools etc).

Given there are no objections and all +1s so far, it would be great if we can 
get help starting next week (21 Oct 2019) when the code will be accepted and 
moved to its new repo under ASF. I'll start another thread to share details on 
a community-wide collaboration plan.

Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Ivan Kudryavtsev 
Sent: Wednesday, October 9, 2019 15:38
To: dev 
Subject: Re: [VOTE] Primate as modern UI for CloudStack

Rohit,

we can not afford full-time QA allocation for the project, but let me know
when you would produce the first piece of the the code, and I'll dedicate
someone from the QA with Cloudstack experience, who can help you to
establish the testing environment, choose the tools and write some tests to
build a foundation, so in the future you and other involved can act by
example.

ср, 9 окт. 2019 г. в 16:59, Rohit Yadav :

> Hi Ivan,
>
> Thanks for your advice.
>
> I agree with the general idea of automating regression test for the UI,
> however, I don't have the expertise around writing tests using best
> practices, and I look forward to you or anyone else who can share some
> pointers, examples or maybe a plan. Given the UI is largely config and data
> driven, the number of components shouldn't be high except for any
> customization we do for some views.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Ivan Kudryavtsev 
> Sent: Wednesday, October 9, 2019 09:37
> To: dev 
> Subject: Re: [VOTE] Primate as modern UI for CloudStack
>
> Hello, community. I know it's just a voting process, but still... a piece
> of wisdom from webdev company:
>
> 1. Manual testing is an extremely bad idea, you've meet a lot of
> regression, much more than the backend typically has.
>
> 2. In our teams frontend/backend ratio have shifted from 1/1 to 2/1,
> without UI automation QA engineers, so 3/1 is average ratio for real life
> high quality web UIs.
>
> 3. Try to use/invent some sort of Django-like UI generator frameworks, no
> code manually. I see the high risk of fail without that. May be need to add
> some sort of metadata to backend first. The Cloudmonkey approach is a great
> basic idea... Oracle also has certain frameworks for that. Ideally, to
> define the forms and sitemap and generate everything else from the ORM.
>
> 4. Happy to see the initiative, as it could help to decrease the pace of
> backend changes and increase the stability, as certain amount of
> influencers turn into frontend JS developers.
>
>
>
> ср, 9 окт. 2019 г., 7:45 Anurag Awasthi :
>
> > +1
> >
> > Kind Regards,
> > Anurag Awasthi
> > 
> > From: Marco Sinhoreli 
> > Sent: Wednesday, October 9, 2019 4:10 AM
> > To: dev@cloudstack.apache.org ;
> > us...@cloudstack.apache.org ;
> > priv...@cloudstack.apache.org 
> > Subject: Re: [VOTE] Primate as modern UI for CloudStack
> >
> > +1
> >
> >
> > Marco Sinhoreli
> > Latam Technical Director
> > marco.sinhor...@shapeblue.com
> > mobile: +55 11 95656-3636
> >
> > Rua Gomes de Carvalho, 911 – Sala 316
> > Vila Olímpia, São Paulo, SP, Brasil, 04547-003
> > Phone: + 55 11 2818-3419
> > http://www.shapeblue.com/ | twitter: @shapeblue
> >
> > Em 07/10/2019 08:31, "Rohit Yadav" 
> escreveu:
> >
> > All,
> >
> > The feedback and response has been positive on the proposal to use
> > Primate as the modern UI for CloudStack [1] [2]. Thank you all.
> >
> > I'm starting this vote (to):
> >
> >   *   Accept Primate codebase [3] as a project under Apache
> CloudStack
> > project
> >   *   Create and host a new repository (cloudstack-primate) and
> follow
> >

Re: [VOTE] Primate as modern UI for CloudStack

2019-10-10 Thread Sven Vogel
Sounds interesting Gregor!

Von meinem iPhone gesendet


__

Sven Vogel
Teamlead Platform

EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
s.vo...@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter
Registergericht: Leipzig HRB 9065

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

EWERK-Blog | LinkedIn | Xing | Twitter | Facebook

Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist 
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der 
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, 
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte 
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die 
E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen 
Dank.

The contents of this e-mail (including any attachments) are confidential and 
may be legally privileged. If you are not the intended recipient of this 
e-mail, any disclosure, copying, distribution or use of its contents is 
strictly prohibited, and you should please notify the sender immediately and 
then delete it (including any attachments) from your system. Thank you.
> Am 10.10.2019 um 16:47 schrieb Riepl, Gregor (SWISS TXT) 
> :
>
> Automated UI testing is usually done by running a web browser, generating 
> artificial user input, then verifying the result either by DOM analysis or 
> image recognition on screenshots.
>
> Our devs have achieved good results with TestCafe: 
> https://devexpress.github.io/testcafe/
> It's very easy to write tests and run them in different browser engines. You 
> can even run certain browser engines in headless mode for automated testing.
> 
> From: Rohit Yadav 
> Sent: 09 October 2019 11:58
> To: dev 
> Subject: Re: [VOTE] Primate as modern UI for CloudStack
>
> Hi Ivan,
>
> Thanks for your advice.
>
> I agree with the general idea of automating regression test for the UI, 
> however, I don't have the expertise around writing tests using best 
> practices, and I look forward to you or anyone else who can share some 
> pointers, examples or maybe a plan. Given the UI is largely config and data 
> driven, the number of components shouldn't be high except for any 
> customization we do for some views.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> ________
> From: Ivan Kudryavtsev 
> Sent: Wednesday, October 9, 2019 09:37
> To: dev 
> Subject: Re: [VOTE] Primate as modern UI for CloudStack
>
> Hello, community. I know it's just a voting process, but still... a piece
> of wisdom from webdev company:
>
> 1. Manual testing is an extremely bad idea, you've meet a lot of
> regression, much more than the backend typically has.
>
> 2. In our teams frontend/backend ratio have shifted from 1/1 to 2/1,
> without UI automation QA engineers, so 3/1 is average ratio for real life
> high quality web UIs.
>
> 3. Try to use/invent some sort of Django-like UI generator frameworks, no
> code manually. I see the high risk of fail without that. May be need to add
> some sort of metadata to backend first. The Cloudmonkey approach is a great
> basic idea... Oracle also has certain frameworks for that. Ideally, to
> define the forms and sitemap and generate everything else from the ORM.
>
> 4. Happy to see the initiative, as it could help to decrease the pace of
> backend changes and increase the stability, as certain amount of
> influencers turn into frontend JS developers.
>
>
>
> ср, 9 окт. 2019 г., 7:45 Anurag Awasthi :
>
>> +1
>>
>> Kind Regards,
>> Anurag Awasthi
>> ________
>> From: Marco Sinhoreli 
>> Sent: Wednesday, October 9, 2019 4:10 AM
>> To: dev@cloudstack.apache.org ;
>> us...@cloudstack.apache.org ;
>> priv...@cloudstack.apache.org 
>> Subject: Re: [VOTE] Primate as modern UI for CloudStack
>>
>> +1
>>
>>
>> Marco Sinhoreli
>> Latam Technical Director
>> marco.sinhor...@shapeblue.com
>> mobile: +55 11 95656-3636
>>
>> Rua Gomes de Carvalho, 911 – Sala 316
>> Vila Olímpia, São Paulo, SP, Brasil, 04547-003
>> Phone: + 55 11 2818-3419
>> http://www.shapeblue.com/ | twitter: @shapeblue
>>
>> Em 07/10/2019 08:31, "Rohit Yadav"  escreveu:
>>
>>All,
>>
>>The feedback and response has been positive on the proposal to use
>> Primate as the modern UI for CloudStack [1] [2]. Thank you al

Re: [VOTE] Primate as modern UI for CloudStack

2019-10-10 Thread Riepl, Gregor (SWISS TXT)
Automated UI testing is usually done by running a web browser, generating 
artificial user input, then verifying the result either by DOM analysis or 
image recognition on screenshots.

Our devs have achieved good results with TestCafe: 
https://devexpress.github.io/testcafe/
It's very easy to write tests and run them in different browser engines. You 
can even run certain browser engines in headless mode for automated testing.

From: Rohit Yadav 
Sent: 09 October 2019 11:58
To: dev 
Subject: Re: [VOTE] Primate as modern UI for CloudStack

Hi Ivan,

Thanks for your advice.

I agree with the general idea of automating regression test for the UI, 
however, I don't have the expertise around writing tests using best practices, 
and I look forward to you or anyone else who can share some pointers, examples 
or maybe a plan. Given the UI is largely config and data driven, the number of 
components shouldn't be high except for any customization we do for some views.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Ivan Kudryavtsev 
Sent: Wednesday, October 9, 2019 09:37
To: dev 
Subject: Re: [VOTE] Primate as modern UI for CloudStack

Hello, community. I know it's just a voting process, but still... a piece
of wisdom from webdev company:

1. Manual testing is an extremely bad idea, you've meet a lot of
regression, much more than the backend typically has.

2. In our teams frontend/backend ratio have shifted from 1/1 to 2/1,
without UI automation QA engineers, so 3/1 is average ratio for real life
high quality web UIs.

3. Try to use/invent some sort of Django-like UI generator frameworks, no
code manually. I see the high risk of fail without that. May be need to add
some sort of metadata to backend first. The Cloudmonkey approach is a great
basic idea... Oracle also has certain frameworks for that. Ideally, to
define the forms and sitemap and generate everything else from the ORM.

4. Happy to see the initiative, as it could help to decrease the pace of
backend changes and increase the stability, as certain amount of
influencers turn into frontend JS developers.



ср, 9 окт. 2019 г., 7:45 Anurag Awasthi :

> +1
>
> Kind Regards,
> Anurag Awasthi
> 
> From: Marco Sinhoreli 
> Sent: Wednesday, October 9, 2019 4:10 AM
> To: dev@cloudstack.apache.org ;
> us...@cloudstack.apache.org ;
> priv...@cloudstack.apache.org 
> Subject: Re: [VOTE] Primate as modern UI for CloudStack
>
> +1
>
>
> Marco Sinhoreli
> Latam Technical Director
> marco.sinhor...@shapeblue.com
> mobile: +55 11 95656-3636
>
> Rua Gomes de Carvalho, 911 – Sala 316
> Vila Olímpia, São Paulo, SP, Brasil, 04547-003
> Phone: + 55 11 2818-3419
> http://www.shapeblue.com/ | twitter: @shapeblue
>
> Em 07/10/2019 08:31, "Rohit Yadav"  escreveu:
>
> All,
>
> The feedback and response has been positive on the proposal to use
> Primate as the modern UI for CloudStack [1] [2]. Thank you all.
>
> I'm starting this vote (to):
>
>   *   Accept Primate codebase [3] as a project under Apache CloudStack
> project
>   *   Create and host a new repository (cloudstack-primate) and follow
> Github based development workflow (issues, pull requests etc) as we do with
> CloudStack
>   *   Given this is a new project, to encourage cadence until its
> feature completeness the merge criteria is proposed as:
>  *   Manual testing against each PR and/or with screenshots from
> the author or testing contributor, integration with Travis is possible once
> we get JS/UI tests
>  *   At least 1 LGTM from any of the active contributors, we'll
> move this to 2 LGTMs when the codebase reaches feature parity wrt the
> existing/old CloudStack UI
>  *   Squash and merge PRs
>   *   Accept the proposed timeline [1][2] (subject to achievement of
> goals wrt Primate technical release and GA)
>  *   the first technical preview targetted with the winter 2019
> LTS release (~Q1 2020) and release to serve a deprecation notice wrt the
> older UI
>  *   define a release approach before winter LTS
>  *   stop taking feature FRs for old/existing UI after winter 2019
> LTS release, work on upgrade path/documentation from old UI to Primate
>  *   the first Primate GA targetted wrt summer LTS 2020 (~H2
> 2019), but still ship old UI with a final deprecation notice
>  *   old UI codebase removed from codebase in winter 2020 LTS
> release
>
> The vote will be up for the next two weeks to give enough time for PMC
> and the community to gather consensus and still have room for questions,
> feedback and discussions. The results to be shared on/after 21th October
> 2019.

RE: [VOTE] Primate as modern UI for CloudStack

2019-10-10 Thread Paul Angus
That sounds great Ivan!  You can see the code at 
https://github.com/shapeBlue/primate
Hopefully within a couple of weeks it'll be able to be included in the Apache 
repo. 

paul.an...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-Original Message-
From: Ivan Kudryavtsev  
Sent: 09 October 2019 11:08
To: dev 
Subject: Re: [VOTE] Primate as modern UI for CloudStack

Rohit,

we can not afford full-time QA allocation for the project, but let me know when 
you would produce the first piece of the the code, and I'll dedicate someone 
from the QA with Cloudstack experience, who can help you to establish the 
testing environment, choose the tools and write some tests to build a 
foundation, so in the future you and other involved can act by example.

ср, 9 окт. 2019 г. в 16:59, Rohit Yadav :

> Hi Ivan,
>
> Thanks for your advice.
>
> I agree with the general idea of automating regression test for the 
> UI, however, I don't have the expertise around writing tests using 
> best practices, and I look forward to you or anyone else who can share 
> some pointers, examples or maybe a plan. Given the UI is largely 
> config and data driven, the number of components shouldn't be high 
> except for any customization we do for some views.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Ivan Kudryavtsev 
> Sent: Wednesday, October 9, 2019 09:37
> To: dev 
> Subject: Re: [VOTE] Primate as modern UI for CloudStack
>
> Hello, community. I know it's just a voting process, but still... a 
> piece of wisdom from webdev company:
>
> 1. Manual testing is an extremely bad idea, you've meet a lot of 
> regression, much more than the backend typically has.
>
> 2. In our teams frontend/backend ratio have shifted from 1/1 to 2/1, 
> without UI automation QA engineers, so 3/1 is average ratio for real 
> life high quality web UIs.
>
> 3. Try to use/invent some sort of Django-like UI generator frameworks, 
> no code manually. I see the high risk of fail without that. May be 
> need to add some sort of metadata to backend first. The Cloudmonkey 
> approach is a great basic idea... Oracle also has certain frameworks 
> for that. Ideally, to define the forms and sitemap and generate everything 
> else from the ORM.
>
> 4. Happy to see the initiative, as it could help to decrease the pace 
> of backend changes and increase the stability, as certain amount of 
> influencers turn into frontend JS developers.
>
>
>
> ср, 9 окт. 2019 г., 7:45 Anurag Awasthi :
>
> > +1
> >
> > Kind Regards,
> > Anurag Awasthi
> > 
> > From: Marco Sinhoreli 
> > Sent: Wednesday, October 9, 2019 4:10 AM
> > To: dev@cloudstack.apache.org ; 
> > us...@cloudstack.apache.org ; 
> > priv...@cloudstack.apache.org 
> > Subject: Re: [VOTE] Primate as modern UI for CloudStack
> >
> > +1
> >
> >
> > Marco Sinhoreli
> > Latam Technical Director
> > marco.sinhor...@shapeblue.com
> > mobile: +55 11 95656-3636
> >
> > Rua Gomes de Carvalho, 911 – Sala 316 Vila Olímpia, São Paulo, SP, 
> > Brasil, 04547-003
> > Phone: + 55 11 2818-3419
> > http://www.shapeblue.com/ | twitter: @shapeblue
> >
> > Em 07/10/2019 08:31, "Rohit Yadav" 
> escreveu:
> >
> > All,
> >
> > The feedback and response has been positive on the proposal to 
> > use Primate as the modern UI for CloudStack [1] [2]. Thank you all.
> >
> > I'm starting this vote (to):
> >
> >   *   Accept Primate codebase [3] as a project under Apache
> CloudStack
> > project
> >   *   Create and host a new repository (cloudstack-primate) and
> follow
> > Github based development workflow (issues, pull requests etc) as we 
> > do
> with
> > CloudStack
> >   *   Given this is a new project, to encourage cadence until its
> > feature completeness the merge criteria is proposed as:
> >  *   Manual testing against each PR and/or with screenshots from
> > the author or testing contributor, integration with Travis is 
> > possible
> once
> > we get JS/UI tests
> >  *   At least 1 LGTM from any of the active contributors, we'll
> > move this to 2 LGTMs when the codebase reaches feature parity wrt 
> > the existing/old CloudStack UI
> >  *   Squash and merge PRs
> >   *   Accept the proposed timeline [1][2] (subject to achievement of
> > goals wrt Primate technical release and GA)
> >  *   the firs

Re: [VOTE] Primate as modern UI for CloudStack

2019-10-09 Thread Ivan Kudryavtsev
Rohit,

we can not afford full-time QA allocation for the project, but let me know
when you would produce the first piece of the the code, and I'll dedicate
someone from the QA with Cloudstack experience, who can help you to
establish the testing environment, choose the tools and write some tests to
build a foundation, so in the future you and other involved can act by
example.

ср, 9 окт. 2019 г. в 16:59, Rohit Yadav :

> Hi Ivan,
>
> Thanks for your advice.
>
> I agree with the general idea of automating regression test for the UI,
> however, I don't have the expertise around writing tests using best
> practices, and I look forward to you or anyone else who can share some
> pointers, examples or maybe a plan. Given the UI is largely config and data
> driven, the number of components shouldn't be high except for any
> customization we do for some views.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Ivan Kudryavtsev 
> Sent: Wednesday, October 9, 2019 09:37
> To: dev 
> Subject: Re: [VOTE] Primate as modern UI for CloudStack
>
> Hello, community. I know it's just a voting process, but still... a piece
> of wisdom from webdev company:
>
> 1. Manual testing is an extremely bad idea, you've meet a lot of
> regression, much more than the backend typically has.
>
> 2. In our teams frontend/backend ratio have shifted from 1/1 to 2/1,
> without UI automation QA engineers, so 3/1 is average ratio for real life
> high quality web UIs.
>
> 3. Try to use/invent some sort of Django-like UI generator frameworks, no
> code manually. I see the high risk of fail without that. May be need to add
> some sort of metadata to backend first. The Cloudmonkey approach is a great
> basic idea... Oracle also has certain frameworks for that. Ideally, to
> define the forms and sitemap and generate everything else from the ORM.
>
> 4. Happy to see the initiative, as it could help to decrease the pace of
> backend changes and increase the stability, as certain amount of
> influencers turn into frontend JS developers.
>
>
>
> ср, 9 окт. 2019 г., 7:45 Anurag Awasthi :
>
> > +1
> >
> > Kind Regards,
> > Anurag Awasthi
> > 
> > From: Marco Sinhoreli 
> > Sent: Wednesday, October 9, 2019 4:10 AM
> > To: dev@cloudstack.apache.org ;
> > us...@cloudstack.apache.org ;
> > priv...@cloudstack.apache.org 
> > Subject: Re: [VOTE] Primate as modern UI for CloudStack
> >
> > +1
> >
> >
> > Marco Sinhoreli
> > Latam Technical Director
> > marco.sinhor...@shapeblue.com
> > mobile: +55 11 95656-3636
> >
> > Rua Gomes de Carvalho, 911 – Sala 316
> > Vila Olímpia, São Paulo, SP, Brasil, 04547-003
> > Phone: + 55 11 2818-3419
> > http://www.shapeblue.com/ | twitter: @shapeblue
> >
> > Em 07/10/2019 08:31, "Rohit Yadav" 
> escreveu:
> >
> > All,
> >
> > The feedback and response has been positive on the proposal to use
> > Primate as the modern UI for CloudStack [1] [2]. Thank you all.
> >
> > I'm starting this vote (to):
> >
> >   *   Accept Primate codebase [3] as a project under Apache
> CloudStack
> > project
> >   *   Create and host a new repository (cloudstack-primate) and
> follow
> > Github based development workflow (issues, pull requests etc) as we do
> with
> > CloudStack
> >   *   Given this is a new project, to encourage cadence until its
> > feature completeness the merge criteria is proposed as:
> >  *   Manual testing against each PR and/or with screenshots from
> > the author or testing contributor, integration with Travis is possible
> once
> > we get JS/UI tests
> >  *   At least 1 LGTM from any of the active contributors, we'll
> > move this to 2 LGTMs when the codebase reaches feature parity wrt the
> > existing/old CloudStack UI
> >  *   Squash and merge PRs
> >   *   Accept the proposed timeline [1][2] (subject to achievement of
> > goals wrt Primate technical release and GA)
> >  *   the first technical preview targetted with the winter 2019
> > LTS release (~Q1 2020) and release to serve a deprecation notice wrt the
> > older UI
> >  *   define a release approach before winter LTS
> >  *   stop taking feature FRs for old/existing UI after winter
> 2019
> > LTS release, work on upgrade path/documentation from old UI to Primate
> >  *   the first Primate GA targetted wrt summer LTS 2020 (~H2
> > 2019), bu

Re: [VOTE] Primate as modern UI for CloudStack

2019-10-09 Thread Rohit Yadav
Hi Ivan,

Thanks for your advice.

I agree with the general idea of automating regression test for the UI, 
however, I don't have the expertise around writing tests using best practices, 
and I look forward to you or anyone else who can share some pointers, examples 
or maybe a plan. Given the UI is largely config and data driven, the number of 
components shouldn't be high except for any customization we do for some views.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Ivan Kudryavtsev 
Sent: Wednesday, October 9, 2019 09:37
To: dev 
Subject: Re: [VOTE] Primate as modern UI for CloudStack

Hello, community. I know it's just a voting process, but still... a piece
of wisdom from webdev company:

1. Manual testing is an extremely bad idea, you've meet a lot of
regression, much more than the backend typically has.

2. In our teams frontend/backend ratio have shifted from 1/1 to 2/1,
without UI automation QA engineers, so 3/1 is average ratio for real life
high quality web UIs.

3. Try to use/invent some sort of Django-like UI generator frameworks, no
code manually. I see the high risk of fail without that. May be need to add
some sort of metadata to backend first. The Cloudmonkey approach is a great
basic idea... Oracle also has certain frameworks for that. Ideally, to
define the forms and sitemap and generate everything else from the ORM.

4. Happy to see the initiative, as it could help to decrease the pace of
backend changes and increase the stability, as certain amount of
influencers turn into frontend JS developers.



ср, 9 окт. 2019 г., 7:45 Anurag Awasthi :

> +1
>
> Kind Regards,
> Anurag Awasthi
> 
> From: Marco Sinhoreli 
> Sent: Wednesday, October 9, 2019 4:10 AM
> To: dev@cloudstack.apache.org ;
> us...@cloudstack.apache.org ;
> priv...@cloudstack.apache.org 
> Subject: Re: [VOTE] Primate as modern UI for CloudStack
>
> +1
>
>
> Marco Sinhoreli
> Latam Technical Director
> marco.sinhor...@shapeblue.com
> mobile: +55 11 95656-3636
>
> Rua Gomes de Carvalho, 911 – Sala 316
> Vila Olímpia, São Paulo, SP, Brasil, 04547-003
> Phone: + 55 11 2818-3419
> http://www.shapeblue.com/ | twitter: @shapeblue
>
> Em 07/10/2019 08:31, "Rohit Yadav"  escreveu:
>
> All,
>
> The feedback and response has been positive on the proposal to use
> Primate as the modern UI for CloudStack [1] [2]. Thank you all.
>
> I'm starting this vote (to):
>
>   *   Accept Primate codebase [3] as a project under Apache CloudStack
> project
>   *   Create and host a new repository (cloudstack-primate) and follow
> Github based development workflow (issues, pull requests etc) as we do with
> CloudStack
>   *   Given this is a new project, to encourage cadence until its
> feature completeness the merge criteria is proposed as:
>  *   Manual testing against each PR and/or with screenshots from
> the author or testing contributor, integration with Travis is possible once
> we get JS/UI tests
>  *   At least 1 LGTM from any of the active contributors, we'll
> move this to 2 LGTMs when the codebase reaches feature parity wrt the
> existing/old CloudStack UI
>  *   Squash and merge PRs
>   *   Accept the proposed timeline [1][2] (subject to achievement of
> goals wrt Primate technical release and GA)
>  *   the first technical preview targetted with the winter 2019
> LTS release (~Q1 2020) and release to serve a deprecation notice wrt the
> older UI
>  *   define a release approach before winter LTS
>  *   stop taking feature FRs for old/existing UI after winter 2019
> LTS release, work on upgrade path/documentation from old UI to Primate
>  *   the first Primate GA targetted wrt summer LTS 2020 (~H2
> 2019), but still ship old UI with a final deprecation notice
>  *   old UI codebase removed from codebase in winter 2020 LTS
> release
>
> The vote will be up for the next two weeks to give enough time for PMC
> and the community to gather consensus and still have room for questions,
> feedback and discussions. The results to be shared on/after 21th October
> 2019.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> [1] Primate Proposal:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>
> [2] Email thread reference:
> https://markmail.org/message/z6fuvw4regig7aqb
>
> [3] Primate repo current location:
> https://github.com/shapeblue/primate
>
>
> Regards

Re: [VOTE] Primate as modern UI for CloudStack

2019-10-08 Thread Ivan Kudryavtsev
Hello, community. I know it's just a voting process, but still... a piece
of wisdom from webdev company:

1. Manual testing is an extremely bad idea, you've meet a lot of
regression, much more than the backend typically has.

2. In our teams frontend/backend ratio have shifted from 1/1 to 2/1,
without UI automation QA engineers, so 3/1 is average ratio for real life
high quality web UIs.

3. Try to use/invent some sort of Django-like UI generator frameworks, no
code manually. I see the high risk of fail without that. May be need to add
some sort of metadata to backend first. The Cloudmonkey approach is a great
basic idea... Oracle also has certain frameworks for that. Ideally, to
define the forms and sitemap and generate everything else from the ORM.

4. Happy to see the initiative, as it could help to decrease the pace of
backend changes and increase the stability, as certain amount of
influencers turn into frontend JS developers.



ср, 9 окт. 2019 г., 7:45 Anurag Awasthi :

> +1
>
> Kind Regards,
> Anurag Awasthi
> 
> From: Marco Sinhoreli 
> Sent: Wednesday, October 9, 2019 4:10 AM
> To: dev@cloudstack.apache.org ;
> us...@cloudstack.apache.org ;
> priv...@cloudstack.apache.org 
> Subject: Re: [VOTE] Primate as modern UI for CloudStack
>
> +1
>
>
> Marco Sinhoreli
> Latam Technical Director
> marco.sinhor...@shapeblue.com
> mobile: +55 11 95656-3636
>
> Rua Gomes de Carvalho, 911 – Sala 316
> Vila Olímpia, São Paulo, SP, Brasil, 04547-003
> Phone: + 55 11 2818-3419
> http://www.shapeblue.com/ | twitter: @shapeblue
>
> Em 07/10/2019 08:31, "Rohit Yadav"  escreveu:
>
> All,
>
> The feedback and response has been positive on the proposal to use
> Primate as the modern UI for CloudStack [1] [2]. Thank you all.
>
> I'm starting this vote (to):
>
>   *   Accept Primate codebase [3] as a project under Apache CloudStack
> project
>   *   Create and host a new repository (cloudstack-primate) and follow
> Github based development workflow (issues, pull requests etc) as we do with
> CloudStack
>   *   Given this is a new project, to encourage cadence until its
> feature completeness the merge criteria is proposed as:
>  *   Manual testing against each PR and/or with screenshots from
> the author or testing contributor, integration with Travis is possible once
> we get JS/UI tests
>  *   At least 1 LGTM from any of the active contributors, we'll
> move this to 2 LGTMs when the codebase reaches feature parity wrt the
> existing/old CloudStack UI
>  *   Squash and merge PRs
>   *   Accept the proposed timeline [1][2] (subject to achievement of
> goals wrt Primate technical release and GA)
>  *   the first technical preview targetted with the winter 2019
> LTS release (~Q1 2020) and release to serve a deprecation notice wrt the
> older UI
>  *   define a release approach before winter LTS
>  *   stop taking feature FRs for old/existing UI after winter 2019
> LTS release, work on upgrade path/documentation from old UI to Primate
>  *   the first Primate GA targetted wrt summer LTS 2020 (~H2
> 2019), but still ship old UI with a final deprecation notice
>  *   old UI codebase removed from codebase in winter 2020 LTS
> release
>
> The vote will be up for the next two weeks to give enough time for PMC
> and the community to gather consensus and still have room for questions,
> feedback and discussions. The results to be shared on/after 21th October
> 2019.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> [1] Primate Proposal:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>
> [2] Email thread reference:
> https://markmail.org/message/z6fuvw4regig7aqb
>
> [3] Primate repo current location:
> https://github.com/shapeblue/primate
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
>
>
> anurag.awas...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>


Re: [VOTE] Primate as modern UI for CloudStack

2019-10-08 Thread Anurag Awasthi
+1

Kind Regards,
Anurag Awasthi

From: Marco Sinhoreli 
Sent: Wednesday, October 9, 2019 4:10 AM
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: Re: [VOTE] Primate as modern UI for CloudStack

+1


Marco Sinhoreli
Latam Technical Director
marco.sinhor...@shapeblue.com
mobile: +55 11 95656-3636

Rua Gomes de Carvalho, 911 – Sala 316
Vila Olímpia, São Paulo, SP, Brasil, 04547-003
Phone: + 55 11 2818-3419
http://www.shapeblue.com/ | twitter: @shapeblue

Em 07/10/2019 08:31, "Rohit Yadav"  escreveu:

All,

The feedback and response has been positive on the proposal to use Primate 
as the modern UI for CloudStack [1] [2]. Thank you all.

I'm starting this vote (to):

  *   Accept Primate codebase [3] as a project under Apache CloudStack 
project
  *   Create and host a new repository (cloudstack-primate) and follow 
Github based development workflow (issues, pull requests etc) as we do with 
CloudStack
  *   Given this is a new project, to encourage cadence until its feature 
completeness the merge criteria is proposed as:
 *   Manual testing against each PR and/or with screenshots from the 
author or testing contributor, integration with Travis is possible once we get 
JS/UI tests
 *   At least 1 LGTM from any of the active contributors, we'll move 
this to 2 LGTMs when the codebase reaches feature parity wrt the existing/old 
CloudStack UI
 *   Squash and merge PRs
  *   Accept the proposed timeline [1][2] (subject to achievement of goals 
wrt Primate technical release and GA)
 *   the first technical preview targetted with the winter 2019 LTS 
release (~Q1 2020) and release to serve a deprecation notice wrt the older UI
 *   define a release approach before winter LTS
 *   stop taking feature FRs for old/existing UI after winter 2019 LTS 
release, work on upgrade path/documentation from old UI to Primate
 *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019), but 
still ship old UI with a final deprecation notice
 *   old UI codebase removed from codebase in winter 2020 LTS release

The vote will be up for the next two weeks to give enough time for PMC and 
the community to gather consensus and still have room for questions, feedback 
and discussions. The results to be shared on/after 21th October 2019.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

[1] Primate Proposal:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI

[2] Email thread reference:
https://markmail.org/message/z6fuvw4regig7aqb

[3] Primate repo current location: https://github.com/shapeblue/primate


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue






anurag.awas...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 



Re: [VOTE] Primate as modern UI for CloudStack

2019-10-08 Thread Marco Sinhoreli
+1
 

Marco Sinhoreli
Latam Technical Director
marco.sinhor...@shapeblue.com
mobile: +55 11 95656-3636
 
Rua Gomes de Carvalho, 911 – Sala 316
Vila Olímpia, São Paulo, SP, Brasil, 04547-003
Phone: + 55 11 2818-3419
http://www.shapeblue.com/ | twitter: @shapeblue

Em 07/10/2019 08:31, "Rohit Yadav"  escreveu:

All,

The feedback and response has been positive on the proposal to use Primate 
as the modern UI for CloudStack [1] [2]. Thank you all.

I'm starting this vote (to):

  *   Accept Primate codebase [3] as a project under Apache CloudStack 
project
  *   Create and host a new repository (cloudstack-primate) and follow 
Github based development workflow (issues, pull requests etc) as we do with 
CloudStack
  *   Given this is a new project, to encourage cadence until its feature 
completeness the merge criteria is proposed as:
 *   Manual testing against each PR and/or with screenshots from the 
author or testing contributor, integration with Travis is possible once we get 
JS/UI tests
 *   At least 1 LGTM from any of the active contributors, we'll move 
this to 2 LGTMs when the codebase reaches feature parity wrt the existing/old 
CloudStack UI
 *   Squash and merge PRs
  *   Accept the proposed timeline [1][2] (subject to achievement of goals 
wrt Primate technical release and GA)
 *   the first technical preview targetted with the winter 2019 LTS 
release (~Q1 2020) and release to serve a deprecation notice wrt the older UI
 *   define a release approach before winter LTS
 *   stop taking feature FRs for old/existing UI after winter 2019 LTS 
release, work on upgrade path/documentation from old UI to Primate
 *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019), but 
still ship old UI with a final deprecation notice
 *   old UI codebase removed from codebase in winter 2020 LTS release

The vote will be up for the next two weeks to give enough time for PMC and 
the community to gather consensus and still have room for questions, feedback 
and discussions. The results to be shared on/after 21th October 2019.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

[1] Primate Proposal:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI

[2] Email thread reference:
https://markmail.org/message/z6fuvw4regig7aqb

[3] Primate repo current location: https://github.com/shapeblue/primate


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 





Re: [VOTE] Primate as modern UI for CloudStack

2019-10-08 Thread Milamber

+1 binding
Thanks

On 07/10/2019 12:31, Rohit Yadav wrote:

All,

The feedback and response has been positive on the proposal to use Primate as 
the modern UI for CloudStack [1] [2]. Thank you all.

I'm starting this vote (to):

   *   Accept Primate codebase [3] as a project under Apache CloudStack project
   *   Create and host a new repository (cloudstack-primate) and follow Github 
based development workflow (issues, pull requests etc) as we do with CloudStack
   *   Given this is a new project, to encourage cadence until its feature 
completeness the merge criteria is proposed as:
  *   Manual testing against each PR and/or with screenshots from the 
author or testing contributor, integration with Travis is possible once we get 
JS/UI tests
  *   At least 1 LGTM from any of the active contributors, we'll move this 
to 2 LGTMs when the codebase reaches feature parity wrt the existing/old 
CloudStack UI
  *   Squash and merge PRs
   *   Accept the proposed timeline [1][2] (subject to achievement of goals wrt 
Primate technical release and GA)
  *   the first technical preview targetted with the winter 2019 LTS 
release (~Q1 2020) and release to serve a deprecation notice wrt the older UI
  *   define a release approach before winter LTS
  *   stop taking feature FRs for old/existing UI after winter 2019 LTS 
release, work on upgrade path/documentation from old UI to Primate
  *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019), but 
still ship old UI with a final deprecation notice
  *   old UI codebase removed from codebase in winter 2020 LTS release

The vote will be up for the next two weeks to give enough time for PMC and the 
community to gather consensus and still have room for questions, feedback and 
discussions. The results to be shared on/after 21th October 2019.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

[1] Primate Proposal:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI

[2] Email thread reference:
https://markmail.org/message/z6fuvw4regig7aqb

[3] Primate repo current location: https://github.com/shapeblue/primate


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
   
  







RE: [VOTE] Primate as modern UI for CloudStack

2019-10-08 Thread Giles Sirett
+1 (binding, although I don’t think that matters if we're not voting on a 
release)


Kind regards
Giles

giles.sir...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-Original Message-
From: Alex Ball  
Sent: 08 October 2019 13:28
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Re: [VOTE] Primate as modern UI for CloudStack

+1 binding

-Alex Ball
CITO
QX <http://qx.net>.net <http://qx.net>
859.721.0128- Direct Line
859.255.1928 x230
859.255.1798 - Fax
awb...@qx.net <mailto:awb...@qx.net>

On 10/8/2019 7:10 AM, Gabriel Beims Bräscher wrote:
> +1 (binding)
>
> On Tue, Oct 8, 2019, 07:48 Syed Ahmed  wrote:
>
>> +1 binding
>>
>> On Tue., Oct. 8, 2019, 4:14 p.m. Will Stevens, 
>> 
>> wrote:
>>
>>> +1 (binding)
>>>
>>> On Mon, Oct 7, 2019, 7:31 AM Rohit Yadav 
>>> wrote:
>>>
>>>> All,
>>>>
>>>> The feedback and response has been positive on the proposal to use
>>> Primate
>>>> as the modern UI for CloudStack [1] [2]. Thank you all.
>>>>
>>>> I'm starting this vote (to):
>>>>
>>>>*   Accept Primate codebase [3] as a project under Apache CloudStack
>>>> project
>>>>*   Create and host a new repository (cloudstack-primate) and follow
>>>> Github based development workflow (issues, pull requests etc) as we 
>>>> do
>>> with
>>>> CloudStack
>>>>*   Given this is a new project, to encourage cadence until its
>> feature
>>>> completeness the merge criteria is proposed as:
>>>>   *   Manual testing against each PR and/or with screenshots from
>> the
>>>> author or testing contributor, integration with Travis is possible 
>>>> once
>>> we
>>>> get JS/UI tests
>>>>   *   At least 1 LGTM from any of the active contributors, we'll
>> move
>>>> this to 2 LGTMs when the codebase reaches feature parity wrt the 
>>>> existing/old CloudStack UI
>>>>   *   Squash and merge PRs
>>>>*   Accept the proposed timeline [1][2] (subject to achievement of
>>> goals
>>>> wrt Primate technical release and GA)
>>>>   *   the first technical preview targetted with the winter 2019 LTS
>>>> release (~Q1 2020) and release to serve a deprecation notice wrt 
>>>> the
>>> older
>>>> UI
>>>>   *   define a release approach before winter LTS
>>>>   *   stop taking feature FRs for old/existing UI after winter 2019
>>> LTS
>>>> release, work on upgrade path/documentation from old UI to Primate
>>>>   *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019),
>>>> but still ship old UI with a final deprecation notice
>>>>   *   old UI codebase removed from codebase in winter 2020 LTS
>> release
>>>> The vote will be up for the next two weeks to give enough time for 
>>>> PMC
>>> and
>>>> the community to gather consensus and still have room for 
>>>> questions, feedback and discussions. The results to be shared 
>>>> on/after 21th
>> October
>>>> 2019.
>>>>
>>>> For sanity in tallying the vote, can PMC members please be sure to 
>>>> indicate "(binding)" with their vote?
>>>>
>>>> [ ] +1  approve
>>>> [ ] +0  no opinion
>>>> [ ] -1  disapprove (and reason why)
>>>>
>>>> [1] Primate Proposal:
>>>>
>>>>
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+Cl
>> oudStack+Primate+UI
>>>> [2] Email thread reference:
>>>> https://markmail.org/message/z6fuvw4regig7aqb
>>>>
>>>> [3] Primate repo current location:
>> https://github.com/shapeblue/primate
>>>>
>>>> Regards,
>>>>
>>>> Rohit Yadav
>>>>
>>>> Software Architect, ShapeBlue
>>>>
>>>> https://www.shapeblue.com
>>>>
>>>> rohit.ya...@shapeblue.com
>>>> www.shapeblue.com
>>>> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>>>>
>>>>
>>>>
>>>>



Re: [VOTE] Primate as modern UI for CloudStack

2019-10-08 Thread Gabriel Beims Bräscher
+1 (binding)

On Tue, Oct 8, 2019, 07:48 Syed Ahmed  wrote:

> +1 binding
>
> On Tue., Oct. 8, 2019, 4:14 p.m. Will Stevens, 
> wrote:
>
> > +1 (binding)
> >
> > On Mon, Oct 7, 2019, 7:31 AM Rohit Yadav 
> > wrote:
> >
> > > All,
> > >
> > > The feedback and response has been positive on the proposal to use
> > Primate
> > > as the modern UI for CloudStack [1] [2]. Thank you all.
> > >
> > > I'm starting this vote (to):
> > >
> > >   *   Accept Primate codebase [3] as a project under Apache CloudStack
> > > project
> > >   *   Create and host a new repository (cloudstack-primate) and follow
> > > Github based development workflow (issues, pull requests etc) as we do
> > with
> > > CloudStack
> > >   *   Given this is a new project, to encourage cadence until its
> feature
> > > completeness the merge criteria is proposed as:
> > >  *   Manual testing against each PR and/or with screenshots from
> the
> > > author or testing contributor, integration with Travis is possible once
> > we
> > > get JS/UI tests
> > >  *   At least 1 LGTM from any of the active contributors, we'll
> move
> > > this to 2 LGTMs when the codebase reaches feature parity wrt the
> > > existing/old CloudStack UI
> > >  *   Squash and merge PRs
> > >   *   Accept the proposed timeline [1][2] (subject to achievement of
> > goals
> > > wrt Primate technical release and GA)
> > >  *   the first technical preview targetted with the winter 2019 LTS
> > > release (~Q1 2020) and release to serve a deprecation notice wrt the
> > older
> > > UI
> > >  *   define a release approach before winter LTS
> > >  *   stop taking feature FRs for old/existing UI after winter 2019
> > LTS
> > > release, work on upgrade path/documentation from old UI to Primate
> > >  *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019),
> > > but still ship old UI with a final deprecation notice
> > >  *   old UI codebase removed from codebase in winter 2020 LTS
> release
> > >
> > > The vote will be up for the next two weeks to give enough time for PMC
> > and
> > > the community to gather consensus and still have room for questions,
> > > feedback and discussions. The results to be shared on/after 21th
> October
> > > 2019.
> > >
> > > For sanity in tallying the vote, can PMC members please be sure to
> > > indicate "(binding)" with their vote?
> > >
> > > [ ] +1  approve
> > > [ ] +0  no opinion
> > > [ ] -1  disapprove (and reason why)
> > >
> > > [1] Primate Proposal:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
> > >
> > > [2] Email thread reference:
> > > https://markmail.org/message/z6fuvw4regig7aqb
> > >
> > > [3] Primate repo current location:
> https://github.com/shapeblue/primate
> > >
> > >
> > > Regards,
> > >
> > > Rohit Yadav
> > >
> > > Software Architect, ShapeBlue
> > >
> > > https://www.shapeblue.com
> > >
> > > rohit.ya...@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > @shapeblue
> > >
> > >
> > >
> > >
> >
>


Re: [VOTE] Primate as modern UI for CloudStack

2019-10-08 Thread Syed Ahmed
+1 binding

On Tue., Oct. 8, 2019, 4:14 p.m. Will Stevens, 
wrote:

> +1 (binding)
>
> On Mon, Oct 7, 2019, 7:31 AM Rohit Yadav 
> wrote:
>
> > All,
> >
> > The feedback and response has been positive on the proposal to use
> Primate
> > as the modern UI for CloudStack [1] [2]. Thank you all.
> >
> > I'm starting this vote (to):
> >
> >   *   Accept Primate codebase [3] as a project under Apache CloudStack
> > project
> >   *   Create and host a new repository (cloudstack-primate) and follow
> > Github based development workflow (issues, pull requests etc) as we do
> with
> > CloudStack
> >   *   Given this is a new project, to encourage cadence until its feature
> > completeness the merge criteria is proposed as:
> >  *   Manual testing against each PR and/or with screenshots from the
> > author or testing contributor, integration with Travis is possible once
> we
> > get JS/UI tests
> >  *   At least 1 LGTM from any of the active contributors, we'll move
> > this to 2 LGTMs when the codebase reaches feature parity wrt the
> > existing/old CloudStack UI
> >  *   Squash and merge PRs
> >   *   Accept the proposed timeline [1][2] (subject to achievement of
> goals
> > wrt Primate technical release and GA)
> >  *   the first technical preview targetted with the winter 2019 LTS
> > release (~Q1 2020) and release to serve a deprecation notice wrt the
> older
> > UI
> >  *   define a release approach before winter LTS
> >  *   stop taking feature FRs for old/existing UI after winter 2019
> LTS
> > release, work on upgrade path/documentation from old UI to Primate
> >  *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019),
> > but still ship old UI with a final deprecation notice
> >  *   old UI codebase removed from codebase in winter 2020 LTS release
> >
> > The vote will be up for the next two weeks to give enough time for PMC
> and
> > the community to gather consensus and still have room for questions,
> > feedback and discussions. The results to be shared on/after 21th October
> > 2019.
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> > indicate "(binding)" with their vote?
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > [1] Primate Proposal:
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
> >
> > [2] Email thread reference:
> > https://markmail.org/message/z6fuvw4regig7aqb
> >
> > [3] Primate repo current location: https://github.com/shapeblue/primate
> >
> >
> > Regards,
> >
> > Rohit Yadav
> >
> > Software Architect, ShapeBlue
> >
> > https://www.shapeblue.com
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
>


Re: [VOTE] Primate as modern UI for CloudStack

2019-10-08 Thread Will Stevens
+1 (binding)

On Mon, Oct 7, 2019, 7:31 AM Rohit Yadav  wrote:

> All,
>
> The feedback and response has been positive on the proposal to use Primate
> as the modern UI for CloudStack [1] [2]. Thank you all.
>
> I'm starting this vote (to):
>
>   *   Accept Primate codebase [3] as a project under Apache CloudStack
> project
>   *   Create and host a new repository (cloudstack-primate) and follow
> Github based development workflow (issues, pull requests etc) as we do with
> CloudStack
>   *   Given this is a new project, to encourage cadence until its feature
> completeness the merge criteria is proposed as:
>  *   Manual testing against each PR and/or with screenshots from the
> author or testing contributor, integration with Travis is possible once we
> get JS/UI tests
>  *   At least 1 LGTM from any of the active contributors, we'll move
> this to 2 LGTMs when the codebase reaches feature parity wrt the
> existing/old CloudStack UI
>  *   Squash and merge PRs
>   *   Accept the proposed timeline [1][2] (subject to achievement of goals
> wrt Primate technical release and GA)
>  *   the first technical preview targetted with the winter 2019 LTS
> release (~Q1 2020) and release to serve a deprecation notice wrt the older
> UI
>  *   define a release approach before winter LTS
>  *   stop taking feature FRs for old/existing UI after winter 2019 LTS
> release, work on upgrade path/documentation from old UI to Primate
>  *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019),
> but still ship old UI with a final deprecation notice
>  *   old UI codebase removed from codebase in winter 2020 LTS release
>
> The vote will be up for the next two weeks to give enough time for PMC and
> the community to gather consensus and still have room for questions,
> feedback and discussions. The results to be shared on/after 21th October
> 2019.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> [1] Primate Proposal:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>
> [2] Email thread reference:
> https://markmail.org/message/z6fuvw4regig7aqb
>
> [3] Primate repo current location: https://github.com/shapeblue/primate
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>


Re: [VOTE] Primate as modern UI for CloudStack

2019-10-08 Thread Boris Stoyanov
+1 (binding) 

There's been a need for a new UI from quite a long time and I'm really excited 
about it, looking forward to play with it. 

Boris. 

On 7.10.19, 14:31, "Rohit Yadav"  wrote:

All,

The feedback and response has been positive on the proposal to use Primate 
as the modern UI for CloudStack [1] [2]. Thank you all.

I'm starting this vote (to):

  *   Accept Primate codebase [3] as a project under Apache CloudStack 
project
  *   Create and host a new repository (cloudstack-primate) and follow 
Github based development workflow (issues, pull requests etc) as we do with 
CloudStack
  *   Given this is a new project, to encourage cadence until its feature 
completeness the merge criteria is proposed as:
 *   Manual testing against each PR and/or with screenshots from the 
author or testing contributor, integration with Travis is possible once we get 
JS/UI tests
 *   At least 1 LGTM from any of the active contributors, we'll move 
this to 2 LGTMs when the codebase reaches feature parity wrt the existing/old 
CloudStack UI
 *   Squash and merge PRs
  *   Accept the proposed timeline [1][2] (subject to achievement of goals 
wrt Primate technical release and GA)
 *   the first technical preview targetted with the winter 2019 LTS 
release (~Q1 2020) and release to serve a deprecation notice wrt the older UI
 *   define a release approach before winter LTS
 *   stop taking feature FRs for old/existing UI after winter 2019 LTS 
release, work on upgrade path/documentation from old UI to Primate
 *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019), but 
still ship old UI with a final deprecation notice
 *   old UI codebase removed from codebase in winter 2020 LTS release

The vote will be up for the next two weeks to give enough time for PMC and 
the community to gather consensus and still have room for questions, feedback 
and discussions. The results to be shared on/after 21th October 2019.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

[1] Primate Proposal:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI

[2] Email thread reference:
https://markmail.org/message/z6fuvw4regig7aqb

[3] Primate repo current location: https://github.com/shapeblue/primate


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 




boris.stoya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 



Re:Re: [VOTE] Primate as modern UI for CloudStack

2019-10-08 Thread Haijiao
+1, could be a major change leading to CloudStack 5.0




At 2019-10-08 04:11:28, "Ezequiel Mc Govern"  
wrote:
>+1
>
>> On 7 Oct 2019, at 08:31, Rohit Yadav  wrote:
>> 
>> All,
>> 
>> The feedback and response has been positive on the proposal to use Primate 
>> as the modern UI for CloudStack [1] [2]. Thank you all.
>> 
>> I'm starting this vote (to):
>> 
>>  *   Accept Primate codebase [3] as a project under Apache CloudStack project
>>  *   Create and host a new repository (cloudstack-primate) and follow Github 
>> based development workflow (issues, pull requests etc) as we do with 
>> CloudStack
>>  *   Given this is a new project, to encourage cadence until its feature 
>> completeness the merge criteria is proposed as:
>> *   Manual testing against each PR and/or with screenshots from the 
>> author or testing contributor, integration with Travis is possible once we 
>> get JS/UI tests
>> *   At least 1 LGTM from any of the active contributors, we'll move this 
>> to 2 LGTMs when the codebase reaches feature parity wrt the existing/old 
>> CloudStack UI
>> *   Squash and merge PRs
>>  *   Accept the proposed timeline [1][2] (subject to achievement of goals 
>> wrt Primate technical release and GA)
>> *   the first technical preview targetted with the winter 2019 LTS 
>> release (~Q1 2020) and release to serve a deprecation notice wrt the older UI
>> *   define a release approach before winter LTS
>> *   stop taking feature FRs for old/existing UI after winter 2019 LTS 
>> release, work on upgrade path/documentation from old UI to Primate
>> *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019), but 
>> still ship old UI with a final deprecation notice
>> *   old UI codebase removed from codebase in winter 2020 LTS release
>> 
>> The vote will be up for the next two weeks to give enough time for PMC and 
>> the community to gather consensus and still have room for questions, 
>> feedback and discussions. The results to be shared on/after 21th October 
>> 2019.
>> 
>> For sanity in tallying the vote, can PMC members please be sure to indicate 
>> "(binding)" with their vote?
>> 
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>> 
>> [1] Primate Proposal:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>> 
>> [2] Email thread reference:
>> https://markmail.org/message/z6fuvw4regig7aqb
>> 
>> [3] Primate repo current location: https://github.com/shapeblue/primate
>> 
>> 
>> Regards,
>> 
>> Rohit Yadav
>> 
>> Software Architect, ShapeBlue
>> 
>> https://www.shapeblue.com
>> 
>> rohit.ya...@shapeblue.com 
>> www.shapeblue.com
>> Amadeus House, Floral Street, London  WC2E 9DPUK
>> @shapeblue
>> 
>> 
>> 


Re: [VOTE] Primate as modern UI for CloudStack

2019-10-07 Thread Ezequiel Mc Govern
+1

> On 7 Oct 2019, at 08:31, Rohit Yadav  wrote:
> 
> All,
> 
> The feedback and response has been positive on the proposal to use Primate as 
> the modern UI for CloudStack [1] [2]. Thank you all.
> 
> I'm starting this vote (to):
> 
>  *   Accept Primate codebase [3] as a project under Apache CloudStack project
>  *   Create and host a new repository (cloudstack-primate) and follow Github 
> based development workflow (issues, pull requests etc) as we do with 
> CloudStack
>  *   Given this is a new project, to encourage cadence until its feature 
> completeness the merge criteria is proposed as:
> *   Manual testing against each PR and/or with screenshots from the 
> author or testing contributor, integration with Travis is possible once we 
> get JS/UI tests
> *   At least 1 LGTM from any of the active contributors, we'll move this 
> to 2 LGTMs when the codebase reaches feature parity wrt the existing/old 
> CloudStack UI
> *   Squash and merge PRs
>  *   Accept the proposed timeline [1][2] (subject to achievement of goals wrt 
> Primate technical release and GA)
> *   the first technical preview targetted with the winter 2019 LTS 
> release (~Q1 2020) and release to serve a deprecation notice wrt the older UI
> *   define a release approach before winter LTS
> *   stop taking feature FRs for old/existing UI after winter 2019 LTS 
> release, work on upgrade path/documentation from old UI to Primate
> *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019), but 
> still ship old UI with a final deprecation notice
> *   old UI codebase removed from codebase in winter 2020 LTS release
> 
> The vote will be up for the next two weeks to give enough time for PMC and 
> the community to gather consensus and still have room for questions, feedback 
> and discussions. The results to be shared on/after 21th October 2019.
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate 
> "(binding)" with their vote?
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> [1] Primate Proposal:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
> 
> [2] Email thread reference:
> https://markmail.org/message/z6fuvw4regig7aqb
> 
> [3] Primate repo current location: https://github.com/shapeblue/primate
> 
> 
> Regards,
> 
> Rohit Yadav
> 
> Software Architect, ShapeBlue
> 
> https://www.shapeblue.com
> 
> rohit.ya...@shapeblue.com 
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
> 
> 
> 



Re: [VOTE] Primate as modern UI for CloudStack

2019-10-07 Thread Wido den Hollander
+1 !!

On 10/7/19 1:31 PM, Rohit Yadav wrote:
> All,
> 
> The feedback and response has been positive on the proposal to use Primate as 
> the modern UI for CloudStack [1] [2]. Thank you all.
> 
> I'm starting this vote (to):
> 
>   *   Accept Primate codebase [3] as a project under Apache CloudStack project
>   *   Create and host a new repository (cloudstack-primate) and follow Github 
> based development workflow (issues, pull requests etc) as we do with 
> CloudStack
>   *   Given this is a new project, to encourage cadence until its feature 
> completeness the merge criteria is proposed as:
>  *   Manual testing against each PR and/or with screenshots from the 
> author or testing contributor, integration with Travis is possible once we 
> get JS/UI tests
>  *   At least 1 LGTM from any of the active contributors, we'll move this 
> to 2 LGTMs when the codebase reaches feature parity wrt the existing/old 
> CloudStack UI
>  *   Squash and merge PRs
>   *   Accept the proposed timeline [1][2] (subject to achievement of goals 
> wrt Primate technical release and GA)
>  *   the first technical preview targetted with the winter 2019 LTS 
> release (~Q1 2020) and release to serve a deprecation notice wrt the older UI
>  *   define a release approach before winter LTS
>  *   stop taking feature FRs for old/existing UI after winter 2019 LTS 
> release, work on upgrade path/documentation from old UI to Primate
>  *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019), but 
> still ship old UI with a final deprecation notice
>  *   old UI codebase removed from codebase in winter 2020 LTS release
> 
> The vote will be up for the next two weeks to give enough time for PMC and 
> the community to gather consensus and still have room for questions, feedback 
> and discussions. The results to be shared on/after 21th October 2019.
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate 
> "(binding)" with their vote?
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> [1] Primate Proposal:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
> 
> [2] Email thread reference:
> https://markmail.org/message/z6fuvw4regig7aqb
> 
> [3] Primate repo current location: https://github.com/shapeblue/primate
> 
> 
> Regards,
> 
> Rohit Yadav
> 
> Software Architect, ShapeBlue
> 
> https://www.shapeblue.com
> 
> rohit.ya...@shapeblue.com 
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>   
>  
> 
> 


Re: [VOTE] Primate as modern UI for CloudStack

2019-10-07 Thread Nux!

+1 (binding)

A welcome change, the current UI is horrible.

---
Sent from the Delta quadrant using Borg technology!

On 2019-10-07 12:31, Rohit Yadav wrote:

All,

The feedback and response has been positive on the proposal to use
Primate as the modern UI for CloudStack [1] [2]. Thank you all.

I'm starting this vote (to):

  *   Accept Primate codebase [3] as a project under Apache CloudStack 
project

  *   Create and host a new repository (cloudstack-primate) and follow
Github based development workflow (issues, pull requests etc) as we do
with CloudStack
  *   Given this is a new project, to encourage cadence until its
feature completeness the merge criteria is proposed as:
 *   Manual testing against each PR and/or with screenshots from
the author or testing contributor, integration with Travis is possible
once we get JS/UI tests
 *   At least 1 LGTM from any of the active contributors, we'll
move this to 2 LGTMs when the codebase reaches feature parity wrt the
existing/old CloudStack UI
 *   Squash and merge PRs
  *   Accept the proposed timeline [1][2] (subject to achievement of
goals wrt Primate technical release and GA)
 *   the first technical preview targetted with the winter 2019
LTS release (~Q1 2020) and release to serve a deprecation notice wrt
the older UI
 *   define a release approach before winter LTS
 *   stop taking feature FRs for old/existing UI after winter 2019
LTS release, work on upgrade path/documentation from old UI to Primate
 *   the first Primate GA targetted wrt summer LTS 2020 (~H2
2019), but still ship old UI with a final deprecation notice
 *   old UI codebase removed from codebase in winter 2020 LTS 
release


The vote will be up for the next two weeks to give enough time for PMC
and the community to gather consensus and still have room for
questions, feedback and discussions. The results to be shared on/after
21th October 2019.

For sanity in tallying the vote, can PMC members please be sure to
indicate "(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

[1] Primate Proposal:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI

[2] Email thread reference:
https://markmail.org/message/z6fuvw4regig7aqb

[3] Primate repo current location: https://github.com/shapeblue/primate


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue


Re: [VOTE] Primate as modern UI for CloudStack

2019-10-07 Thread Nitin Maharana
+1

On Mon, 7 Oct 2019 at 8:39 PM, Sven Vogel  wrote:

> +1 (binding)
>
>
> __
>
> Sven Vogel
> Teamlead Platform
>
> EWERK DIGITAL GmbH
> Brühl 24, D-04109 Leipzig
> <https://www.google.com/maps/search/Br%C3%BChl+24,+D-04109+Leipzig?entry=gmail=g>
> P +49 341 42649 - 99
> F +49 341 42649 - 98
> s.vo...@ewerk.com
> www.ewerk.com
>
> Geschäftsführer:
> Dr. Erik Wende, Hendrik Schubert, Frank Richter
> Registergericht: Leipzig HRB 9065
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 2-1:2011
>
> EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
>
> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
> > Am 07.10.2019 um 16:18 schrieb Nicolas Vazquez <
> nicolas.vazq...@shapeblue.com>:
> >
> > +1
> >
> >
> > Regards,
> >
> > Nicolas Vazquez
> >
> > ________________
> > From: Andrija Panic 
> > Sent: Monday, October 7, 2019 11:16 AM
> > To: users 
> > Cc: dev@cloudstack.apache.org ;
> priv...@cloudstack.apache.org 
> > Subject: Re: [VOTE] Primate as modern UI for CloudStack
> >
> > +1 (binding)
> >
> >
> > nicolas.vazq...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> > On Mon, 7 Oct 2019 at 15:53, Simon Weller 
> wrote:
> >
> >>
> >> +1 (binding)
> >> 
> >> From: Rohit Yadav 
> >> Sent: Monday, October 7, 2019 6:31 AM
> >> To: dev@cloudstack.apache.org ;
> >> us...@cloudstack.apache.org ;
> >> priv...@cloudstack.apache.org 
> >> Subject: [VOTE] Primate as modern UI for CloudStack
> >>
> >> All,
> >>
> >> The feedback and response has been positive on the proposal to use
> Primate
> >> as the modern UI for CloudStack [1] [2]. Thank you all.
> >>
> >> I'm starting this vote (to):
> >>
> >>  *   Accept Primate codebase [3] as a project under Apache CloudStack
> >> project
> >>  *   Create and host a new repository (cloudstack-primate) and follow
> >> Github based development workflow (issues, pull requests etc) as we do
> with
> >> CloudStack
> >>  *   Given this is a new project, to encourage cadence until its feature
> >> completeness the merge criteria is proposed as:
> >> *   Manual testing against each PR and/or with screenshots from the
> >> author or testing contributor, integration with Travis is possible once
> we
> >> get JS/UI tests
> >> *   At least 1 LGTM from any of the active contributors, we'll move
> >> this to 2 LGTMs when the codebase reaches feature parity wrt the
> >> existing/old CloudStack UI
> >> *   Squash and merge PRs
> >>  *   Accept the proposed timeline [1][2] (subject to achievement of
> goals
> >> wrt Primate technical release and GA)
> >> *   the first technical preview targetted with the winter 2019 LTS
> >> release (~Q1 2020) and release to serve a deprecation notice wrt the
> older
> >> UI
> >> *   define a release approach before winter LTS
> >> *   stop taking feature FRs for old/existing UI after winter 2019
> LTS
> >> release, work on upgrade path/documentation from old UI to Primate
> >> *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019),
> >> but still ship old UI with a final deprecation notice
> >> *   old UI codebase removed from codebase in winter 2020 LTS release
> >>
> >> The vote will be up for the next two weeks to give enough time for PMC
> and
> >> the community 

Re: [VOTE] Primate as modern UI for CloudStack

2019-10-07 Thread Sven Vogel
+1 (binding)


__

Sven Vogel
Teamlead Platform

EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
s.vo...@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter
Registergericht: Leipzig HRB 9065

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

EWERK-Blog | LinkedIn | Xing | Twitter | Facebook

Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist 
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der 
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, 
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte 
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die 
E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen 
Dank.

The contents of this e-mail (including any attachments) are confidential and 
may be legally privileged. If you are not the intended recipient of this 
e-mail, any disclosure, copying, distribution or use of its contents is 
strictly prohibited, and you should please notify the sender immediately and 
then delete it (including any attachments) from your system. Thank you.
> Am 07.10.2019 um 16:18 schrieb Nicolas Vazquez 
> :
>
> +1
>
>
> Regards,
>
> Nicolas Vazquez
>
> 
> From: Andrija Panic 
> Sent: Monday, October 7, 2019 11:16 AM
> To: users 
> Cc: dev@cloudstack.apache.org ; 
> priv...@cloudstack.apache.org 
> Subject: Re: [VOTE] Primate as modern UI for CloudStack
>
> +1 (binding)
>
>
> nicolas.vazq...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
> On Mon, 7 Oct 2019 at 15:53, Simon Weller  wrote:
>
>>
>> +1 (binding)
>> 
>> From: Rohit Yadav 
>> Sent: Monday, October 7, 2019 6:31 AM
>> To: dev@cloudstack.apache.org ;
>> us...@cloudstack.apache.org ;
>> priv...@cloudstack.apache.org 
>> Subject: [VOTE] Primate as modern UI for CloudStack
>>
>> All,
>>
>> The feedback and response has been positive on the proposal to use Primate
>> as the modern UI for CloudStack [1] [2]. Thank you all.
>>
>> I'm starting this vote (to):
>>
>>  *   Accept Primate codebase [3] as a project under Apache CloudStack
>> project
>>  *   Create and host a new repository (cloudstack-primate) and follow
>> Github based development workflow (issues, pull requests etc) as we do with
>> CloudStack
>>  *   Given this is a new project, to encourage cadence until its feature
>> completeness the merge criteria is proposed as:
>> *   Manual testing against each PR and/or with screenshots from the
>> author or testing contributor, integration with Travis is possible once we
>> get JS/UI tests
>> *   At least 1 LGTM from any of the active contributors, we'll move
>> this to 2 LGTMs when the codebase reaches feature parity wrt the
>> existing/old CloudStack UI
>> *   Squash and merge PRs
>>  *   Accept the proposed timeline [1][2] (subject to achievement of goals
>> wrt Primate technical release and GA)
>> *   the first technical preview targetted with the winter 2019 LTS
>> release (~Q1 2020) and release to serve a deprecation notice wrt the older
>> UI
>> *   define a release approach before winter LTS
>> *   stop taking feature FRs for old/existing UI after winter 2019 LTS
>> release, work on upgrade path/documentation from old UI to Primate
>> *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019),
>> but still ship old UI with a final deprecation notice
>> *   old UI codebase removed from codebase in winter 2020 LTS release
>>
>> The vote will be up for the next two weeks to give enough time for PMC and
>> the community to gather consensus and still have room for questions,
>> feedback and discussions. The results to be shared on/after 21th October
>> 2019.
>>
>> For sanity in tallying the vote, can PMC members please be sure to
>> indicate "(binding)" with their vote?
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> [1] Primate Proposal:
>>
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>>
>> [2] Email thread reference:
>> https://markmail.org/message/z6fuvw4regig7aqb
>>
>> [3] Primate repo current location: https://github.com/shapeblue/primate
>>
>>
>> Regards,
>>
>> Rohit Yadav
>>
>> Software Architect, ShapeBlue
>>
>> https://www.shapeblue.com
>>
>> rohit.ya...@shapeblue.com
>> www.shapeblue.com<http://www.shapeblue.com>
>> Amadeus House, Floral Street, London  WC2E 9DPUK
>> @shapeblue
>>
>>
>>
>>
>
> --
>
> Andrija Panić



Re: [VOTE] Primate as modern UI for CloudStack

2019-10-07 Thread Nicolas Vazquez
+1


Regards,

Nicolas Vazquez


From: Andrija Panic 
Sent: Monday, October 7, 2019 11:16 AM
To: users 
Cc: dev@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: Re: [VOTE] Primate as modern UI for CloudStack

+1 (binding)


nicolas.vazq...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

On Mon, 7 Oct 2019 at 15:53, Simon Weller  wrote:

>
> +1 (binding)
> 
> From: Rohit Yadav 
> Sent: Monday, October 7, 2019 6:31 AM
> To: dev@cloudstack.apache.org ;
> us...@cloudstack.apache.org ;
> priv...@cloudstack.apache.org 
> Subject: [VOTE] Primate as modern UI for CloudStack
>
> All,
>
> The feedback and response has been positive on the proposal to use Primate
> as the modern UI for CloudStack [1] [2]. Thank you all.
>
> I'm starting this vote (to):
>
>   *   Accept Primate codebase [3] as a project under Apache CloudStack
> project
>   *   Create and host a new repository (cloudstack-primate) and follow
> Github based development workflow (issues, pull requests etc) as we do with
> CloudStack
>   *   Given this is a new project, to encourage cadence until its feature
> completeness the merge criteria is proposed as:
>  *   Manual testing against each PR and/or with screenshots from the
> author or testing contributor, integration with Travis is possible once we
> get JS/UI tests
>  *   At least 1 LGTM from any of the active contributors, we'll move
> this to 2 LGTMs when the codebase reaches feature parity wrt the
> existing/old CloudStack UI
>  *   Squash and merge PRs
>   *   Accept the proposed timeline [1][2] (subject to achievement of goals
> wrt Primate technical release and GA)
>  *   the first technical preview targetted with the winter 2019 LTS
> release (~Q1 2020) and release to serve a deprecation notice wrt the older
> UI
>  *   define a release approach before winter LTS
>  *   stop taking feature FRs for old/existing UI after winter 2019 LTS
> release, work on upgrade path/documentation from old UI to Primate
>  *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019),
> but still ship old UI with a final deprecation notice
>  *   old UI codebase removed from codebase in winter 2020 LTS release
>
> The vote will be up for the next two weeks to give enough time for PMC and
> the community to gather consensus and still have room for questions,
> feedback and discussions. The results to be shared on/after 21th October
> 2019.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> [1] Primate Proposal:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>
> [2] Email thread reference:
> https://markmail.org/message/z6fuvw4regig7aqb
>
> [3] Primate repo current location: https://github.com/shapeblue/primate
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

--

Andrija Panić


Re: [VOTE] Primate as modern UI for CloudStack

2019-10-07 Thread Andrija Panic
+1 (binding)

On Mon, 7 Oct 2019 at 15:53, Simon Weller  wrote:

>
> +1 (binding)
> 
> From: Rohit Yadav 
> Sent: Monday, October 7, 2019 6:31 AM
> To: dev@cloudstack.apache.org ;
> us...@cloudstack.apache.org ;
> priv...@cloudstack.apache.org 
> Subject: [VOTE] Primate as modern UI for CloudStack
>
> All,
>
> The feedback and response has been positive on the proposal to use Primate
> as the modern UI for CloudStack [1] [2]. Thank you all.
>
> I'm starting this vote (to):
>
>   *   Accept Primate codebase [3] as a project under Apache CloudStack
> project
>   *   Create and host a new repository (cloudstack-primate) and follow
> Github based development workflow (issues, pull requests etc) as we do with
> CloudStack
>   *   Given this is a new project, to encourage cadence until its feature
> completeness the merge criteria is proposed as:
>  *   Manual testing against each PR and/or with screenshots from the
> author or testing contributor, integration with Travis is possible once we
> get JS/UI tests
>  *   At least 1 LGTM from any of the active contributors, we'll move
> this to 2 LGTMs when the codebase reaches feature parity wrt the
> existing/old CloudStack UI
>  *   Squash and merge PRs
>   *   Accept the proposed timeline [1][2] (subject to achievement of goals
> wrt Primate technical release and GA)
>  *   the first technical preview targetted with the winter 2019 LTS
> release (~Q1 2020) and release to serve a deprecation notice wrt the older
> UI
>  *   define a release approach before winter LTS
>  *   stop taking feature FRs for old/existing UI after winter 2019 LTS
> release, work on upgrade path/documentation from old UI to Primate
>  *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019),
> but still ship old UI with a final deprecation notice
>  *   old UI codebase removed from codebase in winter 2020 LTS release
>
> The vote will be up for the next two weeks to give enough time for PMC and
> the community to gather consensus and still have room for questions,
> feedback and discussions. The results to be shared on/after 21th October
> 2019.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> [1] Primate Proposal:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>
> [2] Email thread reference:
> https://markmail.org/message/z6fuvw4regig7aqb
>
> [3] Primate repo current location: https://github.com/shapeblue/primate
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

-- 

Andrija Panić


Re: [VOTE] Primate as modern UI for CloudStack

2019-10-07 Thread Simon Weller

+1 (binding)

From: Rohit Yadav 
Sent: Monday, October 7, 2019 6:31 AM
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: [VOTE] Primate as modern UI for CloudStack

All,

The feedback and response has been positive on the proposal to use Primate as 
the modern UI for CloudStack [1] [2]. Thank you all.

I'm starting this vote (to):

  *   Accept Primate codebase [3] as a project under Apache CloudStack project
  *   Create and host a new repository (cloudstack-primate) and follow Github 
based development workflow (issues, pull requests etc) as we do with CloudStack
  *   Given this is a new project, to encourage cadence until its feature 
completeness the merge criteria is proposed as:
 *   Manual testing against each PR and/or with screenshots from the author 
or testing contributor, integration with Travis is possible once we get JS/UI 
tests
 *   At least 1 LGTM from any of the active contributors, we'll move this 
to 2 LGTMs when the codebase reaches feature parity wrt the existing/old 
CloudStack UI
 *   Squash and merge PRs
  *   Accept the proposed timeline [1][2] (subject to achievement of goals wrt 
Primate technical release and GA)
 *   the first technical preview targetted with the winter 2019 LTS release 
(~Q1 2020) and release to serve a deprecation notice wrt the older UI
 *   define a release approach before winter LTS
 *   stop taking feature FRs for old/existing UI after winter 2019 LTS 
release, work on upgrade path/documentation from old UI to Primate
 *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019), but 
still ship old UI with a final deprecation notice
 *   old UI codebase removed from codebase in winter 2020 LTS release

The vote will be up for the next two weeks to give enough time for PMC and the 
community to gather consensus and still have room for questions, feedback and 
discussions. The results to be shared on/after 21th October 2019.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

[1] Primate Proposal:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI

[2] Email thread reference:
https://markmail.org/message/z6fuvw4regig7aqb

[3] Primate repo current location: https://github.com/shapeblue/primate


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue





Re: [VOTE] Primate as modern UI for CloudStack

2019-10-07 Thread Tutkowski, Mike
+1


From: Rohit Yadav 
Sent: Monday, October 7, 2019 5:31:15 AM
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: [VOTE] Primate as modern UI for CloudStack

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




All,

The feedback and response has been positive on the proposal to use Primate as 
the modern UI for CloudStack [1] [2]. Thank you all.

I'm starting this vote (to):

  *   Accept Primate codebase [3] as a project under Apache CloudStack project
  *   Create and host a new repository (cloudstack-primate) and follow Github 
based development workflow (issues, pull requests etc) as we do with CloudStack
  *   Given this is a new project, to encourage cadence until its feature 
completeness the merge criteria is proposed as:
 *   Manual testing against each PR and/or with screenshots from the author 
or testing contributor, integration with Travis is possible once we get JS/UI 
tests
 *   At least 1 LGTM from any of the active contributors, we'll move this 
to 2 LGTMs when the codebase reaches feature parity wrt the existing/old 
CloudStack UI
 *   Squash and merge PRs
  *   Accept the proposed timeline [1][2] (subject to achievement of goals wrt 
Primate technical release and GA)
 *   the first technical preview targetted with the winter 2019 LTS release 
(~Q1 2020) and release to serve a deprecation notice wrt the older UI
 *   define a release approach before winter LTS
 *   stop taking feature FRs for old/existing UI after winter 2019 LTS 
release, work on upgrade path/documentation from old UI to Primate
 *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019), but 
still ship old UI with a final deprecation notice
 *   old UI codebase removed from codebase in winter 2020 LTS release

The vote will be up for the next two weeks to give enough time for PMC and the 
community to gather consensus and still have room for questions, feedback and 
discussions. The results to be shared on/after 21th October 2019.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

[1] Primate Proposal:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI

[2] Email thread reference:
https://markmail.org/message/z6fuvw4regig7aqb

[3] Primate repo current location: https://github.com/shapeblue/primate


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue





[VOTE] Primate as modern UI for CloudStack

2019-10-07 Thread Rohit Yadav
All,

The feedback and response has been positive on the proposal to use Primate as 
the modern UI for CloudStack [1] [2]. Thank you all.

I'm starting this vote (to):

  *   Accept Primate codebase [3] as a project under Apache CloudStack project
  *   Create and host a new repository (cloudstack-primate) and follow Github 
based development workflow (issues, pull requests etc) as we do with CloudStack
  *   Given this is a new project, to encourage cadence until its feature 
completeness the merge criteria is proposed as:
 *   Manual testing against each PR and/or with screenshots from the author 
or testing contributor, integration with Travis is possible once we get JS/UI 
tests
 *   At least 1 LGTM from any of the active contributors, we'll move this 
to 2 LGTMs when the codebase reaches feature parity wrt the existing/old 
CloudStack UI
 *   Squash and merge PRs
  *   Accept the proposed timeline [1][2] (subject to achievement of goals wrt 
Primate technical release and GA)
 *   the first technical preview targetted with the winter 2019 LTS release 
(~Q1 2020) and release to serve a deprecation notice wrt the older UI
 *   define a release approach before winter LTS
 *   stop taking feature FRs for old/existing UI after winter 2019 LTS 
release, work on upgrade path/documentation from old UI to Primate
 *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019), but 
still ship old UI with a final deprecation notice
 *   old UI codebase removed from codebase in winter 2020 LTS release

The vote will be up for the next two weeks to give enough time for PMC and the 
community to gather consensus and still have room for questions, feedback and 
discussions. The results to be shared on/after 21th October 2019.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

[1] Primate Proposal:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI

[2] Email thread reference:
https://markmail.org/message/z6fuvw4regig7aqb

[3] Primate repo current location: https://github.com/shapeblue/primate


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue