Hello Axel and Nick, sorry for the delay.\\

I'll be replying all previous posts in one, hope you don't mind.

{quote:camueller}
 We should bring the latest "official" sources of SnipSnap to our repository.
 We add your modifications
{quote}

Couldn't agree more the 1st version should be uttoxeter. I've done the same thing on my private SVN, so it won't be a problem neither having the "official" source not committing a patch. 

{quote:camueller}
In my professional projects I deal a lot with build infrastructure (e.g. Maven). Therefore I will take care of this. This will include setting up the project at java.net, create a subversion repository, bug tracker, mailing list etc.
{quote}

Regarding the build infrastructure you think it's an improvement changing from ant to maven. If so, could you please elaborate a bit on why? In all the projects I work I use ant, except when I need to build {link:CAS|url=http://www.ja-sig.org/products/cas/}. In my small experience, Maven seems a bit too much verbose. Although I must admit that I don't have actual arguments against it. I'm interested in knowing your thoughts on this.

{quote:camueller}
Below is the project information I would like to use. It comes from snipsnap.org mostly.
(...)
{quote}

I'm ok with the project details :-)

{quote:camueller}
Did you have to modify Radeox or can we use it as a third-party library?

Can you please send me the "offical" SnipSnap sources you started with?
{quote}

I'm using a modified version because I add to adjust how some HTML was rendered to be XHTML 1.0 Transitional valid.

I can either send you the source or probably you can still download it from snipsnap.org it's up to you. I've used the latest one, 1.0b3-uttoxeter.

{quote:cassiel}
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.
{quote}

I think all the major modifications I've made can be found in [my_snipsnap_fork_feature_list] but I admit there's a lack of documentation... I  have to take care of that.

{quote:cassiel}
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?
{quote}

Well Radeox is a standalone wiki syntax render kit, it still makes sense keeping it separate because it's a standalone package, other software application might use it (xwiki for example started with it, but they've switch now). Besides, for what I know, radeox is still maintain by Stephen.
 

{quote:cassiel}
here's a fair chunk of compile errors and some absolute links to library files (/Users/ghost/...)
{quote}

My bad, sorry :-) that's what happens when you commit the wrong .project file. /Users/ghost/... is my homedir! Anyway to fix that just do the following:

1. right click on project and select properties
1. Select java build path on the right menu
1. select Libraries 
1. Remove all the libraries listed there (except the JRE System Library)
1. Select add Jars and browse into the SnipSnap's lib directory and add them all

You should be set to compile it in eclipse if you want.

{quote:camueller}
Before you start getting the code to built we should be sure about the version of the code.
{quote}

I've forked SnipSnap 1.0b3-uttoxeter.

{quote:cassiel}
One thing it would be useful to know is whether the data schema, or the XML export format, has changed since uttoxeter - if it has then I'm already committed to more recent versions.
{quote}

The data schema is still the same. I had that concern because, since I knew data migrations would just make people unease to change to my fork :-)