Re: [Geoserver-devel] Community modules cleanup

[Jody G. <jga...@re...>]

If I can recommend form the uDig experience (which is horrible) ... make 
sure the community section is branched when the geoserver release
is made. In the uDig community section we have a a guessing game in 
order to figure out what module goes with what release; to the point 
some community
folders have started their own trunk/ branches/ tags/ structure.

Be up front about how versioning is going to be handled, and if a module 
is not "upgraded" for an entire release cycle - say 1.5.x then it can 
start as a
1.4.x community module; so rather than an "unsupported" section; people 
can go back in the version history to look for working examples
that have not been maintained.

Cheers,
Jody
> Hi,
> looking at the community section I could not avoid
> noticing the dead modules in that area. Given that
> most of them have not been mantained in ages, others
> are just proof of concept, and that in the end
> we can find them in older branches, I'd like
> to propose the removal of some stale community
> modules from trunk and the 1.6.x branch.
> Here is a list of what I think should be removed:
> * Issues (unmantained)
> * modular_ui (no interest)
> * preferences (unmantained)
> * statusreporter (unmantained)
> * net.opengis.wcs/wcs11 (remove from 1.6.x, promote
>    to main modules on trunk)
>
> Opinions?
> Cheers
> Andrea
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Geoserver-devel mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>