Comments inline, on the kill or keep issue. Two questions first: - Can we have a middle ground where we do not distribute the code? - Can we have a middle ground where modules like oracle datastore (that are in use) are included in the build; and leave everything else in unsupported out of the build ... geoserver is looking at similar steps where they have specific profiles that include their "community" modules; we could handle unsupported in the same way (ie nothing in unsupported is > Do we want to drop the following modules? > We have two options a) do not include them in the release or b) drop them.... Since we want to get done ... > unsupported/community-schemas > people care about this one so keep it and don't include it in the release; the developers are working on 2.4.x now and will show up on trunk and we can bother them then (Rob Atkinson and Gabriel know more). > unsupported/geomedia (with a weird copyright) > We should keep it out of the build; someone may care about geomedia in the future and this would be a good starting point. > unsupported/jpox > We can kill it - this was student code; and they have both gotten jobs outside of the open source geospatial world. > unsupported/notifycollections (with apache license) > Kill it.
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
