<div>As noted in some other responses, we had a few technical difficulties (no power, no wireless, no projector) that caused a late start for a workshop that already had a lot packed in. Although all these problems were eventually solved, in my mind the biggest issue was that Chris and I spent too much time early on running around trying to ensure as many people as possible had a working laptop, causing us to have to choose between trying have a hope of getting people through the coding part of the workshop, or spending time giving context. </div>
<div><br></div><div>Some of the lessons I learned are: </div><div> - Triple check the vmware images to ensure nothing is missing (for example, having only vi instead of vim)<br></div><div> - Assume a quarter of your audience will have a laptop battery life of ~20 minutes (even if you have power, think about adaptors for international audience)</div>
<div> - Assume you won't have wireless connectivity, and that if you do, 10% of your audience will not be able to connect to the wireless anyway</div><div></div><div> - Assume 10% of your audience will not be able to load a vmware dvd (no dvd player, unable to load vmware, etc). This means you need to have another way for them to install everything (I had other dvds with windows binaries and linux binaries and source for everything, but you know, it takes a while to build gdal!)</div>
<div> - If you can get an email list of attendees beforehand, have them attempt to download/install/read some stuff to get started beforehand (I realize others may disagree with this ..)</div><div> - Have 3+ presenters. They don't all need to be experts on the topic at hand - if one of them can just troubleshoot some IT issues, that will let the main presenter(s) concentrate on the core of the workshop.</div>
<div> - It's easier to give a workshop where there's preconfigured desktop machines :)<br></div><div><br></div><div>Obviously a lot of the above depends on the size and type of workshop it is. GeoDjango happens to have a fairly .. robust .. set of dependencies. A workshop on something like OpenLayers could potentially be done with much less software to worry about (turns out the OL demo at the same event did also take advantage of a nice preconfigured GeoServer setup amongst other things, but you see my point).</div>
<div><div><br></div><div>Cheers,</div><div><br></div></div><div> -Josh<br></div>
<br><br><div class="gmail_quote">On Wed, Feb 4, 2009 at 12:17 AM, Cameron Shorter <span dir="ltr"><<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
foss4g 2008 OC,<br>
<br>
Looking through the 2008 program, I notice that the GeoDjango workshop asked participants to bring their own laptops.<br>
<br>
We are also considering inviting participants to bring their own laptops to some of the FOSS4G 2009 tutorials and would like to hear how successful this was in Johannesburg. Do you have any lessons learned that can be passed on to us?<br>
<br>
Please forward this email onto the presenter(s) if you know who they are.<br>
<br>
-- <br>
Cameron Shorter<br>
Geospatial Systems Architect<br>
Tel: +61 (0)2 8570 5050<br>
Mob: +61 (0)419 142 254<br>
<br>
Think Globally, Fix Locally<br>
Geospatial Solutions enhanced with Open Standards and Open Source<br>
<a href="http://www.lisasoft.com" target="_blank">http://www.lisasoft.com</a><br>
<br>
_______________________________________________<br>
FOSS4G2008LOC mailing list<br>
<a href="mailto:FOSS4G2008LOC@lists.osgeo.org" target="_blank">FOSS4G2008LOC@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/foss4g2008loc" target="_blank">http://lists.osgeo.org/mailman/listinfo/foss4g2008loc</a><br>
</blockquote></div><br>