detanglement of dependencies through separating out storage backend plugins
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DataFinder |
New
|
Medium
|
Unassigned |
Bug Description
DataFinder now has got a large and growing list of dependencies, but not everybody needs to satisfy each and every one of them. Many of them are dependent on the type of storage backend used by DF (e. g. boto for AWS, PySVN for SVN, pythonwebdavlib for WebDAV, ...).
The suggestion is as follows:
* Split off a core DataFinder application without any data store backends.
* Make all (meta-) data store backends into plugins, that can be developed and hosted separately, even if they live under the same project.
* For ease of use, a DataFinder distribution can be created that ships with the/a default plugin (most probably WebDAV).
* Split off the documentation (e. g. dependencies, build/install/
* Document for each plugin how it is to be integrated/used with DataFinder.
tags: | added: dependencies documentation refactoring |
Changed in datafinder: | |
importance: | Undecided → Medium |
milestone: | none → 2.3.0 |
Changed in datafinder: | |
milestone: | 2.3.0 → 2.4.0 |
Enhanced documentation: https:/ /wiki.sistec. dlr.de/ DataFinderOpenS ource/RequiredD evPackages
-> Separated core and persistence dependencies
-> Outlined that SVN or WebDAV bindings are at least required for use