[flud-devel] Short-term plans

[Alen Peacock]

With the 0.0.2 release, we have a somewhat sane codebase and the
ability to build packages easily and make releases with greater
frequency.  Many of the features and improvements made between 0.0.1
(which was more of a snapshot than a release) and 0.0.2 could have
been made as releases in their own right, had it been as easy as it is
now to spit out a new release.

Moving forward, then,

Immediate priorities for the core:

A1. fix erasure coding

A2. finalize the resource trading bits of the protocol (for STORE command)

A3. enable trust metrics / persistence


Interface priorities:

B1. credential preservation/restoration upon startup

B2. invitations

B3. scheduling configuration (see D2)

B4. backup progress indication and resource consumption indication


Differential Compression:

C1. implement as discussed at http://www.flud.org/wiki/Architecture#Versioning


Scheduler priorities:

D1. dnotify/fam/etc plugin to replace monitoring via stat()

D2. configuration (see B3)

D3. differential compression (see C1)


When A1 alone is finished, that could form release 0.0.3 (if B1 or B2
sneak in with it, all the better).


Alen