Thanks for the introductions Martin, feels like I have a whole new group of people to meet.
I am doing planning this week; my goal is to review the available implementations and decide which one to support (see GeoTools supported module process). In an ideal world I would love to function as a facilitator, and spend my time on QA and documentation. And now for the difficult part - as a GeoTools PMC I *really* want to see both implementations go forward (as this will keep implementors from making assumptions - forcing them to work against the GeoAPI interfaces). On a pragmatic level I am being paid to make sure a implementation is available in GeoTools for the next release. The decision on where I spend my time will be based after a code review, and talking with you all. I would strongly prefer to do this on the public email list - so perhaps after these introductions we could move to geotools-devel? Cheers, Jody > Hello all > > Congratulation to Sanjay, who just got his gratuation thesis! (I got the > new from Prof. Roehrig). > > This is a funny timing, since we just had a talk yesterday in Geotools > IRC about geometries. Jody would like the get a closer looks to the > implementations around. There is currently two of them (as far as I > know): > > * Wrappers around JTS library (2D and cartesian coordinate system only). > * Native Java implementation by Sanjay, with additional work from the > team in Arles. > > In order to give a chance to Sanjay and Jody to look at the work from > the student at Arles, I think that it would be help if we commit their > work to Geotools SVN. Would it be okay for the Arles team? If yes, I can > ask to the Geotools PMC to grant write access on the > "geotools/modules/unsupported/geometry" directory to one representative > of the Arles team. Sanjay still have write access too, so he can > supervise the work if he wish. > > An alternative may be to send the modified classes to Sanjay or myself, > so we can commit them. But when the development work is more extensive > than just patch, it sometime easier to get the classes commited by the > peoples who work on it. Since the geometry module is not yet part of the > full Geotools build, hacking in this module still a "low risk" activity > for now. > > Martin > > > P.S.: it is going to be important to stay in touch with every > contributors (Sanjay, Roehrig, peoples from Arles...) in the next few > months, for legal reason. Geotools is trying to get more organized, > including on legal standing. Geotools is in the incubation process of > OSGEO (http://www.osgeo.org/), which is dedicaced to Open Source GIS > software. In the future, we may (not sure, we are still in discussion) > ask to every Geotools contributors, for all modules (not just geometry), > to sign some legal paper (copyright assignment or grant of license, I'm > not very aware of current state of discussion) to OSGEO, with the > garantee that the license will stay the OpenSource approved LGPL. The > purpose is to get the code protected by a real legal entity on the > behave of all contributors, a little bit like other fundations (Apache, > Mozilla...). I will contact you again on this topic when I will have > more details. > > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
