Re: Writing for Opensource.com

[Michael Joyce]

+1 sir, I'm on it!


-- Jimmy

On Thu, Oct 22, 2015 at 7:24 AM, Tom Barber <tom.bar...@meteorite.bi> wrote:

> Michael Joyce, if you didn't get a copy this one is for you.
>
> Thanks again for stepping up!
>
>
> Tom
> -- Forwarded message --
> From: Rikki Endsley <rends...@redhat.com>
> Date: Thu, Oct 22, 2015 at 3:21 PM
> Subject: Writing for Opensource.com
> To: ri...@opensource.com
> Cc: open <o...@opensource.com>
>
>
> Hello,
>
> Rich Bowen forwarded me your contact information and said that you're
> interested in writing about Apache projects for Opensource.com.
>
> Here's information about joining our online community:
> http://opensource.com/participate
>
> And here's where you can submit an article proposal:
> http://opensource.com/story
>
> You are also welcome to submit your story idea directly to me and our
> editorial team by emailing o...@opensource.com.
> Please include a brief outline along with your story proposal so that we
> have an idea of what you plan to include in your article and your intended
> audience.
> One of our editors will respond within 5-7 business days (usually sooner!).
>
> Let me know if you have questions.
> I look forward to seeing your ideas!
> Best regards,
> Rikki
>
> 
>
> Rikki Endsley
>
> Community Manager, Opensource.com
> Twitter: @opensourceway | @rikkiends
>
> Discover an open source world -- http://opensource.com
> IRC: Freenode #opensource.com
> * Editorial calendar: http://opensource.com/resources/editorial-calendar
> * How to submit a story: http://opensource.com/how-submit-article
>

Re: OpenSource.com looking for content

[Michael Joyce]

Hey folks,

I work on one of the NASA/JPL projects that uses OODT and would be happy to
get a write up over to the opensource folks. I see what I can crank out in
the next day or two and let the list know.


-- Jimmy

On Tue, Oct 20, 2015 at 12:45 PM, Tom Barber 
wrote:

> Hey Rich,
>
> My last mail must have got drowned out in the noise, just wondered if you
> still wanted content and if OODT could offer up something for
> opensource.com
> ?
>
> Thanks
>
> Tom
>
> On Thu, Sep 17, 2015 at 11:27 PM, Tom Barber 
> wrote:
>
> > Hi Rich
> >
> > I'm sure us folk over at Apache OODT would be able to come up with some
> > content considering all the cool NASA and Darpa stuff it's used in.
> >
> > Regards
> >
> > Tom
> > On 17 Sep 2015 19:50, "Rich Bowen"  wrote:
> >
> > > Several months ago I mentioned that OpenSource.com is looking for
> content
> > > for a monthly series on the ASF's projects. With 166 TLPs, it seems
> that
> > > we'd be able to produce content for at least ten years of articles.
> > >
> > > Please let me know if you're interested in running an article on your
> > > project, and I'll get you on the list. You can, if you like, write the
> > > article yourself, or, if you prefer, I'd be willing to do a
> > > feathercast-style interview with you (see
> http://feathercast.apache.org/
> > > if you're not familiar with Feathercast) about your project, something
> > > exciting in your community, or some interesting use that your project
> has
> > > been put to.
> > >
> > > Thanks!
> > >
> > > --
> > > Rich Bowen - rbo...@rcbowen.com - @rbowen
> > > http://apachecon.com/ - @apachecon
> > >
> >
>

Re: New Committer: Radu Manole

[Michael Joyce]

Welcome!!


-- Jimmy

On Sun, Oct 11, 2015 at 1:52 PM, Lewis John Mcgibbney <
lewis.mcgibb...@gmail.com> wrote:

> Nice
>
> On Sunday, October 11, 2015, Mattmann, Chris A (3980) <
> chris.a.mattm...@jpl.nasa.gov> wrote:
>
> > Also, your first task :-)
> >
> > Please add yourself to the OODT website committers list, and
> > to core/pom.xml :)
> >
> > ++
> > 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...@nasa.gov 
> > WWW:  http://sunset.usc.edu/~mattmann/
> > ++
> > Adjunct Associate Professor, Computer Science Department
> > University of Southern California, Los Angeles, CA 90089 USA
> > ++
> >
> >
> >
> >
> >
> > -Original Message-
> > From: Tom Barber >
> > Reply-To: "dev@oodt.apache.org "  > >
> > Date: Sunday, October 11, 2015 at 7:52 AM
> > To: "dev@oodt.apache.org "  > >
> > Subject: New Committer: Radu Manole
> >
> > >The Project Management Committee (PMC) for Apache OODT has asked Radu
> > >Manole to
> > >become a committer and we are pleased to announce that they have
> accepted.
> > >
> > >-- Tom
> >
> >
>
> --
> *Lewis*
>

Re: [DISCUSS] Moving to Git (was Re: Moving repository to git)

[Michael Joyce]

Sounds good to me. Also, yay git!


-- Jimmy

On Mon, Aug 24, 2015 at 10:57 PM, Chris Mattmann chris.mattm...@gmail.com
wrote:

 Hey Lewis,

 There seems to be widespread support so far. I’d say
 there’s no need for a VOTE and yes, file the issue, but
 please note that we’d like to move AFTER 0.10.

 That work for everyone?

 Cheers,
 Chris

 —
 Chris Mattmann
 chris.mattm...@gmail.com






 -Original Message-
 From: Lewis John Mcgibbney lewis.mcgibb...@gmail.com
 Reply-To: dev@oodt.apache.org
 Date: Monday, August 24, 2015 at 10:31 PM
 To: dev@oodt.apache.org dev@oodt.apache.org
 Subject: Re: [DISCUSS] Moving to Git (was Re: Moving repository to git)

 Hi Folks,
 Is anyone taking this on or can I log an issue with INFRA and address it?
 Thanks
 Lewis
 
 On Mon, Aug 24, 2015 at 12:13 PM, Radu Manole manole.v.r...@gmail.com
 wrote:
 
  Super!
 
  If you move to git as the main repository (when?), please don't forget
 to
  update the reviewboard configuration, too, to point to the git repo.
 This
  way, we might be able to actually RBTools to upload review updates
 directly
  from the git repository.
 
  2015-08-24 18:05 GMT+03:00 Michael Joyce jo...@apache.org:
 
   +1
  
  
   -- Jimmy
  
   On Fri, Aug 21, 2015 at 10:53 PM, Tom Barber tom.bar...@meteorite.bi
 
   wrote:
  
