Cameron, as you know I am supportive of having a cookbook which as others have said is a guide not a rulebook. In doing FOSS4G Denver, despite the lessons learned wikis and plenty of good advice from various members of the community, there were quite a few occasions where we (the LOC) missed something or misunderstood something, and we felt we were reinventing a lot of things. I think more of a checklist would be very helpful - things that should be done when you're starting up the effort, what should be done a year out, six months out, etc (and again there will be variations of course, including the event size - the main global event is generally planned further in advance than smaller regional events, etc).<div>
<br></div><div>So count me in for contributing.</div><div><br></div><div>Cheers,</div><div> Peter.<br><br><div class="gmail_quote">On Thu, Sep 6, 2012 at 2:22 PM, 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">Jeff,<br>
I think Stephen summarises the intent of the cookbook well as a guide rather than a mandate.<br>
I see it also as a way to expand what you have been doing individually (collecting collective knowledge) into a self help which is not limited by the time constraints of one person. Initially when there was only 1 foss4g event per year it was possible for one person to be the core driver, but we now have scores of events per year.<br>
<br>
Bob,<br>
I'd anticipate there being subheading in the Cookbook for using the LiveDVD at FOSS4G events.<div class="HOEnZb"><div class="h5"><br>
<br>
On 7/09/2012 1:00 AM, Basques, Bob (CI-StPaul) wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
All,<br>
<br>
Related to this, I've been wondering about how to go about setting up a business specific LiveDVD. Is there a possible synergy to be had with a recipe derived DVD (collection?) ??.<br>
<br>
Bobb<br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-----Original Message-----<br>
From: <a href="mailto:discuss-bounces@lists.osgeo.org" target="_blank">discuss-bounces@lists.osgeo.<u></u>org</a> [mailto:<a href="mailto:discuss-" target="_blank">discuss-</a><br>
<a href="mailto:bounces@lists.osgeo.org" target="_blank">bounces@lists.osgeo.org</a>] On Behalf Of Stephen Woodbridge<br>
Sent: Thursday, September 06, 2012 9:43 AM<br>
To: <a href="mailto:discuss@lists.osgeo.org" target="_blank">discuss@lists.osgeo.org</a><br>
Subject: Re: [OSGeo-Discuss] Should we write a FOSS4G Cookbook?<br>
Hello,<br>
I think the 'cookbook' is a great idea! It is about capturing our<br>
collective knowledge and experience, it not about limiting<br>
creativity or change. Just like in software when you have an<br>
individual contributor that has passion, vision and drive can<br>
create wonderful things, you also have to help the other<br>
contributors that are not so visionary to do a good job. The<br>
'cookbook' gives us a recipe for success, it is the basic stuff<br>
that you need to know to get the job done successfully. To<br>
continue with the analogy a visionary chef looks at the recipe<br>
and changes it to suit his creative talents.<br>
So it all depends on whether we "require" people to only follow<br>
the recipe or we use it as a guideline for people that are<br>
volunteering to help but may not have had past experience to get<br>
things done correctly.<br>
The cookbook is a great idea in my opinion.<br>
-Steve W<br>
On 9/6/2012 10:14 AM, Jeff McKenna wrote:<br>
> Hello Cameron,<br>
><br>
> Making sure that a transfer of knowledge happens from one<br>
FOSS4G local<br>
> committee to the next is something that I've championed for a<br>
very<br>
> long time now - it is a thankless invisible task that not many<br>
are<br>
> aware is happening (archiving documents, pinging committee<br>
members<br>
> over and over to openly archive documents and logos and files,<br>
making<br>
> sure such critical parts of FOSS4G are kept - ribbon in logo,<br>
t-shirts<br>
> for attendees, hands-on workshops - to the point that local<br>
committees<br>
> kind of become annoyed with me).<br>
><br>
> My vision of FOSS4G (credit here to original "FOSS4G Heroes"<br>
such as<br>
> Venka and Markus of course) has always been very simple: to<br>
spread the<br>
> Open Source Geospatial passion all around the world. It has<br>
not been<br>
> about money or politics. The result has been FOSS4G local<br>
committees<br>
> are free to take this passion and mold it into their own<br>
vision.<br>
> Events such as FOSS4G Cape Town in 2008 are proof of this.<br>
><br>
> I worry that such a 'cookbook' will hinder this open passion<br>
and<br>
> vision for a local committee.<br>
><br>
> The first drafts of such a cookbook came many years ago from<br>
Paul<br>
> Ramsey, from his 2007 experiences. Since then I've heard<br>
rumblings<br>
> from Arnulf, Cameron and others.<br>
><br>
> I guess it is time for such guidelines. For sure we need a<br>
conference<br>
> Content Management System internal to OSGeo that is required<br>
for all<br>
> FOSS4G local committees to use (not external systems such as<br>
> Basecamp); this is critical.<br>
><br>
><br>
> -jeff<br>
><br>
><br>
><br>
><br>
><br>
> On 12-09-05 7:34 PM, Cameron Shorter wrote:<br>
>> In analysing the downfall of FOSS4G 2012 [1] one of the key<br>
lessons<br>
>> that became apparent to me is that we are not very efficient<br>
at<br>
>> passing on Lessons Learned from one conference to the next.<br>
>><br>
>> Could we do a better job of knowledge transfer by building an<br>
OSGeo<br>
>> Conference Body of Knowledge? Something like a FOSS4G Cookbook<br>
[2]?<br>
>><br>
>> If so, what should be the scope of the cookbook? Should it<br>
only be<br>
>> for the international FOSS4G event? Should it cover regional<br>
>> conferences too? Should it also cover FOSS4G steams in other<br>
conferences?<br>
>><br>
>> Who thinks this idea is important enough that you would like<br>
to help<br>
>> write sections of the Cookbook, or help with editing?<br>
>><br>
>> What format should we use to write the Cookbook? Maybe a wiki?<br>
>><br>
>> I'm interested to help push this idea forward if we as a<br>
community<br>
>> think that there will be value in such a collaboratively<br>
edited document.<br>
>><br>
>> If you have an interest, please respond on the OSGeo<br>
conference_dev<br>
>> email list (rather than OSGeo Discuss)<br>
>><br>
>> [1]<br>
>> <a href="http://cameronshorter.blogspot.com.au/2012/08/analysing-" target="_blank">http://cameronshorter.<u></u>blogspot.com.au/2012/08/<u></u>analysing-</a><br>
downfall-of-f<br>
>> oss4g-2012.html<br>
>><br>
>> [2] <a href="http://wiki.osgeo.org/wiki/FOSS4G_Cookbook" target="_blank">http://wiki.osgeo.org/wiki/<u></u>FOSS4G_Cookbook</a><br>
>> [3] <a href="http://lists.osgeo.org/mailman/listinfo/conference_dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/conference_<u></u>dev</a><br>
>><br>
><br>
> ______________________________<u></u>_________________<br>
> Discuss mailing list<br>
> <a href="mailto:Discuss@lists.osgeo.org" target="_blank">Discuss@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/discuss" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/discuss</a><br>
><br>
______________________________<u></u>_________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.osgeo.org" target="_blank">Discuss@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/discuss" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/discuss</a><br>
</blockquote></blockquote>
<br>
______________________________<u></u>_________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.osgeo.org" target="_blank">Discuss@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/discuss" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/discuss</a><br>
</blockquote>
<br>
<br></div></div><div class="im HOEnZb">
-- <br>
Cameron Shorter<br>
Geospatial Solutions Manager<br>
Tel: <a href="tel:%2B61%20%280%292%208570%205050" value="+61285705050" target="_blank">+61 (0)2 8570 5050</a><br>
Mob: <a href="tel:%2B61%20%280%29419%20142%20254" value="+61419142254" target="_blank">+61 (0)419 142 254</a><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></div><div class="HOEnZb"><div class="h5">
______________________________<u></u>_________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.osgeo.org" target="_blank">Discuss@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/discuss" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/discuss</a><br>
</div></div></blockquote></div><br></div>