Sounds if things are starting to happen.

I guess the first stage is to make the current release available with enough documentation so that people can do a source build and get it running. If source is available then it shows that the project hasn't become stiffware and that they aren't locked into it.

The Ant build is pretty straightforward, if rather opaque (to me, anyway); the SnipSnap configuration pass is pretty simple although I'd like to see more documentation about what's actually happening here. (I'm thinking of ways of smoothing the effort for newcomers.)

I'm happy to see things Mavenised, although my Maven chops are pretty bare; I've done a lot more in Ant. I guess Maven would let us see what the library dependencies are.

Re: Radeox: is there a good reason for keeping it as a separate project? In what way is it useful outside SnipSnap as a whole?

Regarding other interest: there's still the old SnipSnap mailing list - might be worth a note there at some stage. Also, commenters to the last message at snipsnap.org might have left email addresses.

Anyway, let me know what I can do to help.