Adrian Custer wrote: > 1) How we structure the headers of code files, notably to > indicate which files contain contributions which are used under > license rather than under copyright grant, > We keep the date range of any copyright that went into the file, along with any license that was encountered. In most cases it is LGPL across the board (say when forking JTS code). We have a few strange ones (some kind of pulic somain license on a few files, and possibly for our demos too?). The review.txt should list what is going on for each modules. > 2) If we need permission letters from employers for the > contributions of employees > Chris Holmes did this kind of thing for GeoServer; I do not know what is needed. > 3) What other work may be required to graduate, > I woudl like to: - Release a a 2.4 RC with everything order (so the OSGeo board could have a look at what they are signing up for) - Release a 2.4.0 with the headers modifed for OSGeo
I am not sure what we say about history? ... something like the following example from the catalog api: (c) 2007 Open Source GeoSpatial Foundation (c) 2003-2005 GeoTools PMC (c) 2005 Refractions Research, Inc. Or do we need to strip GeoTools PMC completly out of the picture (c) 2007 Open Source GeoSpatial Foundation (c) 2005 Refractions Research, Inc. In this case we may be able to simply list the module maintainers name as oppoesd to (c) GeoTools PMC - indeed I reccomend it. GeoTools tries to live/breath by module maintainers > 4) Anything else you can think of that we need to consider. > Can you make a decision (not recommend) a license for the demo code? I will be happy to apply it on trunk. > Hopefully, I can integrate your answers into a final version of this > document which we can attach to the new version of the "assignment" > document when that goes back out for review. > Cheers, Jody ------------------------------------------------------------------------- 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 Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
