Michael G Schwern wrote:
My concern is that we'll be spending time
futzing with git rather than hacking on QA stuff.
We all know SVN/SVK and can stand to use it for a little while longer.
Agreed. One hackathon I attended wasted one-third of the participants'
available time because everyone had to download a Perforce client and
learn how to use it.
I discussed this in my lightning talk in Houston last year, "How to Get
the Most Out of a Hackathon"
(http://thenceforward.net/perl/yapc/YAPC-NA-2007/houslight.tgz). In
general, each project being worked on at a hackathon should have a
pre-announced repository/VCS. Then it becomes the responsibility of
each hacker to install the appropriate client on his/her laptop and
learn the basics of checkin/commit before the event.
If, coming out of this event, you collectively learn something about
organizing hackathons, please post that new knowledge to this list so
that I can incorporate it into the next version of my talk!
Thank you very much.
Jim Keenan