1000 times yes.
   
I asked Chris about this a few years ago and he told me svn was fine
  now
he's a git slut. I think that's the technical term.
   
Anyway for those of us who live with rubbish broadband or who like
committing often but out of the main repo it's a welcome change.
   
Tom
On 22 Aug 2015 1:55 am, Lewis John Mcgibbney 
   lewis.mcgibb...@gmail.com
wrote:
   
 Hi Valerie,
 Main rationale seems to be that most patches are comingr through
   Github.
 Therefore people seem to be pulling code from the github mirror at
   master
 branch as oppose to from SVN trunk.

 On Friday, August 21, 2015, Mallder, Valerie 
   valerie.mall...@jhuapl.edu

 wrote:

  I guess I can't really object. But, I don't really want to learn
  yet
  another CM system :(. Would be nice to know the rationale
 behind
  the
  change though. Why would this be considered an improvement? I
   haven't
 run
  into anything yet that would make me dislike svn.
 
 
 
  Sent from my iPhone.
  
  From: Mattmann, Chris A (3980) chris.a.mattm...@jpl.nasa.gov
  javascript:;
  Sent: Friday, August 21, 2015 3:50:01 PM
  To: dev@oodt.apache.org javascript:;
  Subject: [DISCUSS] Moving to Git (was Re: Moving repository to
 git)
 
  I would be fully supportive of this.
 
  What do others in the community think? If there are no
 objections
  over the next week I’d like to call a VOTE.
 
  Note, Radu, that this wouldn’t mean “moving to Github”. Github
 !=
  Git != Apache. Apache has writeable Git repos (that run on ASF
  hardware) and separately, Git mirrors that mirror and interact
 with
  Github from the Apache gold source. Everyone should check out:
  http://git.apache.org for more detail.
 
  Thoughts, please?
 
  Cheers,
  Chris
 
 
 ++
  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...@nasa.gov javascript:;
  WWW:  http://sunset.usc.edu/~mattmann/
 
 ++
  Adjunct Associate Professor, Computer Science Department
  University of Southern California, Los Angeles, CA 90089 USA
 
 ++
 
 
 
 
 
  -Original Message-
  From: Radu Manole manole.v.r...@gmail.com javascript:;
  Reply-To: dev@oodt.apache.org javascript:; 
  dev@oodt.apache.org
  javascript:;
  Date: Friday, August 21, 2015 at 11:51 AM
  To: oodt dev@oodt.apache.org javascript:;
  Subject: Moving repository to git
 
  Hello,
  
  Did you consider moving to git from svn as the main repository
 for
   the
  project?
  Especially since most of the pull requests are done from
 github,
  converting
  a diff to svn feels a bit unnecessary.
  
  It woul have made my life easier certainly. Especially if I
 didn't
have
 to
  convert from git to svn diffs in order to post reviews on
 review
board.
  
  Thanks,
  Radu.
 
 

 --
 *Lewis*

   
  
 
 
 
 
 --
 *Lewis*

Re: [DISCUSS] Moving to Git (was Re: Moving repository to git)

[Michael Joyce]

+1


-- Jimmy

On Fri, Aug 21, 2015 at 10:53 PM, Tom Barber tom.bar...@meteorite.bi
wrote:

 1000 times yes.

 I asked Chris about this a few years ago and he told me svn was fine now
 he's a git slut. I think that's the technical term.

 Anyway for those of us who live with rubbish broadband or who like
 committing often but out of the main repo it's a welcome change.

 Tom
 On 22 Aug 2015 1:55 am, Lewis John Mcgibbney lewis.mcgibb...@gmail.com
 wrote:

  Hi Valerie,
  Main rationale seems to be that most patches are comingr through Github.
  Therefore people seem to be pulling code from the github mirror at master
  branch as oppose to from SVN trunk.
 
  On Friday, August 21, 2015, Mallder, Valerie valerie.mall...@jhuapl.edu
 
  wrote:
 
   I guess I can't really object. But, I don't really want to learn yet
   another CM system :(. Would be nice to know the rationale behind the
   change though. Why would this be considered an improvement? I haven't
  run
   into anything yet that would make me dislike svn.
  
  
  
   Sent from my iPhone.
   
   From: Mattmann, Chris A (3980) chris.a.mattm...@jpl.nasa.gov
   javascript:;
   Sent: Friday, August 21, 2015 3:50:01 PM
   To: dev@oodt.apache.org javascript:;
   Subject: [DISCUSS] Moving to Git (was Re: Moving repository to git)
  
   I would be fully supportive of this.
  
   What do others in the community think? If there are no objections
   over the next week I’d like to call a VOTE.
  
   Note, Radu, that this wouldn’t mean “moving to Github”. Github !=
   Git != Apache. Apache has writeable Git repos (that run on ASF
   hardware) and separately, Git mirrors that mirror and interact with
   Github from the Apache gold source. Everyone should check out:
   http://git.apache.org for more detail.
  
   Thoughts, please?
  
   Cheers,
   Chris
  
   ++
   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...@nasa.gov javascript:;
   WWW:  http://sunset.usc.edu/~mattmann/
   ++
   Adjunct Associate Professor, Computer Science Department
   University of Southern California, Los Angeles, CA 90089 USA
   ++
  
  
  
  
  
   -Original Message-
   From: Radu Manole manole.v.r...@gmail.com javascript:;
   Reply-To: dev@oodt.apache.org javascript:; dev@oodt.apache.org
   javascript:;
   Date: Friday, August 21, 2015 at 11:51 AM
   To: oodt dev@oodt.apache.org javascript:;
   Subject: Moving repository to git
  
   Hello,
   
   Did you consider moving to git from svn as the main repository for the
   project?
   Especially since most of the pull requests are done from github,
   converting
   a diff to svn feels a bit unnecessary.
   
   It woul have made my life easier certainly. Especially if I didn't
 have
  to
   convert from git to svn diffs in order to post reviews on review
 board.
   
   Thanks,
   Radu.
  
  
 
  --
  *Lewis*
 

Re: how do you manage OODT files vs. project-specific files?

[Michael Joyce]

Hi Valerie,

In my experience we tend to take the files that we modify for a specific
project and put them into version control. This includes any config files
that we needed to change, code changes, and various other things (PGE
templates, etc.). Often times we replicate the component structure to make
our lives easier. So if the config for the resource manager is in
/resmgr/policy we would have a /resmgr/policy folder in our project VCS and
put the modified config there.



-- Joyce

On Tue, Feb 17, 2015 at 11:46 AM, Mallder, Valerie 
valerie.mall...@jhuapl.edu wrote:

 Hi All,

 I am looking for some advice, so please respond if you have ideas on this
 topic.

 Assuming you are using OODT, or developing OODT, to support a totally
 different project that you are working on in your day job, how do you
 manage all of your OODT files vs. all of your project-specific files?  I am
 looking for real-life examples of how people are configuration managing
 their files.

 I am using the deployed RADiX Archetype, which suggests that I keep my
 project specific files in an 'oodt/extensions' directory.  However, I have
 also made changes to some OODT configuration and policy files such as
 workflow/policy/tasks.xml and workflow/policy/events.xml, etc.

 If I wanted to upgrade to a new version of the RADiX Archetype and deploy
 a new release of the RADiX Archetype over top of my current version, then
 all of my changes to the tasks.xml and events.xml files would be lost.

 What is your favorite way of managing your OODT installations so that
 changes you have made to the configuration  files and policy files located
 in each OODT application's directory tree are not overwritten?  (Ideally, I
 wish I could keep all of my project-specific and changed files outside of
 the each OODT application directory tree, but it doesn't sound like anyone
 does this.)

 Thanks,

 Val

 P.S. I have managed large software systems before, but they were different
 from OODT in that



 Valerie A. Mallder

 New Horizons Deputy Mission System Engineer
 The Johns Hopkins University/Applied Physics Laboratory
 11100 Johns Hopkins Rd (MS 23-282), Laurel, MD 20723
 240-228-7846 (Office) 410-504-2233 (Blackberry)

Re: OODT ./filemgr start gives me a error -- Can't load log handler java.util.logging.FileHandler`

[Michael Joyce]

Strange that it was failing with maven 3. I thought that had been resolved.
Maybe I'm mixing issues together in my mind. If it's still breaking for you
then we should definitely open up a new ticket


-- Joyce

On Mon, Feb 16, 2015 at 10:42 PM, Aditya Dhulipala adhul...@usc.edu wrote:

 Hi Micheal,

 Thanks for your response!

 OK. I’ll try that. I’ll create ../logs

 Yeah there were some issues I ran into while building oodt. It failed the
 first time i tired mvn install. But that happened because I was using mvn
 version3. I installed mvn2 and it worked fine. This is probably a minor
 issue but maybe we can raise an issue for support for mvn3…

 So far I’ve not run into any other issues. I’ll shoot a message if I do.
 Thanks for helping me out!

 —
 adi

 Aditya Dhulipala
 USC Viterbi
 adhul...@usc.edu




  On Feb 16, 2015, at 9:38 PM, Michael Starch starc...@umich.edu wrote:
 
  Aditya,
 
  Did you create a logs directory?  It is missing the directory, so it
 cannot
  create your log files.  Otherwise, it looks ok.  It seems to have
 started,
  any other issues?
 
  Michael
 
 
  On Mon, Feb 16, 2015 at 9:30 PM, Aditya Dhulipala adhul...@usc.edu
 wrote:
 
  Hi,
 
  I'm trying to run filmgr component of oodt
 
  I'm running steps off from this guide -
 
 https://cwiki.apache.org/confluence/display/OODT/OODT+Filemgr+User+Guide
 
  On executing ./filemgr start I get the following error:-
  http://pastebin.com/cudQPmAa
 
  Can anybody take a look and help me out?
 
  Thanks!
  --
  Aditya
 
 
  adi
 

Re: [DISCUSS] Cutting over the website from http://oodt.staging.apache.org

[Michael Joyce]

+1, let's get it out there!


Mike

On Sun, Feb 8, 2015 at 5:26 PM, Ramirez, Paul M (398M) 
paul.m.rami...@jpl.nasa.gov wrote:

 +1

 Sent from my iPhone

  On Feb 8, 2015, at 5:06 PM, ke...@apache.org ke...@apache.org wrote:
 
 
  On 2015-02-08, at 5:23 PM, Mattmann, Chris A (3980) 
 chris.a.mattm...@jpl.nasa.gov wrote:
 
  So on Wednesday I will ask infra to switch over the site please get
 updates in by then and if there are updates to be made we can always do so
 after as frequently as folks and their commit but desire.
 
  The CMS is the way to go. Editing through-the-web is immediate and
 effective, and everyone can do it. I just put in a bunch myself.
 
  Let's make it live!
 
  --k
 

Re: [VOTE] Apache OODT 0.8.1 RC #2

[Michael Joyce]

+1!



-- Joyce

On Sun, Feb 8, 2015 at 5:28 PM, Ramirez, Paul M (398M) 
paul.m.rami...@jpl.nasa.gov wrote:

 That would be awesome.

 --Paul

 Sent from my iPhone

  On Feb 8, 2015, at 4:09 PM, Chris Mattmann chris.mattm...@gmail.com
 wrote:
 
  Yep and longer term I am thinking of a more clever solution (aka plugin)
 to
  update radix script version
 
  On Sunday, February 8, 2015, Tom Barber tom.bar...@meteorite.bi
 wrote:
 
  I'm happy if Val is happy ;)
 
  +1
 
  On 08/02/15 22:17, Lewis John Mcgibbney wrote:
 
  Well Tom my justification for my +1 was that there has been a bunch of
  other issues addressed.
  At end of the day it is down to release managers digression.
  I am happy to see 0.8.1 going out as is per release candidate.
  The script update instructions are documented within the release
 procedure
  so we will catch them the next time around.
  My VOTE stands as +1
  Thanks
  Lewis
 
  On Sun, Feb 8, 2015 at 1:58 PM, Tom Barber tom.bar...@meteorite.bi
  wrote:
 
  I've not looked, but don't you need to unpeg Radix so the fix that
 0.8.1
  was built for in the first place goes through?
 
  Tom
 
  On 08/02/15 21:44, Lewis John Mcgibbney wrote:
 
  Hi Chris,
 
  On Fri, Feb 6, 2015 at 9:47 PM, Mattmann, Chris A (3980) 
  chris.a.mattm...@jpl.nasa.gov wrote:
 
   The release was made from the OODT 0.8.1 tag (r1658019) at:
 
  http://svn.apache.org/repos/asf/oodt/tags/0.8.1/
 
   I've checked both of the tags for the OODT version within the radix
 
  archetype script
 
  Both RC's at [0] and [1] have OODT version pegged to 0.8 rather than
  0.8.1
 
  [0]
  http://svn.apache.org/repos/asf/oodt/tags/0.8.1-rc1/mvn/
  archetypes/radix/src/main/resources/bin/radix
  [1]
  http://svn.apache.org/repos/asf/oodt/tags/0.8.1/mvn/
  archetypes/radix/src/main/resources/bin/radix
 
  MD5: matches
  SHA1: matches
  Signature: Chris Mattmann (CODE SIGNING KEY) mattm...@apache.org
  Python tests: pass
  Java tests: pass
 
  All good for me except for the radix script.
  What do people think?
 
  Personally, I am +1 as this is not a blocking issue.
 
  Lewis
 
 
  --
  *Tom Barber* | Technical Director
 
  meteorite bi
  *T:* +44 20 8133 3730
  *W:* www.meteorite.bi | *Skype:* meteorite.consulting
  *A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2
 7YG,
  UK
 
 
 
 
 
  --
  *Tom Barber* | Technical Director
 
  meteorite bi
  *T:* +44 20 8133 3730
  *W:* www.meteorite.bi | *Skype:* meteorite.consulting
  *A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2
 7YG, UK
 

Re: OODT 0.8 release

[Michael Joyce]

I've run into some problems with the CMS where it wont stage the build to
the 'staging' site before Chris (on OCW). However, if you go through the
bajillion links and get to the point of publishing to prod it'll work. I'm
not sure why and it's rather annoying.

Where was yours getting hung up? Maybe we've been having the same pain.


-- Joyce

On Tue, Dec 9, 2014 at 1:43 PM, Mattmann, Chris A (3980) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Didn’t work for me :-) It committed, but it didn’t publish to the
 staging area. Note, my update to the link for the download on the
 home page, that never made it?

 ++
 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...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Associate Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++






 -Original Message-
 From: Tom Barber tom.bar...@meteorite.bi
 Reply-To: dev@oodt.apache.org dev@oodt.apache.org
 Date: Tuesday, December 9, 2014 at 12:34 PM
 To: dev@oodt.apache.org dev@oodt.apache.org
 Subject: Re: OODT 0.8 release

 Edit - Save... ;)
 
 Yeah I'll put something on the wiki
 
 On 09/12/14 20:16, Mattmann, Chris A (3980) wrote:
  BTW, I have tried to publish some updates before and
  was getting an error - the commit would go through but
  it wouldn’t update the staging site. Tom can you throw up
  a quick how to guide? I see you have been updating and
  it seems to be working.
 
  ++
  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...@nasa.gov
  WWW:  http://sunset.usc.edu/~mattmann/
  ++
  Adjunct Associate Professor, Computer Science Department
  University of Southern California, Los Angeles, CA 90089 USA
  ++
 
 
 
 
 
 
  -Original Message-
  From: Tom Barber tom.bar...@meteorite.bi
  Reply-To: dev@oodt.apache.org dev@oodt.apache.org
  Date: Monday, December 8, 2014 at 12:43 PM
  To: dev@oodt.apache.org dev@oodt.apache.org
  Subject: Re: OODT 0.8 release
 
  Cool, I'll crank the juggernaut.
 
  On 08/12/14 20:42, Mattmann, Chris A (3980) wrote:
  PERFECT, let’s do it!
 
  ++
  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...@nasa.gov
  WWW:  http://sunset.usc.edu/~mattmann/
  ++
  Adjunct Associate Professor, Computer Science Department
  University of Southern California, Los Angeles, CA 90089 USA
  ++
 
 
 
 
 
 
  -Original Message-
  From: Tom Barber tom.bar...@meteorite.bi
  Reply-To: dev@oodt.apache.org dev@oodt.apache.org
  Date: Monday, December 8, 2014 at 12:20 PM
  To: dev@oodt.apache.org dev@oodt.apache.org
  Subject: OODT 0.8 release
 
  Alright chaps
 
  Just thinking about our plans for quarterly-ish releases. With the
  fixes
  to tika, and the fact that ops-ui doesn't work properly without a
  patch,
  would it be worth planning for an early Jan release, and we can spend
  some time in the run up to Christmas kicking Lewis in the privates
  until
  he either a) finished the new website or b) divides and conquers and
  tells us what needs doing to get it finished so we can all pitch in.
 
  Either way, I think a Jan release would be sensible after our meeting
  earlier in the year.
 
  Let me know what you think.
 
  Tom
  --
  *Tom Barber* | Technical Director
 
  meteorite bi
  *T:* +44 20 8133 3730
  *W:* www.meteorite.bi | *Skype:* meteorite.consulting
  *A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2
  7YG,
  UK
 
  --
  *Tom Barber* | Technical Director
 
  meteorite bi
  *T:* +44 20 8133 3730
  *W:* www.meteorite.bi | *Skype:* meteorite.consulting
  *A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2
 7YG,
  UK
 
 
 --
 *Tom Barber* | Technical Director
 
 meteorite bi
 *T:* +44 20 8133 3730
 *W:* www.meteorite.bi | *Skype:* meteorite.consulting
 *A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2 7YG,
 UK

