OK - that doesn't look too hard. Thanks for the information. Also, I'm an outlander and need to get accustomed to new customs.
Bruce B. On Fri, Sep 3, 2010 at 11:39 AM, David M Woollard <wooll...@jpl.nasa.gov>wrote: > Bruce, > > There are a number of formats for documentation that are easily integrated > into our existing user's guides, website, etc. As mentioned in the comment, > one of these formats is xDoc. You can check out this reference [1]. > Otherwise, since it is on the mailing list and has an issue, we will try to > move on it soon. > > Though I think Chris thanked you on the mailing list, I'll do it as well. > Thanks for the contribution! > > -Dave > > > [1] http://maven.apache.org/doxia/references/xdoc-format.html > > --------------------------------------------------------- > David M. Woollard, Software Engineer > Data Management Systems and Technologies Group (388J) > NASA Jet Propulsion Laboratory, Pasadena, CA, 91109, USA > Office: 171-243D Phone: (818) 354-4291 > > "Anybody who wants to make a revolution shouldn't grab a gun. > Just go and start working to change the world by using science > and technology." -Stanford Ovshinsky > > > > > > On Sep 3, 2010, at 8:28 AM, Bruce Barkstrom wrote: > > > What, if anything do I need to do? > > > > On Thu, Sep 2, 2010 at 11:48 PM, Chris A. Mattmann (JIRA) > > <j...@apache.org>wrote: > > > >> > >> [ > >> > https://issues.apache.org/jira/browse/OODT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > >> > >> Chris A. Mattmann updated OODT-28: > >> ---------------------------------- > >> > >> Fix Version/s: 0.2-incubating > >> > >>> OODT use case descriptions > >>> -------------------------- > >>> > >>> Key: OODT-28 > >>> URL: https://issues.apache.org/jira/browse/OODT-28 > >>> Project: OODT > >>> Issue Type: New Feature > >>> Components: website > >>> Reporter: Chris A. Mattmann > >>> Fix For: 0.2-incubating > >>> > >>> > >>> Bruce Barkstrom sent a message to the OODT email list [1] including a > use > >> case that he came up with from OODT. We should figure out a way: > >>> 1. to include this use case on the site (convert the ODT file into > >> something like Maven XDOC?) > >>> 2. include the ODT as a site ersource and link to it > >>> Or anything else that folks can think of. We'll track the issue here. > >>> [1] http://s.apache.org/9f4 > >> > >> -- > >> This message is automatically generated by JIRA. > >> - > >> You can reply to this email to add a comment to the issue online. > >> > >> > >
