forked from deegree/deegree3
-
Notifications
You must be signed in to change notification settings - Fork 2
Obsolete modules proposal
hwbllmnn edited this page Mar 25, 2013
·
5 revisions
This is a discussion page to discuss how we can clean up the deegree modules a little bit.
- we have @uncoupled@, where a couple of non-maintained modules reside
- we have modules in the main tree which are unmaintained
Let's clean up the @uncoupled@ directory, then move more unmaintained modules to @uncoupled@.
I believe almost everything can be deleted from @uncoupled@:
- @deegree-demos@ - we have proper workspaces as demos now
- @deegree-maven-plugin@ - it's been extracted into a separate GitHub project
- @deegree-wfs-cite110-postgis-blob/relational@ - completely out of date, were never running anyway
- @deegree-workspace-sos@ - nobody seems to know the status
- @resources@, @scripts@ seems like some directories made it from the pre-maven-phase
Anybody knows the state of the @deegree-mdeditor@?
The following modules are marked as unmaintained in the stability status page and should be @uncoupled@ IMHO:
- @deegree-api-examples@
- @deegree-core-3d@
- @deegree-core-observation@
- @deegree-services-sos@
- @deegree-services-wpvs@
- @deegree-sos-webclient@
- @deegree-tools-3d@
- @deegree-workspace-wpvs@
A couple of modules I'm not sure about:
- @deegree-processprovider-sextante@ - should we keep it? It pulls a lot of dependencies and is not maintained.
- @deegree-featurestore-geocouch@ - as long as there's no interest from the community, we should move this to @uncoupled@