Re: [VOTE] Apache OODT 0.7 release candidate #1

[Michael Joyce]

Sigs and MD5s look good. +1 from me. Great job on all the hard work folks

--- Verification Output ---


--

  Verifying MD5s

--


** NOTE ** Using md5deep with -M ...

The files that match a known MD5 will be displayed.

If you don't see an RC artifact something is wrong with the MD5


Verifying MD5s ...

18fe10547d0ca91e6b6337d45ba98521
/Users/mjjoyce/Coding/OODT/rc_staging/apache-oodt-0.7-src.zip




  Verifying Signatures



Verifying Signature for file apache-oodt-0.7-src.zip.asc

gpg: Signature made Sun Sep 14 22:43:58 2014 PDT using DSA key ID B876884A

gpg: Good signature from Chris Mattmann (CODE SIGNING KEY) 
mattm...@apache.org

gpg: WARNING: This key is not certified with a trusted signature!

gpg:  There is no indication that the signature belongs to the
owner.

Primary key fingerprint: 03CC 5FFA 61AA AD3C 8FF2  5E92 70F0 9CC6 B876 884A


-- Joyce

On Mon, Sep 15, 2014 at 6:50 AM, Chris Mattmann mattm...@apache.org wrote:

 Hi Folks,

 I have posted a 1st release candidate for the Apache OODT 0.7 release. The
 source code is at:

 https://dist.apache.org/repos/dist/dev/oodt/

 For more detailed information, see the included CHANGES.txt file for
 details on
 release contents and latest changes. The release was made using the OODT
 release process, documented on the Wiki here:

 https://cwiki.apache.org/confluence/display/OODT/Release+Process

 The release was made from the OODT 0.7 tag (r1624941) at:

 http://svn.apache.org/repos/asf/oodt/tags/0.7/


 A staged Maven repository is available at:

 https://repository.apache.org/content/repositories/orgapacheoodt-1000/


 Please vote on releasing these packages as Apache OODT version. The vote
 is
 open for the next 72 hours.

 Only votes from OODT PMC are binding, but folks are welcome to check the
 release candidate and voice their approval or disapproval. The vote passes
 if at least three binding +1 votes are cast.

 [ ] +1 Release the packages as Apache OODT version

 [ ] -1 Do not release the packages because...

 Thanks!

 Chris

 P.S. Here is my +1.

