I've got a couple of questions about when to "apply for" and when to make a release of a GeoTools module.
I'll soon have a logical group of working and unit tested code for my GPX2 module. This is basically a GPX reader/parser and a Waypoint object. This code is currently residing in my SurveyOS SVN repository. Someone could use this code to parse and manipulate waypoint objects. (For example: This code could be used to import waypoints into UDig.) However, the module as a whole is far from complete. I want to add support for writing waypoints, not just reading them, and also reading/writing of other GPX entities. I might also swap out JDOM with an XML Pull Parser implementation or something like Apache's Axiom. I've been putting off "applying" for an actual GeoTools module because it means I'll have to actually read the developer's guide. :] Still, I know I need to make the move to the GeoTools SVN at some point, and I think this might be the best time. Are there any rules or guidelines that dictate how much functionality or how operational code must be before it is granted status as an expiremental module? Does GeoTools encourage incremental releases of modules as functionality is added? Or would you guys prefer that I get everything working in my own SVN, and then hop over to a GeoTools module hosted in the GeoTools SVN? Thanks, Landon ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
