I was looking at the "how to import a shapefile" page on the wiki - and it mentions the "do not invent here" policy and how that has lead to our massive amount of dependencies. Here are some ideas on how to set up a "positive" invent-here policy.
How about this for a GeoTools 3 where live is beautiful etc... GeoTools 3 should adopt an "Invent here" policy: 1) unless a dependency offers significant benefit we should roll our own - A dependency that brings in additional dependencies is a bad thing - A dependency that is used by several modules is a good thing 2 Significant benefit is measured in weeks not days - if you want to use Joda time it better offer more functionality than we can expect you to code in in two weeks. If you are using a couple of functions we can probably expect you to be able to code them up in 13 days... you do after all have Joda time to serve as an example. 3) unsupported modulesare not considered part of the library (and are not available for download) - as such they are free to experiment quickly making use of a range of jars when creating a prototype. Cheers, Jody ------------------------------------------------------------------------- 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