Re: [ANNOUNCE] Tyler Palsulich is now on the PMC too!

[Michael Joyce]

Yay! Welcome Tyler!!!


-- Joyce


On Tue, Jul 22, 2014 at 11:36 AM, Tom Barber tom.bar...@meteorite.bi
wrote:

  Aye I'll +1 that, and move this over to dev@

 We have an ever expanding PMC, so lets do some Project Managing! ;)

 I think we need to come up with some roadmap goals, both regarding
 features, and also the existing code base, build systems and delivery.

 Personally I think it would be benificial to get a bunch of us on the
 phone and discuss it in real time (I'm GMT based which does make it a
 little tricker) rather than hash it out over a 6 month chain of emails.
 Like I said the other day, I don't really know how other projects manage
 this type of thing so those with more experience may want to chime in here.

 Regards

 Tom



 On 22/07/14 18:33, Lewis John Mcgibbney wrote:

   Hi Tyler,
  Please see Tom's thread from before the weekend.
  I say we have a full on discussion on establishing a roadmap.
  For us to establish and agree on this will be extremely beneficial for
 the project.
  Lewis


 On Tue, Jul 22, 2014 at 10:29 AM, Tyler Palsulich tpalsul...@gmail.com
 wrote:

 Hi All,

  Thanks for inviting me to join as a committer and PMC member! I'm happy
 to be part of the project. Any tips on where to dive in?

  Tyler

