oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: A Use Case for Helping Users "Qualify" Their Environment for OODT
Date Wed, 25 Aug 2010 16:37:25 GMT
Big +1 from me too on this one. Also I didn't see the PDF either. But, I was able to open the
use case ODT file in TextEdit on Mac OS X 10.5.6 and the use case looks good to me. Based
on feedback from others, we could put together a quick patch to the documentation on the website
that incorporates the use case into the site docs. I've filed a JIRA issue [1] to track this.

Welcome, Bruce!

Cheers,
Chris

[1] https://issues.apache.org/jira/browse/OODT-28

On 8/25/10 9:30 AM, "Justin Erenkrantz" <justin@erenkrantz.com> wrote:

On Wed, Aug 25, 2010 at 8:39 AM, Bruce Barkstrom <brbarkstrom@gmail.com> wrote:
> I've included two versions of the use case:
> 1.  A PDF version that could be placed in an
> appropriate place for public visibility.
> 2.  An Open Office version that could be modified
> by developers and contributors.  Open Office doesn't
> cost anything, so it is available to anyone that
> wanted to download it (as opposed to MS Office
> products, say).

Welcome!

Note that I don't see the PDF actually attached and I don't have
OpenOffice, but I'd definitely be +1 to making such docs available.
This would be a very very good thing to have!  -- justin



++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: Chris.Mattmann@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message