>>>>> "BR" == Bob Rogers <[EMAIL PROTECTED]> writes:
BR> From: "Bill Ricker" <[EMAIL PROTECTED]> BR> Date: Sat, 12 Jul 2008 21:05:54 -0400 >> But what you say about git's suitability for such a hackathon is >> right on the mark. If Andy has a git repo, then the commit history >> could be preserved after the hackathon, without needed to give everybody >> direct access. (There are also git <=> Subversion tools as well.) BR> Checking in the result of the hackathon as a single delta to the trunk BR> would be ok BR> Will Andy allow us to commit directly? In that case, we should try to BR> get everybody commit bits ASAP. I'm guessing that Google has Subversion BR> set up to support per-file permissions, so he only needs to grant us BR> access to a new branch. let's not worry about that yet. we can always do the work offline and submit a big patch. the goal is to code up the new core loop. any source control we need to use will be for our benefit. and we may not even need it if we divide the work well and have someone be the source editor. BR> If not, we will still need to arrange a shared repository far enough BR> in advance so that everybody can be sure that they have a compatible BR> client. Otherwise, getting tests to testers will be a nightmare. (I'm BR> still skeptical there will be enough setup time.) like i said, we can always bypass source control for the time being. just emailing source to the list (or only attendees) will be fine for a quick hack. i would rather people focus on the design and coding to be done. and few have joined this thread and that needs to improve. so hop on board and join the (h)ackathon. this will be a chance to learn some neat perl, help with a popular perl project and have fun. uri -- Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.sysarch.com -- ----- Perl Code Review , Architecture, Development, Training, Support ------ --------- Free Perl Training --- http://perlhunter.com/college.html --------- --------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com --------- _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