Re: ApacheCon 2014 Slides

[Michael Joyce]

I'm a bit late to the party but these look great Tom!


-- Joyce


On Tue, Mar 25, 2014 at 11:11 PM, Mattmann, Chris A (3980) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Those are some boss slides my friend. I will sincerely miss watching
 you present them but they record the vids so I'll see it anyways! ;)
 Awesome job

 ++
 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-5th floor
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Associate Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++






 -Original Message-
 From: Tom Barber tom.bar...@meteorite.bi
 Reply-To: dev@oodt.apache.org dev@oodt.apache.org
 Date: Monday, March 24, 2014 5:56 PM
 To: dev@oodt.apache.org dev@oodt.apache.org
 Subject: Re: ApacheCon 2014 Slides

 Last call folks,
 
 I anyone wants to say anything good or bad regarding my slide deck
 before I submit them in an hour or two, say it now! :)
 
 
 https://docs.google.com/presentation/d/1L7JVF9i8HsDWA0Qm41eGQrzymbiD4tX7M1
 SK_OPnTRk/edit?usp=sharing
 
 Tom
 
 
 On 23/03/14 21:43, Tom Barber wrote:
  Always helpful if I provide the link..
 
 
 
  Tom
 
  On 23/03/14 21:42, Tom Barber wrote:
  Alright chaps
 
  Seeing how everyone else presenting chickened out, and its left to
  the guy thats never actually done anything with OODT in anger to
  present an interesting and intuitive demo, can some of you guys cast
  an eye over my slides between now and Monday night and add if you
  have anything constructive to add, please let me know before the
  deadline :)
 
  They are still a work in progress and will no doubt change between
  now and tomorrow night, but let me know what you think.
 
  Tom
  --
  *Tom Barber* | Technical Director
 
  meteorite bi
  *T:* +44 20 8133 3730
  *W:* www.meteorite.bi | *Skype:* meteorite.consulting
  *A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2
  7YG, UK
 
 
  --
  *Tom Barber* | Technical Director
 
  meteorite bi
  *T:* +44 20 8133 3730
  *W:* www.meteorite.bi | *Skype:* meteorite.consulting
  *A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2
  7YG, UK
 
 
 --
 *Tom Barber* | Technical Director
 
 meteorite bi
 *T:* +44 20 8133 3730
 *W:* www.meteorite.bi | *Skype:* meteorite.consulting
 *A:* Surrey Technology Centre, Surrey Research Park, Guildford, GU2 7YG,
 UK

Re: ApacheCon 2014

[Michael Joyce]

Sounds like an interesting talk. Very nice!


-- Joyce


