That's not the angle we're trying to hit here. We have customers, and potential
> ones, complaining that GeoTools is full of "junk" and they point at the
> unsupported modules. So it's a cleanup angle, has nothing to do with
> that is useful or not useful from the pov or GeoServer and uDig.
I don't view the unsupported modules as part of GeoTools; they are a community
out reach
area - a wild attempt to get more contributors.
> The idea is not to remove all unsupported modules, but at least the ones
> that are really dead and in no shape for resuscitation.
Okay; I just have a hard time identifying that.
> Simone compiled a list with some that should not be removed, I agree,
> but there are a few that are indeed just increasing the confusion
> such as mysql/oracle-spatial/db2 (becuse they have stable replacement).
Agreed, the gpx2 should also be scrubbed.
> We already have the separate branch for all of those modules, it's the past
> ones. If you create a parallel branch who's going to keep it up to date?
Asking people to grab stuff from the past would also work for me; the downside
is we cannot
ask people to fix things in the past.
So what would the procedure be; they would ask on the email list if they can
work on "excel" for example; and
copy it from 2.7.x to trunk?
Jody
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
