datafinder-team team mailing list archive

["Guy K. Kloss" <guy.kloss@xxxxxxxxx>]

Hi,

I've just seen another development dependency (pysvn) added to the wiki here:

https://wiki.sistec.dlr.de/DataFinderOpenSource/RequiredDevPackages

This got me thinking, as we've hit a similar point in another project I'm 
participating (Griffin). 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, ...).

My suggestion is as follows, and I'm hoping to get some constructive 
discussion out of this:

 * 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/configure
   notes off to be specific for each plugin.

 * Document for each plugin how it is to be integrated/used with DataFinder.

Any comments?

Guy

-- 
Guy K. Kloss
School of Computing + Mathematical Sciences
Auckland University of Technology
Private Bag 92006, Auckland 1142
phone: +64 9 921 9999 ext. 5032
eMail: Guy.Kloss@xxxxxxxxx

Attachment: signature.asc
Description: This is a digitally signed message part.