On Fri, Jan 31, 2014 at 6:39 PM, Chris Mattmann chris.mattm...@gmail.comwrote:

 Great job Tom!

 
 Chris Mattmann
 chris.mattm...@gmail.com




 -Original Message-
 From: Tom Barber tom.bar...@meteorite.bi
 Reply-To: dev@oodt.apache.org
 Date: Friday, January 31, 2014 1:15 PM
 To: dev@oodt.apache.org
 Subject: Re: ApacheCon 2014

 Submitted it is!
 
 On 31/01/14 16:29, ke...@apache.org wrote:
  Nothing short of brilliant.
 
  Submit! Submit with extreme prejudice! 
 
  --k
 
  On 2014-01-31, at 8:16 AM, Tom Barber tom.bar...@meteorite.bi wrote:
 
  Alright folks I was planning on pitching this, what do you think?
 
  Title: Utilising the power of Apache OODT with open source Business
 Intelligence tools
 
  Event: ApacheCon North America 2014
 
  Submission Type: Presentation
 
  Category: Developer
 
  Biography: Tom Barber has been a vocal Open Source Business
 Intelligence proponent for many years. He is well known in the Pentaho
 community having instigated a number of Pentaho community meetings in
 the UK and Europe. He has extensive experience of information
 management, business intelligence, data warehousing, and data
 integration with a range of technologies. Tom is also the project
 founder of the Apache Licensed Saiku OLAP Analysis Tool. When not
 hacking Open Source technologies Tom is the Technical Director of
 Meteorite Consulting, an open source focussed Business Intelligence
 consultancy.
 
  Abstract: Apache OODT is a science data processing framework that is
 NASA's
 
  first project to be released to the ASF. OODT has many publicised use
 cases in the science world, but less discussed is the use of Apache
 OODT in the world of business. We'll run through a number of examples
 detailing how OODT can be used for non science based applications. We
 will also demonstrate how Open Source Business Intelligence tools can
 interact with Apache OODT and help integrate Apache OODT into Business
 Intelligence ecosystems. Using Pentaho Data Integration we will
 demonstrate data ingestion and extraction, and how ETL tools can help
 you manipulate data from within Apache OODT.
 
  Audience: User of OODT, and Business Intelligence developers who have
 an interest in Metadata storage and processing.
 
  Experience Level: Beginner
 
  Technical Requirements: Projector
 
 
  Cheers
 
  Tom
 
 
  On 30/01/14 21:11, Christopher Warner wrote:
  Ok, i've got a day to decide.. i'm swamped and I feel really lazy
 right
  now, let me procrastinate a little while I think of how I can lay
 this out
  into a compelling talk of some sort.
 
 
  On Wed, Jan 29, 2014 at 11:54 PM, Chris Mattmann
  chris.mattm...@gmail.comwrote:
 
  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 christopher.war...@gmail.com
  Reply-To: dev@oodt.apache.org
  Date: Wednesday, January 29, 2014 8:45 AM
  To: dev@oodt.apache.org
  Subject: 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, or some other unstructured crazy format. So part of the
  problem is social and dealing with researchers outside of the
 science
  paradigm whom aren't readily used to processing or extracting
 information
  from their data in that way.
  I think it's a great idea that would give an immediate visually
 accessible
  way of how it's useful for data sets not-related to science alone.
 
  From New York..
  On Mon, Jan 27, 2014 at 2:08 PM, Tom Barber
 tom.bar...@meteorite.bi
  wrote:
 
  So I saw the call go out that they were short of applications and
 it got
  me thinking once again.
 
  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
 applications,
  its not publicised very well  which is where I want to try and
 advocate
  OODT
 
  But with my current clients don't have an obvious use case, but
 there
  must
  be a bunch if I sit down and think about them, so I was thinking
 about
  pitching a talk along the lines of
 
  Utilising the power of Apache OODT with mainstream Business
  Intelligence tools
 
  Where I can discuss a few real world scenarios and I was
 thinking I
  could demonstrate OODT integration with Pentaho Data
  Integration(Apache Licensed) using ETL to control ingestion
 and use
  Pentaho Data Integration to query 

Re: OODT's Git mirror at Github is borked

[Michael Joyce]

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, Jake Farrell jfarr...@apache.org wrote:

 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 merged into
 that mirror. The Github notification email that is sent contains a link to
 the patch and the description or comment that was given, not the actual
 patch itself.

 Tika has 3 open pull requests which are 8 months old to 2 years old,
 comments can be made by anyone on them, but only Github Apache org admins
 can close them out.

 If OODT is interested in switching over to git and using git-wip-us.a.o as
 the primary repository I would be happy to help migrate them.

 If you have any other questions let me know
 -Jake




 On Thu, Jan 30, 2014 at 12:21 AM, Chris Mattmann mattm...@apache.org
 wrote:

  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 Tika and in a few other projects.
 
  Is that not the case anymore? I could directly commit to OODT as I'm
  a PMC member for the project, but I wanted to be cool and try Github ;)
 
  Cheers,
  Chris
 
 
 
 
  -Original Message-
  From: Jake Farrell jfarr...@apache.org
  Reply-To: jfarr...@apache.org jfarr...@apache.org
  Date: Wednesday, January 29, 2014 9:19 PM
  To: jpluser mattm...@apache.org
  Cc: infrastruct...@apache.org infrastruct...@apache.org,
  dev@oodt.apache.org dev@oodt.apache.org
  Subject: 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 them or close the pull request.
  
  
  Thanks
  -Jake
  
  
  
  
  
  
  On Wed, Jan 29, 2014 at 11:58 PM, Chris Mattmann
  mattm...@apache.org wrote:
  
  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
  
  
  
  
  
  
  
 
 
 

Git(hub) Mirrors are oudated?

[Michael Joyce]

I noticed that the Last Updated dates of the files in the OODT Github
Mirror [1] all read 3 Years Ago. Is the github/git mirror this far behind
our SVN?

[1] https://github.com/apache/oodt

-- Joyce

Re: Git(hub) Mirrors are oudated?

[Michael Joyce]

You're right Sherl I wasn't looking at trunk (but it is still very far
behind). I wonder who we could bother about why this is so far behind.
Maybe Chris will know when he finds this thread...


-- Joyce


On Thu, Aug 29, 2013 at 5:09 PM, Lewis John Mcgibbney 
lewis.mcgibb...@gmail.com wrote:

 Yes it is certainly behind.


 On Thu, Aug 29, 2013 at 4:47 PM, Sheryl John shery...@gmail.com wrote:

  Hi,
 
  The other branches have later commits [1]. The 'trunk' has commits from 4
  months ago..But, it doesn't have a 0.6 branch or tag so it still seems
  behind SVN.
 
  [1] https://github.com/apache/oodt/branches
 
 
  On Thu, Aug 29, 2013 at 4:33 PM, Michael Joyce jo...@apache.org wrote:
 
   I noticed that the Last Updated dates of the files in the OODT Github
   Mirror [1] all read 3 Years Ago. Is the github/git mirror this far
  behind
   our SVN?
  
   [1] https://github.com/apache/oodt
  
   -- Joyce
  
 
 
 
  --
  -Sheryl
 



 --
 *Lewis*

Review Request: OODT-627 Review

[Michael Joyce]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/11810/
---

Review request for oodt, Chris Mattmann and Cameron Goodale.


Description
---

