<div dir="ltr">in the event that it's not already completely clear from my post 5 minutes ago (d'oh, before reading this thread)<br><br>i completely concur with what chris has said here. I think it's pretty reasonable to think that anyone who is going<br>
to put in the $ to go out to australia is probably planning on spending at least two or three days to do a bit of <br>travelling (i feel confident of that but maybe it's actually *not* a valid assumption?) and so having the spacing between<br>
the code sprint and the conference is in my mind a great idea. <br><br>-e<br><br><div class="gmail_quote">On Sat, Oct 11, 2008 at 2:27 PM, Christopher Schmidt <span dir="ltr"><<a href="mailto:crschmidt@crschmidt.net">crschmidt@crschmidt.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Sat, Oct 11, 2008 at 04:45:49PM +0800, Tim Bowden wrote:<br>
> The FOSS4G 2009 team are planning a 3 day code sprint. The conference<br>
> itself will be starting with workshops on Tuesday 20 Oct and finishing<br>
> on Friday 23rd Oct.<br>
><br>
> The possibilities for the code sprint are for the preceding Wednesday-<br>
> Friday giving a long weekend in between (giving time for touring, more<br>
> coding or whatever) or Sat - Monday with no break between the code<br>
> sprint and the conference. What would people prefer?<br>
<br>
</div>I'm strongly in favor of the former.<br>
<br>
For one, like Cape Town, Sydney is too long of a flight to make it just<br>
a trip about the conference, in my opinion. We had an organized group do<br>
a two day trip down the cape after the Code Sprint in Cape Town, and I<br>
think it was a really successful bonding experience for those of us who<br>
came along, allowing some non-coding social time where we all go to hang<br>
out and know each other a little better, which I expect will help<br>
develop better communications in the coming months within the project.<br>
<br>
Also, having a break between the conference after the code sprint keeps<br>
the possibility of having a 'finished' result of something by the<br>
conference more likely as well. In general, code sprints are good at<br>
producing a lot of unpolished code: a couple days can help to get the<br>
code a bit more polished in order to present it as a new development<br>
during the conference, if people so choose.<br>
<br>
Lastly, I think that having a break before the conference gives people a<br>
bit of time to unwind: code sprints tend to be exhausting if you do them<br>
right (taking full advantage of shared physical location with long<br>
hours, for example), and going directly from that into a conference<br>
(described by one attendee as being similar to 'a 5 day long rave' due<br>
to the amount of energy it consumes) feels dangerous. :)<br>
<br>
Regards,<br>
<font color="#888888">--<br>
Christopher Schmidt<br>
Web Developer<br>
</font><div><div></div><div class="Wj3C7c">_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.osgeo.org">Discuss@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/discuss" target="_blank">http://lists.osgeo.org/mailman/listinfo/discuss</a><br>
</div></div></blockquote></div><br></div>