VirtuaHac is a hackathon for the rest of us! Instead of travel and lodging expenses, we plan to host a collective hacking session using technology and distance collaboration tools.
1 Collaboration Tools
The tools we plan to use are:
- Google+ (http://plus.google.com) hangouts for real-time video (or audio-only) chat.
- 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.
2 VirtuaHac 2011.10
The first VirtuaHac is October 21-23, 2011.
Signups (including projects you know something about and are willing or interested in working on):
- Chris Smith
- snap-typed-sessions (mysnapsession in Hackage)
- gloss-web (https://github.com/cdsmith/gloss-web)
- mvclient (in Hackage) - willing only if anyone else is so motivated
- GHC Issue #4900 or #5527
- I'm also happy to join in other projects
- Clint Moore
- I'll work on anything I'm capable of.
- Etienne `AtnNn` Laurin
- Jens Petersen (juhp)
- probably something cabal/packaging related
Once VirtuaHac starts, we'll create a Lobby section of this wiki page. To start up a collaboration:
1. Create a Hangout on Google+. Name it to indicate it's part of VirtuaHac. 2. Post a link to the Hangout in the Lobby section. 3. 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.