Please see [1] for a more thorough description. I decided to change the 
MappingFunc calls instead of the actual implementation of ReplaceFunc since I 
felt that this made the most sense. The ReplaceFunc implementation seems to 
imply the replace 'orig' with 'with' approach so I left that alone and 
changed the various calls.

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


Diffs
-

  
/trunk/xmlps/src/main/java/org/apache/oodt/xmlps/product/XMLPSProductHandler.java
 1490420 
  /trunk/xmlps/src/main/java/org/apache/oodt/xmlps/profile/DBMSExecutor.java 
1490420 
  /trunk/xmlps/src/main/java/org/apache/oodt/xmlps/structs/CDEResult.java 
1490420 

Diff: https://reviews.apache.org/r/11810/diff/


Testing
---

Tested locally with the setup from [1] and changes to the example-ps.xml file 
from [2]. All tests pass and functionality of product handler is as expected.

[1] https://cwiki.apache.org/confluence/display/OODT/XMLPS+Quick+Start+Guide
[2] https://issues.apache.org/jira/browse/OODT-627


Thanks,

Michael Joyce

Re: JIRA label for new users

[Michael Joyce]

Awesome, thanks Gav!!


-- Joyce


On Tue, May 21, 2013 at 5:34 PM, Gavin McDonald ga...@16degrees.com.auwrote:

 Ok so I've implemented this using the labels suggested.

 Someone should change the default skill level to any issues they are
 familiar with to what is appropriate.

 Gav...


  -Original Message-
  From: mltjo...@gmail.com [mailto:mltjo...@gmail.com] On Behalf Of
  Michael Joyce
  Sent: Wednesday, 22 May 2013 1:14 AM
  To: dev@oodt.apache.org
  Subject: Re: JIRA label for new users
 
  +1 on this Gavin.
 
  Re. actual label names, how about a name followed by an (explanation) of
  the difficulty level:
 
  Don't Know
  Newcomer (Easy) - Everyone can do this level Committer (Medium) - This is
  for regular contributors/committers. Where the vast majority of issues
 would
  fall.
  Expert (Hard) or Guru or ChrisMattmann or whatever everyone likes for
  hard - Used sparingly when an issue requires expert component
  knowledge
 
  We could default the field to Don't Know so every issue always has some
  level?
 
  I like the CouchDB approach but I feel they have too many options.
  Easy
  Easy - Medium
  Medium - Hard
  Really Really Hard (Their Guru level)
 
  So, when something is Medium, which category does it fall into? I think
 the
  most important part of this system is identifying the difficulty for
  newcomers. The other levels are just nice to have in my opinion. That
 being
  said, I think simpler is better here.
 
  What do you guys think?
 
 
  -- Joyce
 
 
  On Sun, May 19, 2013 at 8:30 AM, Rajith Siriwardana 
  rajithsiriward...@gmail.com wrote:
 
   +1 for having a label for issues that new users can help to resolve.
  
  
   On Sun, May 19, 2013 at 8:51 PM, Mattmann, Chris A (398J) 
   chris.a.mattm...@jpl.nasa.gov wrote:
  
Thanks Gav. +1 to using a controlled value field to make the labels
meaningful.
   
Let's see what others think but I am for sure +1.
   
Cheers,
Chris
   
   
  ++
  
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
   
  ++
  
Adjunct Assistant Professor, Computer Science Department University
of Southern California, Los Angeles, CA 90089 USA
   
  ++
  
   
   
   
   
   
   
-Original Message-
From: Gavin McDonald ga...@16degrees.com.au
Organization: 16 degrees complete web solutions
Reply-To: dev@oodt.apache.org dev@oodt.apache.org,
ga...@16degrees.com.au ga...@16degrees.com.au
Date: Sunday, May 19, 2013 3:37 AM
To: dev@oodt.apache.org dev@oodt.apache.org
Subject: RE: JIRA label for new users
   


 -Original Message-
 From: Mattmann, Chris A (398J)
 [mailto:chris.a.mattm...@jpl.nasa.gov]
 Sent: Friday, 17 May 2013 1:37 AM
 To: d...@climate.incubator.apache.org
 Cc: dev@oodt.apache.org
 Subject: Re: JIRA label for new users

 Great idea, please implement on OODT too! (cc to dev@oodt for
 peeps)
   :)

We can start to use labels now for jira tickets, we just need an
agreed and documented set of labels. Why? Too many labels and we
run the risk of there being too many and they sort of Lose the
impact and meaning. So a few well-chosen labels for attention
grabbing is needed.

Every Jira ticket has a Labels section so this is available now.

However, my main point of this mail, is that we can add custom
fields to our issues. Some projects have done such a thing, some,
like the couchdb project, have
   implemented a
drop down field in
their jiras so that anyone at a glance can determine if the ticket
is newcomer, contributor, committer, hardcore project  guru or Greg
Stein level. (OK so I made that last
   level
up, but really, the choice of drop down field name is ours to
decide)

Pop on over to the couchdb jira and take a look.

I am happy to implement this in the OODT Jira if you agree it a
good idea.

I'm a big +1 ftr

Gav...


 Cheers,
 Chris


  ++
 
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/

  ++
 
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA

Re: New list ?

[Michael Joyce]

I would be fine with it either way. I usually just filter the commit
related messages anyway if I'm on an especially verbose list. OODT is quiet
enough that I don't really mind them being the same.


On Tue, Apr 30, 2013 at 7:42 AM, ke...@apache.org wrote:

 Progress on OODT is strongly driven by JIRA issues, so my only concern
 would be that folks might forget to subscribe and miss out on what
 initiates progress on the codebase.

 --k

 On 2013.Apr.30, at 5.04a, Gavin McDonald ga...@16degrees.com.au wrote:

  A personal peeve of mine, all the jira notifications going to the commits
  list, makes it hard to see whats going on.
 
  (Yes I could filter but..)
 
  How about an issues@ list where we can send the jira stuff ?
 
  Gav...
 
 

Re: Review Request: XMLPS should provided ordered results based on requested fields

[Michael Joyce]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9438/#review16585
---

Ship it!


Ship It!

- Michael Joyce


