Adrian the "providence" review was carried out last year - basically a code audit to make sure all the headers are in place. You can look at the resulting review.txt for each module and see the results.
We do use external code; geotools has a range of licenses - in cases where we were in trouble I contacted the developer (happy fun ball license?). In some cases we could not recover (integer parser taken right out of the sun JDK) and the code was changed so we were not in violation. When code originated in other projects the record is kept in the header, with a list of (c) statements and dates. The developers guide and incubation pages have more details. But we probably need another providence review :-( Jody Adrian Custer wrote: > Hey jody, > > I'm about to delve into the code to see what our licensing structure > looks like. Do you know of any place that we use external code? Do you > know how we have handled the need to include copyright notices in that > code? > > thanks, > adrian > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
