TiddlyWeb through the end of the year

[chris...@gmail.com]

I'm hoping to take TiddlyWeb through a proper beta and to a release
candidate before the end of this year. If you are curious about
TiddlyWeb this message might be of interest to you. If you aren't you
can probably skip this one.

To do that lots of bugs need to be shaken out (and I'm sure there are
plenty), documentation needs to be updated and expanded and any
missing but important features either need to be added or at least
recorded for future releases. There are a lot of holes that have been
left as sort of exercises for the reader so that the evolution of the
system is informed by the people who use it.

TiddlyWeb's development is now being tracked by trac at http://trac.tiddlywiki.org/
with a growing collection of tiddlers. You can see the results of a
query of all unresolved tickets at http://preview.tinyurl.com/6cqqep

To help move the process along I'd appreciate several bits of help:

* If you have access to trac and can change priority on the tickets or
leave comments, please raise, lower or comment as you see fit to give
some indication of the relevance of the defect or ehancement.
* If you are interested in TiddlyWeb, please download either a
distribution file from http://peermore.com/tiddlyweb/dist/ and
experiment with it, or check out the source at
http://svn.tiddlywiki.org/Trunk/association/serversides/tiddlyweb/core/
* Explore plugins, such as twoter and spowt (mentioned on this list),
and others found at http://svn.tiddlywiki.org/Trunk/contributors/ChrisDent/experimental/tiddlyweb-plugins/
. The plugins have been great tools for exposing bugs and are a great
way to learn some of things TiddlyWeb can do.
* Take a ticket, try to fix it, provide a patch if you do, or what you
learned as a comment.
* Use your imagination to learn about and break things.

In each of these cases even the tiniest bit of feedback, or the
smallest patch can make a huge difference in moving the process along.

I'll be watching trac, dealing with tickets, finding and fixing bugs
as I'm able, and making regular releases of the code.

If you have any questions please feel free to post to this list or
contact me directly.

Thanks for your help and input!