[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot commented on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538886094
 
 
   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] PaulAngus commented on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
PaulAngus commented on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538886062
 
 
   requesting docbuild
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot commented on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538886588
 
 
   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/pr71
   
   Build Log Output:
   
   
   No log errors found to report.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


RE: [DISCUSS] Short "marketing" video project

2019-10-07 Thread Giles Sirett
Good catch David
I'll ping Karen and see if shes still got the details and report back here


Kind regards
Giles

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


-Original Message-
From: David Nalley  
Sent: 04 October 2019 18:02
To: dev@cloudstack.apache.org
Cc: Apache CloudStack Marketing ; users 

Subject: Re: [DISCUSS] Short "marketing" video project

Like this one?
https://www.youtube.com/user/cloudstack/about

I think Karen had creds to this.

On Fri, Oct 4, 2019 at 11:04 AM Will Stevens  wrote:
>
> I am +1 to an ACS youtube channel.
>
> *Will Stevens*
> Chief Technology Officer
> c 514.826.0190
>
> 
>
>
> On Fri, Oct 4, 2019 at 9:46 AM Giles Sirett 
> 
> wrote:
>
> > I love the video Andrija
> >
> > Very good point Julia - we also have a whole of catalogue community 
> > video content hosted in the Shapeblue channel - simply because there 
> > was nowhere else to put it For CCC the last  2 years,  we've worked 
> > with Rich Bowen to get conference talks into the Apache channel, but 
> > that’s only really fits  because CCC has been part of Apachecon 
> > (i.e. it wouldn’t work for "how to" videos) ,etc
> >
> > If we have people who are creating video content for the project 
> > such as this , it would probably make sense to create an ACS youtube 
> > channel.
> >
> > Any objections ?
> >
> > From a practicality side, access to this would need to work in a 
> > similar way to the ACS twitter account: the account owner is a PMC 
> > email address, allowing password resets from the PMC as a group. The 
> > actual login credentials  then held by a small subset of people who 
> > actually publish.
> >
> > This is a bigger decsison than Andrijas one specific  video IMO and 
> > should have its own discuss thread , but keen to see initial 
> > thoughts here first
> >
> >
> >
> >
> >
> > Kind regards
> > Giles
> >
> > giles.sir...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Andrija Panic 
> > Sent: 03 October 2019 18:58
> > To: Apache CloudStack Marketing 
> > Cc: users ; dev 
> > Subject: Re: [DISCUSS] Short "marketing" video project
> >
> > I believe I saw that video - very nice work Julia.
> >
> > I believe, by (very) lazy consensus (a.k.a. if no objections), that I will
> > add that video to the main web site.
> >
> > Cheers
> > Andrija
> >
> >
> > On Thu, 3 Oct 2019 at 14:56, Julia Simon  wrote:
> >
> > > Hi,
> > >
> > > We ran in to this issue a few years ago when we hosted the CloudStack
> > > Collab. Videos from that are on our (CloudOps) youtube channel, since
> > > there wasn't another place to publish them.
> > > Julia
> > >
> > > On Tue, Oct 1, 2019 at 10:21 AM Andrija Panic
> > > 
> > > wrote:
> > >
> > >> Hi guys,
> > >>
> > >> this is a little project I've been experimenting last 2 weeks and is
> > >> **temporarily** located on the ShapeBlue channel.
> > >>
> > >> https://youtu.be/k3uD69fajCU
> > >>
> > >> Do you have any ideas where we can publish this, in more "official",
> > >> CloudStack way?
> > >>
> > >> I was thinking about putting this on the main website
> > >> http://cloudstack.apache.org
> > >>
> > >> Comments, objections, ideas?
> > >>
> > >> Best,
> > >> Andrija
> > >>
> > >>
> > >
> > > --
> > >
> > > *Julia Simon*Responsable principale du marketing *| *Senior Marketing
> > > Manager t 514.447.3456 ext. 1103 c 514.993.6661
> > >
> > > 
> > >
> > >
> > >
> >
> >
> > --
> >
> > Andrija Panić
> >


[GitHub] [cloudstack-documentation] ACSGitBot removed a comment on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot removed a comment on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538140108
 
 
   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot removed a comment on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot removed a comment on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538140506
 
 
   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/pr71
   
   Build Log Output:
   
   
   No log errors found to report.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] PaulAngus removed a comment on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
PaulAngus removed a comment on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538922332
 
 
   requesting docbuild


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot removed a comment on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot removed a comment on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538922367
 
 
   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot commented on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538922367
 
 
   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] PaulAngus commented on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