On Feb. 14, 2013, 3:50 p.m., Chris Mattmann wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/9438/
 ---
 
 (Updated Feb. 14, 2013, 3:50 p.m.)
 
 
 Review request for oodt.
 
 
 Description
 ---
 
 Patch augments CDEResult with an ordering of the fields, and then uses that 
 and a few other functions to make sure that the result row is populated in 
 order, pulling from dyn, and const fields where needed.
 
 
 This addresses bug OODT-564.
 https://issues.apache.org/jira/browse/OODT-564
 
 
 Diffs
 -
 
   
 ./trunk/xmlps/src/main/java/org/apache/oodt/xmlps/product/XMLPSProductHandler.java
  1444629 
   ./trunk/xmlps/src/main/java/org/apache/oodt/xmlps/structs/CDEResult.java 
 1444629 
 
 Diff: https://reviews.apache.org/r/9438/diff/
 
 
 Testing
 ---
 
 none yet.
 
 
 Thanks,
 
 Chris Mattmann
 

Re: [HEADS UP] Apache OODT now builds with Maven3 too

[Michael Joyce]

Woot! Nice. Now I can't give Cam more Stack Overflow points though =(.

Mike


Mike


On Wed, Feb 6, 2013 at 3:54 PM, Cameron Goodale good...@apache.org wrote:

 Chris,

 This is a huge win!  Now I can let Apple install Maven 3 with my next Java
 update and I don't have to revert.

 -Cam


 On Sun, Feb 3, 2013 at 3:41 PM, Mattmann, Chris A (388J) 
 chris.a.mattm...@jpl.nasa.gov wrote:

  Hey Guys,
 
  With r1441987, OODT 0.6 trunk now builds with Maven3. Yay!
 
  Trunk still builds with Maven2 as well.
 
  [INFO] CAS Product Server  SUCCESS
  [2.791s]
  [INFO] CAS Workflow Manager Monitor Web App .. SUCCESS
  [2.341s]
  [INFO] Catalog and Archive File Management Browser ... SUCCESS
  [1.561s]
  [INFO] Catalog and Archive Workflow Management GUI Editor  SUCCESS
  [9.351s]
  [INFO] Process Control System Operator Interface Webapp .. SUCCESS
  [4.225s]
  [INFO] OODT Process Control System JAX-RS service layer .. SUCCESS
  [4.131s]
  [INFO] Apache OODT ... SUCCESS
  [37.794s]
  [INFO]
  
  [INFO]
  
  [INFO] BUILD SUCCESSFUL
  [INFO]
  
  [INFO] Total time: 7 minutes 6 seconds
  [INFO] Finished at: Sun Feb 03 15:40:18 PST 2013
  [INFO] Final Memory: 100M/191M
  [INFO]
  
  [chipotle:~/tmp/oodt0.6] mattmann%
 
 
  Cheers,
  Chris
 
 

Re: [VOTE] Apache OODT 0.5 RC #1

[Michael Joyce]

Looks good to me! +1

Thanks Chris!


Mike


On Fri, Dec 21, 2012 at 6:15 AM, Cinquini, Luca (3880) 
luca.cinqu...@jpl.nasa.gov wrote:

 +1 from me too,
 thanks for putting this together,
 Luca

 On Dec 20, 2012, at 9:43 PM, Sean Kelly wrote:

 
  Will do thanks dude. Are you +1 on the release?
 
  See: http://s.apache.org/WQC
 
  --k

Re: [ANNOUNCE] Welcome Mike Joyce as an Apache OODT PMC member and Committer

[Michael Joyce]

Thanks much everyone!

As I'm sure most of you know, I'm currently working at JPL with Chris and
many others from here. I look forward to helping out more on OODT and
getting the opportunity to work with everyone!

Thanks all!
Mike


Mike



On Fri, Nov 30, 2012 at 5:58 PM, Mattmann, Chris A (388J) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Hi Folks,

 Mike Joyce was recently elected to the Apache OODT PMC and as a committer
 on the project.
 Welcome Mike! Feel free to say a bit about yourself.

 Cheers,
 Chris

Re: [jira] [Commented] (OODT-328) Remove jpl.nasa.gov references from code

[Michael Joyce]

I'm not familiar, if someone can comment I'd appreciate it.

Mike



On Wed, Aug 8, 2012 at 8:00 AM, Cameron Goodale sigep...@gmail.com wrote:

 Mike and Chris,

 I just scope this svn url in the file and I wonder if the CAS-SSO code has
 been pushed to Apache.  If the code has not been migrated then it will be a
 blocker to this issue.

 I did find an SSO package in the OODT Pear Channel here:
 http://pear.apache.org/oodt/

 Assuming the OODT Pear Channel has all the code in it:

 Since the edit is focused on a comment block / docstring change, it would
 seem that the checkout/build process needs to be re-written in this file,
 or omitted entirely if no longer necessary.


 Mike if you are unfamiliar with the PHP build/install process check with
 Andrew Hart or Shakeh Khudikyan (both on this mailing-list) for help.


 Keep up the great work,


 Cam

 On Tue, Aug 7, 2012 at 10:09 PM, Chris A. Mattmann (JIRA)
 j...@apache.orgwrote:

 
  [
 
 https://issues.apache.org/jira/browse/OODT-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13430872#comment-13430872
 ]
 
  Chris A. Mattmann commented on OODT-328:
  
 
  Mike: I would focus on the SVN lines since the DTD stuff and XML schema
 NS
  involves other discussions (for example, see Ross's recent Geospatial
 stuff
  e.g., in OODT-469 and OODT-471).
 
  If you fix files in SVN refs, I think we can call this done!
 
 
   Remove jpl.nasa.gov references from code
   
  
   Key: OODT-328
   URL: https://issues.apache.org/jira/browse/OODT-328
   Project: OODT
Issue Type: Bug
Components: build proces
  Reporter: Chris A. Mattmann
   Fix For: 0.5
  
   Attachments: grepoutput.txt
  
  
   We need to remove all references to jpl.nasa.gov in our code (for
  example I just saw one in:
 
 http://svn.apache.org/repos/asf/oodt/tags/0.3/balance/lib/pear/Providers/Auth/LDAPAuthenticationProvider.class.phpwhichmade
  me think that we need to code review before we roll 0.4).
 
  --
  This message is automatically generated by JIRA.
  If you think it was sent incorrectly, please contact your JIRA
  administrators:
  https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
  For more information on JIRA, see:
 http://www.atlassian.com/software/jira
 
 
 


 --

 Sent from a Tin Can attached to a String

Introducing myself

[Michael Joyce]

Hi all,

I'm a new intern in Chris/Cameron/Pauls' section at JPL. Just wanted to
send a quick email to introduce myself and say hello.

Look forward to helping out with the project!

Mike