RE: OODT-3 progress

2010-04-02 Thread Mccleese, Sean W (388A)
Hey Andrew,

Ok, great! 
I think a good way to divvy up the remaining work is by filetype, specifically 
*.java and then everything else (xml config files, etc). If that works for you, 
I'll take the remaining *.java files and go back and ensure we've gotten all 
the previous ones. Does that work for you?

-Sean


-Original Message-
From: Andrew Hart [mailto:andrew.f.h...@jpl.nasa.gov] 
Sent: Thursday, April 01, 2010 5:47 PM
To: oodt-dev@incubator.apache.org
Subject: Re: OODT-3 progress

Sean,

Great! I've been focused on the File Manager component, though I have to 
admit it has only been during the occasional free period rather than a 
concentrated effort. I find that once I get going, its a relatively 
painless process (highlight, paste, save, repeat) ..almost trance-inducing.


How would you like to divide it up? I'm happy with anything we come up 
with, and appreciate you taking the time to get us synchronized on this.

Thanks,
Andrew.



Mccleese, Sean W (388A) wrote:
 Hey everyone,
 
 Just writing to check the progress  coordinate completion on OODT-3 (ASL 
 license headers). I started prepending all the *.java files for a number of 
 the packages and I know ahart made some additional commits for more headers. 
 Rather than personally trawling through each individual file checking the 
 license, I wanted to coordinate with someone (ahart) to identify what 
 packages/filetypes are left to fix and then get this issue closed.
 
 Thanks!
 -Sean


Re: OODT-3 progress

2010-04-02 Thread Justin Erenkrantz
On Fri, Apr 2, 2010 at 9:25 AM, Mccleese, Sean W (388A)
sean.w.mccle...@jpl.nasa.gov wrote:
 Hey Andrew,

 Ok, great!
 I think a good way to divvy up the remaining work is by filetype, 
 specifically *.java and then everything else (xml config files, etc). If that 
 works for you, I'll take the remaining *.java files and go back and ensure 
 we've gotten all the previous ones. Does that work for you?

Just a note that the ASF committers repository has a bunch of
relicensing tools and scripts:

https://svn.apache.org/repos/private/committers/relicense/

And you can use RAT to verify the licenses are on all appropriate files:

http://incubator.apache.org/rat/

Caveat emptor, but it might help.  =)  -- justin