PaulAngus commented on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538922332
 
 
   requesting docbuild


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] PaulAngus removed a comment on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
PaulAngus removed a comment on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538886062
 
 
   requesting docbuild
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot removed a comment on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot removed a comment on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538886094
 
 
   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot commented on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538922442
 
 
   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot commented on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538922505
 
 
   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot commented on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538922951
 
 
   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/pr71
   
   Build Log Output:
   
   
   No log errors found to report.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot commented on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538923491
 
 
   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/pr71
   
   Build Log Output:
   
   
   No log errors found to report.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[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
  
 



Re: Further cleaning up NuageVsp plugin code

2019-10-07 Thread Rohit Yadav
Hi Kris,

Thanks for sending the PRs. Unless any of us are working on a next minor 
release of 4.11 and 4.12, the PRs towards 4.11 and 4.12 are not necessary, also 
because in minor releases I think we've preferred to avoid any major changes 
including addition or removal of features.

The PR towards 4.13 can be used towards master as we can forward merge that to 
master and therefore #3619 may be closed.
I'll help wrt review and testing of #3620.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Kris Sterckx 
Sent: Sunday, October 6, 2019 18:41
To: dev@cloudstack.apache.org 
Subject: Further cleaning up NuageVsp plugin code

Hi all,


Please take a look at following PR's

https://github.com/apache/cloudstack/pull/3619  (master)
https://github.com/apache/cloudstack/pull/3620  (4.13)
https://github.com/apache/cloudstack/pull/3621  (4.12)
https://github.com/apache/cloudstack/pull/3622  (4.11)

They proceed with cleanup of NuageVsp plugin (cfr [1]) to the relevant
per-release master branches (+ on 4.13 and master have some additional
minor cleanups).

I would like these to get merged as i am concerned with the
cs.mv.nuagenetworks.net maven repo, referred to from the Nuage plugin code,
being no longer maintained and i don't want to break any build going
forward.

Your collaboration to get this merged is appreciated.

thanks

Kris

[1] https://github.com/apache/cloudstack/pull/3146

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



Re: Further cleaning up NuageVsp plugin code

2019-10-07 Thread Kris Sterckx
Thanks Rohit

Thanks for moving ahead #3620.
I closed #3619 now.

The reason why i would like #3621 and #3622 to see go ahead as well is
because the Nuage CS maven repo is publicly hosted and not maintained and
for that we decide it to cease to exist. I would like to shut it down by
end of the year.

To your concern, what I can do instead on 4.11 and 4.12 branch is removing
Nuage from the main pom files (the root pom file + the client pom file),
without touching any code at all.  Whenever then a bigger change is planned
anyway, the current PR's can still be considered (by which you will get the
clean cut). The 4.12 was an easy port but the 4.11 one was not
straight-forward.

Let me know what you think.

Cheers,

Kris

On Mon, 7 Oct 2019 at 13:39, Rohit Yadav  wrote:

> Hi Kris,
>
> Thanks for sending the PRs. Unless any of us are working on a next minor
> release of 4.11 and 4.12, the PRs towards 4.11 and 4.12 are not necessary,
> also because in minor releases I think we've preferred to avoid any major
> changes including addition or removal of features.
>
> The PR towards 4.13 can be used towards master as we can forward merge
> that to master and therefore #3619 may be closed.
> I'll help wrt review and testing of #3620.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Kris Sterckx 
> Sent: Sunday, October 6, 2019 18:41
> To: dev@cloudstack.apache.org 
> Subject: Further cleaning up NuageVsp plugin code
>
> Hi all,
>
>
> Please take a look at following PR's
>
> https://github.com/apache/cloudstack/pull/3619  (master)
> https://github.com/apache/cloudstack/pull/3620  (4.13)
> https://github.com/apache/cloudstack/pull/3621  (4.12)
> https://github.com/apache/cloudstack/pull/3622  (4.11)
>
> They proceed with cleanup of NuageVsp plugin (cfr [1]) to the relevant
> per-release master branches (+ on 4.13 and master have some additional
> minor cleanups).
>
> I would like these to get merged as i am concerned with the
> cs.mv.nuagenetworks.net maven repo, referred to from the Nuage plugin
> code,
> being no longer maintained and i don't want to break any build going
> forward.
>
> Your collaboration to get this merged is appreciated.
>
> thanks
>
> Kris
>
> [1] https://github.com/apache/cloudstack/pull/3146
>
> 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 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
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue





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
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue





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
> 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
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

--

Andrija Panić


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
>> Amadeus House, Floral Street, London  WC2E 9DPUK
>> @shapeblue
>>
>>
>>
>>
>
> --
>
> Andrija Panić



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
> 
> 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 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, ShapeBlu

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 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 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
> 
> 
> 



[GitHub] [cloudstack-documentation] ACSGitBot removed a comment on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot removed a comment on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538922442
 
 
   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] PaulAngus commented on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
PaulAngus commented on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-539205353
 
 
   request docbuild
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot removed a comment on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot removed a comment on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538922951
 
 
   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/pr71
   
   Build Log Output:
   
   
   No log errors found to report.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot removed a comment on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot removed a comment on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538922505
 
 
   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot removed a comment on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot removed a comment on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-538886588
 
 
   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/pr71
   
   Build Log Output:
   
   
   No log errors found to report.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot commented on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-539205393
 
 
   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #71: Add warning about customisations when upgrading

2019-10-07 Thread GitBox
ACSGitBot commented on issue #71: Add warning about customisations when 
upgrading
URL: 
https://github.com/apache/cloudstack-documentation/pull/71#issuecomment-539205982
 
 
   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/pr71
   
   Build Log Output:
   
   
   No log errors found to report.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services