Mailing-List: contact bigtop-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bigtop-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of email4yliu@gmail.com
 designates 209.85.210.53 as permitted sender)
User-Agent: Microsoft-MacOutlook/14.2.1.120420
Date: Wed, 02 May 2012 12:18:17 -0700
Subject: Re: Guarding against the use of upstream scripts
From: "David Liu (gmail dev)" <email4yliu@gmail.com>
To: <bigtop-dev@incubator.apache.org>
Message-ID: <CBC6D540.90330%email4yliu@gmail.com>
Thread-Topic: Guarding against the use of upstream scripts
In-Reply-To: 
 <CA+ULb+te8V3PTjVCK6G4eAF9A01J-iHBjUV_JPj6vhjhnXdyow@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Thanks Roman. Sure, I will create a ticket, and work toward a proposal for
discussion. 

David

On 5/2/12 12:08 PM, "Roman Shaposhnik" <rvs@apache.org> wrote:

>On Wed, May 2, 2012 at 10:58 AM, David Liu (gmail dev)
><email4yliu@gmail.com> wrote:
>> Along the same line, I wonder if bigtop community has considered to
>>have a
>> shell that allows single point of entry to any of the upstream systems.
>> Something like mvn or git command. This will introduce something to
>>learn
>> at first but it adds value to start/stop/access help for all systems in
>>a
>> consistent way. It can also shield some changes that happens with
>>upstream
>> systems. Instead of dealing with some many <XXX>_HOME, we could have one
>> BIGTOP_HOME. It's quite nice to be able to say:
>> bigtop -help
>> bigtop -start <xxx|all>
>
>I like the idea very much (darn! how come I didn't think of it ;-)).
>Would you care
>to work on a proposal?
>
>This would be a perfect thing to discuss at our upcoming Bigtop hackathon.
>
>Thanks,
>Roman.