[kepler-dev] Build Script Suggestion

[Laura L. Downey]

>From a usability perspective, anything that makes it easier for users to get
up and running is a good idea.  In the commercial world, when products are
hard to install and configure, oftentimes users just give up and don't
install or the product sits on the shelf and is never used because they
couldn't get it configured properly.  In either case the really good
features of a hard-to-install or hard-to-configure product are not
appreciated and/or improved upon.

As we go forward with getting more and more scientists to adopt Kepler as a
premier scientific workflow system, I think it is critical that Kepler is
easy to download, install and configure.

Laura L. Downey
Senior Usability Engineer
LTER Network Office
Department of Biology, MSC03 2020
1 University of New Mexico
Albuquerque, NM  87131-0001
505.277.3157 phone
505.277-2541 fax
ldowney at lternet.edu
 
-----Original Message-----
From: kepler-dev-bounces at ecoinformatics.org
[mailto:kepler-dev-bounces at ecoinformatics.org] On Behalf Of Nandita Mangal
Sent: Thursday, June 09, 2005 6:27 PM
To: kepler-dev at ecoinformatics.org
Subject: [kepler-dev] Build Script Suggestion

Hi there,

It is being suggested that for ease of first time Kepler Users
installing kepler, there be a build script which would automatically
checkout Kepler for them, instead of users manually trying to checkout
kepler after installing Ptolemy.

This suggestion was made after the following post on confusion
/assumption of Kepler being checked out automatically. The post posted
by a beginning user can be found at :-

http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/kepler-dev/2005-June/
001955.html

Kindly post your suggestions whether to have the above build script. 

thank you,

Nandita Mangal.
_______________________________________________
Kepler-dev mailing list
Kepler-dev at ecoinformatics.org
http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev