Migrate to Google Code?

[Bob Ippolito]

I've been considering this for a while but didn't want to put forth
the effort at the time, but I think that with the release of 1.4 it
would be a good time to migrate from the Mochi Media hosted Trac and
SVN over to something else. My personal preference is Google Code
because we already use that for our other open source projects and it
wouldn't require transitioning from a mainstream VC solution to
something more obscure (e.g. launchpad, github).

Per, do you have any thoughts on this?

-bob

[Per Cederberg]

Google code seems fine by me. Especially if we get better access for
normal users.

The only issue I come to think of is that the mochikit.com web site
automatically updates from svn trunk. Don't know if it would be easy
to keep that link. Something which is pretty good to have from time to
time. Especially when we are linking to examples and demos that are
actually inside the project repo (not just on the web site).

On the other hand, we often forget to make_docs.py or pack.py before
committing to svn. So perhaps it would be good to have these steps
performed automatically by some automated web publisher. So that we
wouldn't need the packed version in svn...

Just my random thoughts.

Cheers,

/Per

[Bob Ippolito]

Keeping the commit hooks for updating the site is possible, I'll
probably set up a svn mirror at or near the current svn repository and
our internal tools will be able to update that. Might have to hook up
some kind of mail hook thing to have it happen "instantly" though, I
don't think google code has a HTTP post-commit "web hook".

Anyway, I can take care of it. These are the sorts of reasons that I
didn't bother before, but I'm willing to do it now :)

I do like keeping the packed version and docs in svn, but we could
have a process that automatically does it and performs a second commit
when necessary (but setting that up might be a little too much work to
bother).

-bob