Jody Garnett ha scritto: > See earlier review of all the GSIP's there is some overlap between these > two: > - http://geoserver.org/display/GEOS/GSIP+17+-+Community+module+handling > - http://geoserver.org/display/GEOS/GSIP+22+-+Extensions > > Can this be resolved; or combined into a single policy change separating > out the difference between how these are handled? > The GSIP+22 will need to change or define project build procedure; we > should figure out what documentation pages > need to be updated?
+1 > - Can we have a procedure for "removing an extension" I would suggest the following. The module goes back into community limbo if any of the requirements for getting into extension drops below the acceptable level. When anyone notices the requirements are no more there, the PSC contact the maintainer, which has to fix up the problem in time for the next release. If that does not happen, the module gets moved into community > - Since these are a lot more formal than community modules; can we get a > wiki page with docs? Or even a formal installation/useage doc? Agreed, this should be a requirement to get into "extensions". > I am correct in thinking these are full fledged running modules (like > WPS?) that are ready to go - they are just not in the default GeoServer > download. As such I would like to hold them to the same high standard. Yep. Cheers Andrea ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
