+1

On Tue, Oct 8, 2019 at 3:35 PM Giles Sirett <giles.sir...@shapeblue.com>
wrote:

> +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 <awb...@qx.net>
> Sent: 08 October 2019 13:28
> To: users@cloudstack.apache.org; d...@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 <sah...@cloudops.com> wrote:
> >
> >> +1 binding
> >>
> >> On Tue., Oct. 8, 2019, 4:14 p.m. Will Stevens,
> >> <wstev...@cloudops.com>
> >> wrote:
> >>
> >>> +1 (binding)
> >>>
> >>> On Mon, Oct 7, 2019, 7:31 AM Rohit Yadav <rohit.ya...@shapeblue.com>
> >>> 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
> >>>>
> >>>>
> >>>>
> >>>>
>
>

Reply via email to