Hi again!
My comments below.

On Thu, Feb 12, 2009 at 4:40 PM, Claes Wikström <klacke@tail-f.com> wrote:
Davide Marquês wrote:

I second that thought! :)
My experience with git/github has also been very positive (thumbs up for the network graphs: http://github.com/blog/39-say-hello-to-the-network-graph-visualizer).

Hmmmm, I feel kinda reluctant. What would be the purpose?
I'd say: growth! :)

Github would provide a simply way for others to fork the official codebase and play around with new features having them visible by the community at large (which would help finding collaborators).
Using git helps speed up the collaboration process in that a small group of people can hack away, pulling/pushing changes as they go along without having to depend on the "official repository".
As for developments on the "official" Yaws repository, since you'd be using the same scm tool you could pull patches directly from other people's repositories without having to email patches around.

I really like github in that it get's people's contributions out in the open. Even if their changes aren't accepted back into the "official" codebase they're still there (who knows if someone won't find them useful!).
That might be enough to get more people contributing to Yaws and even if it doesn't it will enable Yaws to reach a more wider audience.

It's mostly Steve Vinoski and me using the repo anyway
and i sure don't need no graph visualizers.
The visualizer is actually quite useful for seeing code changes across branches and user's repositories.

Besides, svn works excellent for our purposes - thus I believe the
"if it works don't fix it" theorem applies here.
I am tempted to suggest a Yaws github mirror (http://github.com/guides/import-from-subversion) but since that would create a new channel for receiving contributions I think it's your call. ;)