Last year FOSS4G saw a number of projects arrange a sprint prior (or during) FOSS4G. Are we interested in doing the same for GeoServer?
There are two ways to do this, but we would need to move quickly (both to talk to the OSGeo board about funding, and to establish a date before our contributors book flights).
BEFORE: This is what the QGIS team did last year. It has the advantage of having everyone well rested, and gives those travelling from overseas a chance to adjust to jet lag before the conference. The downside is the time conflict with any prep for workshops or presentations.
AFTER: For the feature model migration we extended the FOSS4G code sprint by a couple of days so we could get some work done. It worked fairly well, but after a long conference people may be tired and strung out.
Discussion:
The OpenLayers team had a sprint during the conference (instead of a birds of a feather meeting). In my experience the evenings is when the business of FOSS4G gets done, so I cannot imagine that working for us.
Sprints go better with a goal - migrating to a new wicket was what I had in mind (not sure if we can wait that long?)
Look I know this is a long ways away, but if there is interest we will need to figure it out now in order to line up OSGeo sponsorship. Bart (CCed) may be able to outline how that works?
I think the codebase can benefit from an in person code sprint.
Last year FOSS4G saw a number of projects arrange a sprint prior (or during) FOSS4G. Are we interested in doing the same for GeoServer?
There are two ways to do this, but we would need to move quickly (both to talk to the OSGeo board about funding, and to establish a date before our contributors book flights).
BEFORE: This is what the QGIS team did last year. It has the advantage of having everyone well rested, and gives those travelling from overseas a chance to adjust to jet lag before the conference. The downside is the time conflict with any prep for workshops or presentations.
AFTER: For the feature model migration we extended the FOSS4G code sprint by a couple of days so we could get some work done. It worked fairly well, but after a long conference people may be tired and strung out.
Discussion:
The OpenLayers team had a sprint during the conference (instead of a birds of a feather meeting). In my experience the evenings is when the business of FOSS4G gets done, so I cannot imagine that working for us.
Sprints go better with a goal - migrating to a new wicket was what I had in mind (not sure if we can wait that long?)
Last year FOSS4G saw a number of projects arrange a sprint prior (or during) FOSS4G. Are we interested in doing the same for GeoServer?
There are two ways to do this, but we would need to move quickly (both to talk to the OSGeo board about funding, and to establish a date before our contributors book flights).
BEFORE: This is what the QGIS team did last year. It has the advantage of having everyone well rested, and gives those travelling from overseas a chance to adjust to jet lag before the conference. The downside is the time conflict with any prep for workshops or presentations.
AFTER: For the feature model migration we extended the FOSS4G code sprint by a couple of days so we could get some work done. It worked fairly well, but after a long conference people may be tired and strung out.
Discussion:
The OpenLayers team had a sprint during the conference (instead of a birds of a feather meeting). In my experience the evenings is when the business of FOSS4G gets done, so I cannot imagine that working for us.
Sprints go better with a goal - migrating to a new wicket was what I had in mind (not sure if we can wait that long?)
On Sat, Feb 15, 2014 at 7:04 AM, Jody Garnett <jody.garnett@anonymised.com>wrote:
Look I know this is a long ways away, but if there is interest we will
need to figure it out now in order to line up OSGeo sponsorship. Bart
(CCed) may be able to outline how that works?
I think the codebase can benefit from an in person code sprint.
I guess it would be a good idea to have the FOSS4G code sprint be extended
by one day, which should not require
that much extra sponsorship, and it's a Sunday anyways
We probably need a show of hands of who is going to participate.
I'd still like to do a code sprint before September to complete the Wicket
upgrade, it costs a lot less
than a "in person" one if people can just set that day aside from work
(well, besides urgent stuff, of course)