<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
+1, great idea<BR>
<BR>
even with lessons learned on the wiki, I reckon there has been too much reinventing of the wheel.<BR>
<BR>
<BR>
On Fri, 2011-10-14 at 21:52 +1100, Cameron Shorter wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
I suggest that we, the conference committee and interested people,
should organically start building a FOSS4G Cookbook.
The Cookbook should cover all the aspects of putting on a FOSS4G
conference, including such things as:
* Schedule coming up to the conference
* Budget
* Program
* Web Site
* Catering
* Venue selection
Initially much of the content for this cookbook can be drawn directly
from Lessons Learned from previous years. As more events are run, I'd
expect ideas to evolve and the Cookbook to grow with it.
I see two key advantages of such a Cookbook:
1. Access to such information will make it much easier for someone to
put on a FOSS4G conference
2. The Cookbook can be used as a baseline to guide deciding whether a
conference may make use of the FOSS4G brand. This will help maintain the
quality associated with the FOSS4G brand.
Do others see value in building such a document?
I'm assuming we should build the Cookbook as a wiki, but am happy to
hear suggestions for other collaborative tools.
If there is sufficient interest, I'll build a skeleton of the Cookbook,
and invite others to contribute content.
</PRE>
</BLOCKQUOTE>
<BR>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<PRE>
--
Gavin Fleming
t: 0218620670
c: 0845965680
f: 0866164820
Paarl
South Africa
18°59'18.8"E 33°44'40.2"S
</PRE>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>