Re: Prototype Apache OODT website
Just so long as chemistry is “baked in” and it “lands” in the trunk, I’m happy! NICE! Cheers, Chris On 7/28/10 4:04 AM, Sean Kelly ke...@apache.org wrote: OK if no one else objects I'll go ahead and move forward with this. Thanks! P.S. Minor thing, but why Ob and Or instead of O and O on the OO blocks that are part of OODT? Chemistry. Heh. The advertising idea: I want it to look like chemical elements from a periodic table to emphasize OODT's science lineage. But O and O with two different atomic weights is illogical, and Ob Or look more like chemical elements. E.g.: Ob₁₂Or₁₆D₃T₂₀ = Apache OODT = something to get you totally baked Anyone got a better concept banner image? I'm not wedded to this concept. --k PS: Don Draper makes it look so easy on Mad Men. ^_^ ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
Re: Prototype Apache OODT website
+1, this graphic rox! On 7/28/10 6:03 AM, Sean Kelly ke...@apache.org wrote: First off, this site is BADA$$! I read through it and I am going to try to carve off a little time to augment the CAS page with some more detailed descriptions of those components and maybe some organization. Thanks and that would be great! Truly, the script to generate the site was the easy part-it's all the content that's hard! The CAS page is in https://svn.apache.org/repos/asf/incubator/oodt/docs/site/components/cas. Add graphics if you can. Graphics are sexy. Regarding the logo, I, for one, really like the elements idea. I think the only confusing part is that it does not quite read oodt if you are like me and never pay 100% attention to anything ;). What if you tried to fade that second letter out a little more or make it smaller, or both (or left it alone and told me to shut up)? Just some thoughts... I likey. See attached for a sample. Feelings? [cid:3363146092_92242645] ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
Prototype Apache OODT website
OODT'ers: As part of progress on OODT-16, I've got a prototype of the Apache OODT website up and running at http://216.146.47.22/oodt/ This site is generated from the Maven site artifacts of the oodt tree as of r965292 (back when mvn site worked for every module except catalog), combined with static HTML artifacts. Outstanding issues you'll encounter: - Broken links - Misshapen Maven reports - Broken Facebook URL - Missing apidocs link - Lack of Twitter account - Need handling of news items - Add search box - Make HEAD of the oodt tree work again - More! I welcome everyone's help, of course, ~_^ The static HTML artifacts are in svn at https://svn.apache.org/repos/asf/incubator/oodt/docs/site To re-generate the Maven artifacts, just run mvn site at the top level oodt tree—assuming we can get that working. (I had to svn up -r965292.) Then you can generate the site docs by using the oodtsite.publisher script. The script is checked in: https://svn.apache.org/repos/asf/incubator/oodt/tools/oodtsite.publisher Of course, all this is open to change. Maybe static HTML artifacts aren't the right way to go. Maybe Maven reports aren't all that useful. Maybe we should use a content management system or just grab a Confluence space. Maybe blue black aren't the right feel for OODT. Maybe the look is too professional, not hokey open sourcy enough. Hey, I'm flexible. We're all in this together! O-O-D-T! O-O-D-T!
