Git/Darcs: We recommend (but don't require) using github or patch-tag for projects that are hacked on. You probably want to create a hackathon-specific repo to make it easier for hackathon members to collaborate without handing out permissions to the real code. Even if it's not through github or patch-tag, anyone sponsoring a project will need to provide an easy way to manage collective access to the source code. If that's 'darcs send', you'll have to be pretty responsive.

This Wiki: Make sure you have a HaskellWiki account, as we'll be posting links to current projects here.

I'll be open to working on anything, but I will be at a conference so my time will be limited. I'm especially open to learning to hack on GHC.

The Yesod Team (possibly any time zone)

There are a lot of items and ideas on our Todo and Wish List. A high-level, backwards-compatible websockets interface that will show off Haskell's amazing concurrency could be fun to work on during VirtuaHac.

Once VirtuaHac starts, we'll create a Lobby section of this wiki page. To start up a collaboration:

Create a Hangout on Google+. Name it to indicate it's part of VirtuaHac.

Post a link to the Hangout in the Lobby section.

As applicable, post links to version control or other resources under the project in Lobby, too.

As needed, also feel free to create "VirtuaHac Break Room" Hangouts, for chatting among people who aren't currently working on a collaboration. These could be a good chance to chat with others about what they've got in the pipe, and start collaborations.

If a collaboration is at or very close to 10 people (the size limit for Google+ hangouts), you may want to break it into subprojects.