[Foss4g2009] Code Sprint

[Tim Bowden]

On Sun, 2008-10-12 at 22:05 +1100, Cameron Shorter wrote:
> I'm very strongly against having a code sprint before FOSS4G.
> Before FOSS4G the Organising Committee will be flat out fixing last 
> minute details and won't have time to support the Code Sprint as well. 
> Either the code sprint, or the main event will suffer.
> 

The idea of having the code sprint before the conf was to enable the
various projects to take advantage of the integration showcase, but
you're right.  The loss in having it before is more than the gain.
After is much more sensible.

> So while I can see the merits to attendees of having the code sprint 
> first, in practice, it puts too much risk on the main event. (We also 
> might find we have some extra $$ left over from the conference, which 
> could be splashed around the code sprint).

Be nice if we could find a sponsor for the code sprint- Someone who
isn't necessarily spatial (and hence a target for conf sponsorship) but
does have a history or willingness to support open source development in
general (and here Tim wonders why they're not a conf sponsor target
anyway).  Still, that would be nice rather than something to spend too
much energy on at this stage.

So, proposed sprint dates then: Monday 28 Oct - Wed 30 Oct.  The
feedback on the list (and privately) seems to indicate that the break
would be well received (though many of the more fervent supporters of a
longer code sprint at Cape Town are still in the disconnected wilds).
Given the state of most delegates by the end of the conf, I'd be
surprised if there were too many who were up to three days intense
coding without a break anyway.

Regards,
Tim

> 
> Tim Bowden wrote:
> > On Fri, 2008-10-10 at 23:21 -0700, Dave Patton wrote:
> >   
> >> On 2008/10/10 9:23 PM, Tim Bowden wrote:
> >>
> >>     
> >>> The feeling I got from talking to ppl in Cape Town was that at least 3
> >>> days is required.  Some will do 4 days if it's offered, but 3 is less
> >>> risky and probably enough to meet most objectives.
> >>>
> >>> I'd strongly favour Wed - Fri before the conf proper.
> >>>       
> >> Assume for the moment that we have Workshops on Tuesday,
> >> and that the plan is for a "3-day Code Sprint".
> >>
> >> What about the idea of having it be Sat - Mon before
> >> the conference? That would still leave the option of
> >> groups discussing further work during the week(e.g.
> >> in a BOF; at the bar), and continuing the following
> >> weekend(perhaps in a less formal arrangement than
> >> the prior weekend). Is that 'less risky' than doing
> >> Wed - Fri, which enforces a break for some people
> >> that either they may not want, or may not be a long
> >> enough break for what they want to do?
> >>     
> >
> > Lets take it to discuss.  Them's the people that will be impacted.
> >
> > Regards,
> > Tim
> >
> >   
> 
> 
-- 
Experience is that marvelous thing that enables you recognize a mistake
when you make it again.