Re: OODT Website Changes (Redux)

2016-04-05 Thread Lewis John Mcgibbney
Rendering beautifully on mobile. This is neat as. On Tuesday, April 5, 2016, Mattmann, Chris A (3980) < chris.a.mattm...@jpl.nasa.gov> wrote: > LOVE the style and of course GH pages and the work there > is superior to the CMS. > > Let’s explore this..great start. > > +

Re: OODT Website Changes (Redux)

2016-04-05 Thread Mattmann, Chris A (3980)
LOVE the style and of course GH pages and the work there is superior to the CMS. Let’s explore this..great start. ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion

Re: OODT Website Changes (Redux)

2016-04-05 Thread Tom Barber
Okay, spent an hour hacking around ideas tonight, just to get a feel for things. http://buggtb.github.io/oodt-website/ I've only messed around with a frontpage and basic blog listing. You can see what i'm trying to do in breaking it up a bunch, I still want to do make the text easier to digest, i

Re: OODT Website Changes (Redux)

2016-04-05 Thread Mattmann, Chris A (3980)
Understood, OK Tom. ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@n

Re: OODT Website Changes (Redux)

2016-04-05 Thread Tom Barber
Yeah, I'm not suggesting we switch any time soon. My viewpoint is thus: we can do a better job with content, look and feel and the maintenance side. Personally, I find the CMS hard to use, maybe its just me, who knows. So, my suggestion is purely do some POC work to come up with what may, or may

Re: OODT Website Changes (Redux)

2016-04-05 Thread Chris Mattmann
Tom, my comment here is that we tried to do the exact same thing in Summer 2014 on XDATA. Just note that “dummy site” is now what we have in our operational site for Apache OODT. I think we have just only recently come to a point where it’s more stable (we don’t have people like Sebb coming exter

Re: OODT Website Changes (Redux)

2016-04-05 Thread Lewis John Mcgibbney
Steam ahead captain On Tuesday, April 5, 2016, Tom Barber wrote: > Okay here's what I propose. Apache CMS will be retired, not any time soon, > but at some point in the medium term future. ASF Infra offer > gitsubpub/svnsubpub as the standard for website publishing and we(I?) want > something mo

Re: OODT Website Changes (Redux)

2016-04-05 Thread Tom Barber
Okay here's what I propose. Apache CMS will be retired, not any time soon, but at some point in the medium term future. ASF Infra offer gitsubpub/svnsubpub as the standard for website publishing and we(I?) want something more useable for non webdevs. Thats not necessarily code free, but certainly a

[GitHub] oodt pull request: OODT-926 Sync pom.xml versioning

2016-04-05 Thread buggtb
Github user buggtb commented on the pull request: https://github.com/apache/oodt/pull/37#issuecomment-205715756 Commit away! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabl

Re: Transition from OODT 0.6 to 0.12 cannot find extractor specifications

2016-04-05 Thread Lewis John Mcgibbney
Hi K, OK so I did a bit of searching here and located a bunch of files which are defined as legacy... you can check the search results out below https://github.com/apache/oodt/search?utf8=%E2%9C%93&q=AutoDetectProductCrawler&type=Code I would urge you to have a look at the AutoDetectProductCrawler

[GitHub] oodt pull request: OODT-925 Update schema.xml field definitions fo...

2016-04-05 Thread lewismc
Github user lewismc commented on the pull request: https://github.com/apache/oodt/pull/36#issuecomment-205691424 Any objections to commit? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] oodt pull request: OODT-926 Sync pom.xml versioning

2016-04-05 Thread lewismc
Github user lewismc commented on the pull request: https://github.com/apache/oodt/pull/37#issuecomment-205691368 Any objections to commit? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this