I'm almost done with the migration and integration of the various source repositories.
One final question here; would anybody object to actually picking my current SVN/SVK repository as master for the ChiliMoon sources?
We lose the nice graphical interface which is on the current repository on lysator. I could start exporting my repository to that CVS. OTOH, there exist similar interfaces for SVN. Alternately, by using SVK, you have your own local copy of everything which works *really* fast and easy (much better than plain SVN). I can give write access to all ChiliMoon developers here. I don't mind (might even encourage) moving the repository back to lysator (now or later).
Incidentally, this also means that I have a fully SVN/SVK up-to-date mirror for both Roxen and Pike repositories. If someone wants the repository in order to migrate Roxen and/or Pike to SVN, just drop me a note.
And, yes, this also means that I have retrofitted SVN/SVK to fully show that ChiliMoon emerged out of Roxen around 2002/06/03 and that they share the same repository history now (file moves and renames and everything).
As soon as we agree on where the ChiliMoon repository lives, I'll hand out coordinates to access it (we have enough bandwidth here to host it for now, if that is what we would decide on).
P.S. Merry Christmas everyone :-).
One final question here; would anybody object to actually picking my current SVN/SVK repository as master for the ChiliMoon sources?
I think that would be great. If and when the time comes for migrating back to Lysator, I think that would be good too, but that time is not right now, since those of us who would be involved in settint it up are a bit busy at the moment. In losing the current browse repository UI, it might be worth testing some alternative; the demos I've seen of Chora for instance (http://freshmeat.net/projects/chora/), isn't tenth as bad as ViewCVS.
Besides, actually having a live svn repository might encourage people to upgrade code librarian all the way to supporting subversion. (Not sure if I'll have the time myself, but it's more likely than if there is no present need for it.)
The same probably applies to the Pike site and repository, eventually. Will there be a read-only subversion tree open for Pike, that we can point to from the site (noting details such as how often it is synced et cetera)?
pike-devel@lists.lysator.liu.se