Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Received-SPF: pass (athena.apache.org: domain of screeley@redhat.com
 designates 209.132.183.25 as permitted sender)
Date: Tue, 27 May 2014 10:45:32 -0400 (EDT)
From: Scott Creeley <screeley@redhat.com>
To: dev@ambari.apache.org
Message-ID: <2100482424.7434184.1401201932830.JavaMail.zimbra@redhat.com>
In-Reply-To: <1750585841.8929635.1400859660030.JavaMail.zimbra@redhat.com>
References: 
 <CAGjSOKWEC44J-PsWg4Jo2WL71A-UXsax+BmyNdoa-+r0EY-bCQ@mail.gmail.com>
 <CAOWF125-BxjZhq2PeThMRi3TT65QR5xqRf+2MxwVF6Xma-iz2A@mail.gmail.com>
 <CACDnAubxgSyfh70iWU+Ka655jT8KM9yoGjpTfYVxc9afxX1uMg@mail.gmail.com>
 <CAGjSOKW-Aab55C0=4Rt3Guuw=odBaAzo+CeVQz6JcDq5EXkvUA@mail.gmail.com>
 <CABCXrRTdMhcmLFJ=R_oZq3eq0ECGYnaD0M2huO2Sp=dVWTPT0w@mail.gmail.com>
 <1750585841.8929635.1400859660030.JavaMail.zimbra@redhat.com>
Subject: Re: Restructuring ambari-client directory structure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Thread-Topic: Restructuring ambari-client directory structure
Thread-Index: ycz14QbUp3VpQaQtYqcSWKI1GAGM+63iGCQE

+1

----- Original Message -----
From: "Erin Boyd" <eboyd@redhat.com>
To: dev@ambari.apache.org
Sent: Friday, May 23, 2014 11:41:00 AM
Subject: Re: Restructuring ambari-client directory structure

+1;

----- Original Message -----
From: "Sumit Mohanty" <smohanty@hortonworks.com>
To: dev@ambari.apache.org
Sent: Thursday, May 22, 2014 5:44:04 PM
Subject: Re: Restructuring ambari-client directory structure

+1


On Thu, May 22, 2014 at 3:03 PM, Yusaku Sako <yusaku@hortonworks.com> wrote:

> Sid, I thought about that also.
> I personally like the explicit names python-client, groovy-client
> better vs just python, groovy, because it suggests whoever is looking
> at the code that these are standalone client modules by themselves,
> rather than subcomponents that make up the client.
>
> Yusaku
>
> On Thu, May 22, 2014 at 2:42 PM, Siddharth Wagle <swagle@hortonworks.com>
> wrote:
> > ambari-client/python
> > ambari-client/groovy
> >
> > +1
> >
> >
> > On Thu, May 22, 2014 at 2:29 PM, Jeff Sposetti <jeff@hortonworks.com>
> wrote:
> >
> >> +1
> >>
> >>
> >> On Thu, May 22, 2014 at 5:26 PM, Yusaku Sako <yusaku@hortonworks.com>
> >> wrote:
> >>
> >> > Hi Ambari devs,
> >> >
> >> > There's new development [1] on Ambari Groovy client and Ambari Shell
> >> > that utilizes that client.
> >> > Our current project directory structure is:
> >> >
> >> > ambari-client/<python-client>
> >> >
> >> > In [1], the proposal is to restructure it as follows:
> >> >
> >> > ambari-client/python-client
> >> > ambari-client/groovy-client
> >> >
> >> > I think this is a good approach, as there could be other clients in
> >> > the future as well.
> >> > What do you all think?
> >> >
> >> > [1] https://issues.apache.org/jira/browse/AMBARI-5482
> >> >
> >> > Yusaku
> >> >
> >> > --
> >> > CONFIDENTIALITY NOTICE
> >> > NOTICE: This message is intended for the use of the individual or
> entity
> >> to
> >> > which it is addressed and may contain information that is
> confidential,
> >> > privileged and exempt from disclosure under applicable law. If the
> reader
> >> > of this message is not the intended recipient, you are hereby notified
> >> that
> >> > any printing, copying, dissemination, distribution, disclosure or
> >> > forwarding of this communication is strictly prohibited. If you have
> >> > received this communication in error, please contact the sender
> >> immediately
> >> > and delete it from your system. Thank You.
> >> >
> >>
> >> --
> >> CONFIDENTIALITY NOTICE
> >> NOTICE: This message is intended for the use of the individual or
> entity to
> >> which it is addressed and may contain information that is confidential,
> >> privileged and exempt from disclosure under applicable law. If the
> reader
> >> of this message is not the intended recipient, you are hereby notified
> that
> >> any printing, copying, dissemination, distribution, disclosure or
> >> forwarding of this communication is strictly prohibited. If you have
> >> received this communication in error, please contact the sender
> immediately
> >> and delete it from your system. Thank You.
> >>
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.