Jody Garnett ha scritto: ... > I do like the idea of *time* as a measure of how hard the the code is > to get right; how about 1 week Andrea?
I believe the thing should be considered from a different angle. When do we say a solid "no" to a contribution that's adding a new dependency? If we face a contribution that either adds a new dependency or is just dropped, where do we draw the line? To make you a realistic example, most of the paid works I worked on lately where split in chunks varying from 3 days to two weeks, adding a week on top of one of them may prove to be impossible, or either so hard that it's tempting to propose a new extension point in GeoTools and add the real work in GeoServer. > And also how about the (gasp) idea of forking; assuming the code is > LGPL of course ... we have already forked JTS once; can we fork JODA > and just take out the tricky code we are having trouble with? And for > that matter can we fork geoapi... >> I agree with Martin here, we need to decide on per-case basis. I >> usually try to reuse whatever is around, unless I found problems in >> it or it is to big to carry it along, nut sometimes rewritingis the >> best option. I can provide another example which was interesting >> for me. In the metadata module there are some hekper classes for >> implementing equals and hashcode methods which can substitue pretty >> easily the usage of commons-lang for that purpose. IMHO reducing >> the number of dependencies for at least the core modules of >> geotools is a crucial objective. >> > Thanks for putting that into words. > > If I can put things on the other foot Simone (shoot me down if this > is a bad idea) - if we need to have a dependency on commons-lang > anyways can we remove our metadata-module helper classes for equals > and hashcode? > > In short I want less duplication; having code in a dependency and in > our code base just makes the decision confusing and the code > inconsistent. I would like us to make a decision; or get out of the > way. Jody++, having our code duplicating a library that we depend onto (without removing it) is the worst solution. Cheers Andrea ------------------------------------------------------------------------- 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
