Re: OODT's Git mirror at Github is borked

Hi Jake, With regards to switching to git as the primary repo, how does that work with the Github mirror? Can Github actually be used then for merging pull requests, etc., or is it still just a static mirror that the project has minimal control over? -- Joyce On Wed, Jan 29, 2014 at 9:36 PM,

Re: OODT's Git mirror at Github is borked

Hey Chris The official source repository for OODT is currently in svn, and Github is just a mirror of that svn repository. When a pull request is issued against one of our mirrors on Github it can email the configured mailing list for that mirror that a pull request is available, but it can not be

Re: OODT's Git mirror at Github is borked

Hey Jake, Thanks. I know what the official source repository is for OODT, and that SVN is the canonical bits, and that the mirror at Github is simply a mirror. I also know that merges aren't automatic and that they can't automatically be integrated. My question is can you configure the pull reque

Re: OODT's Git mirror at Github is borked

Hey Chris I have switched the default branch on the Github mirror for OODT to be trunk and closed out the two open pull requests that you had issued. Can you please submit the patches you have to OODT and not issue pull requests against the mirror as no one from OODT will be able to accept/merge th

Re: OODT's Git mirror at Github is borked

Thanks Jake. I guess I was under the (potentially) wrong impression that we could do pull requests against our Github mirrors for ASF projects and they would show up as emails on our dev@oodt.apache.org mailing lists with emails back to the patch that the pull request represented. I've seen this in

Re: ApacheCon 2014

Tom, OODT as a business application is a novel use case for sure. Perhaps to help, if you took some of the architecture diagrams and tried to relabel the pieces with Business jargon instead of NASA/Science jargon it might help. Just this week several of the JPL folks were at Caltech meeting with

OODT's Git mirror at Github is borked

Hey Guys, I just tried to do some Github.com/apache/oodt work and submitted a pull request and saw that the default branch at Github for OODT is the 0.1-incubating branch which in turn seems to have borked my pull request (thinks it's over 800+ changes). Any ideas? Thanks! Cheers, Chris

Re: ApacheCon 2014

Chris, smells like another talk. Please submit :) Seriously, you have it written below :) Submit! :) Chris Mattmann chris.mattm...@gmail.com -Original Message- From: Christopher Warner Reply-To: Date: Wednesday, January 29, 2014 8:45 AM To: Subject: Re: Apac

Re: ApacheCon 2014

Tom this sounds fantastic and yes please submit! Chris Mattmann chris.mattm...@gmail.com -Original Message- From: Tom Barber Reply-To: Date: Monday, January 27, 2014 11:08 AM To: Subject: Re: ApacheCon 2014 >So I saw the call go out that they were short of

Re: borked links

Juha, The URL will get updated soon. In the meantime the proper URL is: http://www.apache.org/dyn/closer.cgi/oodt/apache-oodt-0.6-src.zip Thanks for reporting this. -Cameron On Wed, Jan 29, 2014 at 3:19 PM, Juha Vierinen wrote: > Downloads -> 0.6 Release > > http://www.apache.org/dyn/closer

borked links

Downloads -> 0.6 Release http://www.apache.org/dyn/closer.cgi/oodt/apache-oodt-0.6.zip juha

Build failed in Jenkins: oodt-trunk » CAS Protocol FTP Implementation #1226

See -- [INFO] [INFO] Building CAS Protocol FTP Implementation [INFO]task-segment: [install] [INFO]

Build failed in Jenkins: oodt-trunk #1226

See -- [...truncated 5451 lines...] [INFO] [surefire:test {execution: default-test}] [INFO] Surefire report directory: -

Re: ApacheCon 2014

Hi Guys, Nice for some people to chime up 2 days before the deadline! ;) Christopher, its some very interesting points you raise, and partly where I struggle I think. Coming from an Business Intelligence ETL world where you suck data from data source and pump it into target b on a scheduled

Re: ApacheCon 2014

One of the more difficult things for me trying to sell OODT was espousing why it's useful for structured processes whether they be government initiated protocols for data handling or workflow handling of that data. In some cases I'm dealing with large data sets that exist in things like excel, word

Re: ApacheCon 2014

> My issue with Apache OODT is the fact currently a load of science bods use it > (no offence ;) ) and the stuff you see written about and presented whilst a) > is cool as hell b) lacks day to day "real world" applications for non > scientists because if people do use it for non science applicat