I am considering moving some of the community-schemas code base from GeoServer to GeoTools. This raises several issues.
(1) Is there any copyright or licensing problem moving GeoServer code to GeoTools? (2) Which copyright headers should they use? Their original ones, or should they be changed to the new project? (3) Is there a best/preferred practice for how to do this? Dumb copy (losing history), svnadmin dump ... The code in question includes the WFS binding overrides in the wfs-c fork in the 1.6.x branch. Having these binding overrides in GeoServer prevents any GeoTools unit tests from touching them. This has allowed some deficiencies in GeoTools community-schemas-ds to persist for far too long. The key problem is that the existing GeoTools community-schemas-ds unit tests cover feature construction but not encoding, and there are no useful unit tests(!) for GeoServer community-schemas. Half of the action happens during encoding, so this is a big problem. This situation can be remedied by moving the bindings to GeoTools, and doing a lot of work to retrofit unit tests. I won't be moving this code right away, but it has to be done. It should probably be done when we port community-schemas to trunk, to minimise the carnage. -- Ben Caradoc-Davies <[EMAIL PROTECTED]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
