[OSGeo-Conf] FOSS4G Cookbook writing guide

Peter Batty peter at ebatty.com
Tue Sep 11 09:16:48 PDT 2012

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.

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).

But some items are not really negotiable for the global event, a few
examples that spring to mind are:
- The logo has to include the FOSS4G ribbon, this is not negotiable
- You need to allow a time slot on the agenda for the OSGeo AGM (though
this is not formally part of the conference)
- You need to allow time for the Sol Katz award, traditionally in the
closing session
... etc etc (I have more items for this list if I dig back through notes /
lessons learned)

There's a typical timeline that we adapted from Barcelona (and I imagine
they took from previous years) which is at

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).

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?


On Mon, Sep 10, 2012 at 4:15 PM, Dave Patton <davep at confluence.org> wrote:

> On 2012/09/10 1:34 PM, Cameron Shorter wrote:
>> Jachym, Maybe you like to start putting together Cookbook headings?
>> It need not be perfect on the first pass, but it will be useful to
>> have a starting point which we can talk to as a group. (Feel free to
>> remove the prior headings I had in place) I suspect that there would
>> be other Conference Cookbooks on the web which we could make use of.
>> It would be well worth doing some research to see if if is worth
>> basing our cookbook on some of them.
> Just a 'comment from the sidelines' - various people have mentioned
> that the "Cookbook" needs to be a 'guide', and that it can't be a
> 'recipe' for how to run a conference, given all the variations involved.
> However, the term "cookbook" does in some ways imply
> "a set of recipes".
> What about using the term "Body of Knowledge"?
> http://en.wikipedia.org/wiki/**Body_of_Knowledge<http://en.wikipedia.org/wiki/Body_of_Knowledge>
> --
> Dave Patton
> Victoria, B.C.
> Degree Confluence Project:
> Canadian Coordinator
> Technical Coordinator
> http://www.confluence.org/
> Personal website:
> http://members.shaw.ca/**davepatton/ <http://members.shaw.ca/davepatton/>
> ______________________________**_________________
> Conference_dev mailing list
> Conference_dev at lists.osgeo.org
> http://lists.osgeo.org/**mailman/listinfo/conference_**dev<http://lists.osgeo.org/mailman/listinfo/conference_dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/conference_dev/attachments/20120911/1614275f/attachment.html>

More information about the Conference_dev mailing list