<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Peter,<br>
Good thoughts. I've updated a "Relevance" section to the writing
guidelines [1]. I suggest people start writing a section or two
and we can test what sort of format we should be using.<br>
<br>
Relevance<br>
International FOSS4G: [Mandatory, Recommended, Optional, Not
Relevant] <br>
Regional FOSS4G: [Mandatory, Recommended, Optional, Not
Relevant] <br>
FOSS4G stream / Local Event: [Mandatory, Recommended,
Optional, Not Relevant] <br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/FOSS4G_Cookbook#Section_Writing_Guide">http://wiki.osgeo.org/wiki/FOSS4G_Cookbook#Section_Writing_Guide</a><br>
<br>
On 12/09/12 02:16, Peter Batty wrote:<br>
</div>
<blockquote
cite="mid:CAPJXf1Wfvc_PrA7JQt7M7VJVCF0XX47ZRY=Qc=gib110NKgpGg@mail.gmail.com"
type="cite">One thing I think we need to somehow distinguish is
"general conference advice" that (may) apply to any event, small
or large, from some items that are more specific to the annual
global conference.
<div><br>
</div>
<div>I think that for the global conference what we are after is
something like a recipe - but one that people can choose to vary
(in some aspects).</div>
<div><br>
</div>
<div>But some items are not really negotiable for the global
event, a few examples that spring to mind are:</div>
<div>- The logo has to include the FOSS4G ribbon, this is not
negotiable</div>
<div>- You need to allow a time slot on the agenda for the OSGeo
AGM (though this is not formally part of the conference)</div>
<div>- You need to allow time for the Sol Katz award,
traditionally in the closing session</div>
<div>... etc etc (I have more items for this list if I dig back
through notes / lessons learned)</div>
<div><br>
</div>
<div>There's a typical timeline that we adapted from Barcelona
(and I imagine they took from previous years) which is at <a
moz-do-not-send="true"
href="http://2011.foss4g.org/content/timeline">http://2011.foss4g.org/content/timeline</a></div>
<div><br>
</div>
<div>I think a version of this with some more details added in is
a good piece of the "cookbook" approach to the annual event
(again with flexibility for people to adapt, but in most cases
people are going to follow this more or less I imagine).</div>
<div><br>
</div>
<div>So I think we need to decide how to structure things with
this in mind. Do we have two separate sections, one that's a
cookbook for the annual event and one for smaller events? Or do
we try to make it mainly common information, and have the
timeline and other global conference specific items in their own
smaller section? Or something else?</div>
<div><br>
</div>
<div>Cheers,</div>
<div> Peter.</div>
<br>
<div class="gmail_quote">On Mon, Sep 10, 2012 at 4:15 PM, Dave
Patton <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:davep@confluence.org" target="_blank">davep@confluence.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 2012/09/10 1:34 PM, Cameron Shorter wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Jachym, Maybe you like to start putting together Cookbook
headings?<br>
It need not be perfect on the first pass, but it will be
useful to<br>
have a starting point which we can talk to as a group.
(Feel free to<br>
remove the prior headings I had in place) I suspect that
there would<br>
be other Conference Cookbooks on the web which we could
make use of.<br>
It would be well worth doing some research to see if if is
worth<br>
basing our cookbook on some of them.<br>
</blockquote>
<br>
</div>
Just a 'comment from the sidelines' - various people have
mentioned<br>
that the "Cookbook" needs to be a 'guide', and that it can't
be a<br>
'recipe' for how to run a conference, given all the variations
involved.<br>
<br>
However, the term "cookbook" does in some ways imply<br>
"a set of recipes".<br>
<br>
What about using the term "Body of Knowledge"?<br>
<a moz-do-not-send="true"
href="http://en.wikipedia.org/wiki/Body_of_Knowledge"
target="_blank">http://en.wikipedia.org/wiki/Body_of_Knowledge</a><span
class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Dave Patton<br>
Victoria, B.C.<br>
<br>
Degree Confluence Project:<br>
Canadian Coordinator<br>
Technical Coordinator<br>
<a moz-do-not-send="true"
href="http://www.confluence.org/" target="_blank">http://www.confluence.org/</a><br>
<br>
Personal website:<br>
<a moz-do-not-send="true"
href="http://members.shaw.ca/davepatton/"
target="_blank">http://members.shaw.ca/davepatton/</a></font></span>
<div class="HOEnZb">
<div class="h5"><br>
_______________________________________________<br>
Conference_dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:Conference_dev@lists.osgeo.org"
target="_blank">Conference_dev@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/conference_dev"
target="_blank">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Conference_dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Geospatial Solutions Manager
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254
Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
<a class="moz-txt-link-freetext" href="http://www.lisasoft.com">http://www.lisasoft.com</a>
</pre>
</body>
</html>