[flud-devel] goals for 0.2.0

[Alen Peacock]

I've compiled a short list of the issues I'd most like to see solved
in 0.2.0 (please forgive bugzilla url nastiness):
http://www.flud.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&target_milestone=0.2.0&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=

#26, #67, and #68 are related in that they give a lot of
bang-for-the-buck demo-wise.  #26 is the least critical in this regard
-- the solution for #67 is likely sufficient in terms of demonstrating
functionality (and provides pieces that make solving #26 much easier).

#21 and #35 are review bugs, not likely to take significant time
during this release cycle.

#16 is not too difficult given that we've solved this for the inverse
operation and we just need to copy that here, but requires some time
for qa/fix cycles.

#30, #64, and #69 are related to claims.  These could be pushed out
into a later release, but it'd be nice to get a start on #69 in order
to get to a point where we can document a stable protocol version.

I'm going to start knocking these down as the fancy strikes.  There
are a couple in here that would be good for a noob to take a crack at.
 If anyone out there is itching to get involved, send me an email (or
post here) and I'll provide a bit of guidance.

Alen