<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 08/09/12 05:05, Jachym Cepicky
wrote:<br>
</div>
<blockquote cite="mid:504A458F.8050707@gmail.com" type="cite">
<pre wrap="">
Dne 7.9.2012 14:58, Jo Cook napsal(a):
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">> </span>Dear All,
<span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">></span>[ .... ]
<span class="moz-txt-citetags">> </span>It seems as if the best
<span class="moz-txt-citetags">> </span>approach might be to put a basic structure up on the wiki, then we can all
<span class="moz-txt-citetags">> </span>add to it as we think of something appropriate. How does that sound?
</pre>
</blockquote>
<pre wrap="">
I would fully agree with that -
J
</pre>
</blockquote>
<br>
Agreed. Lets build as we go.<br>
I do acknowledge the extra load that the UK LOC will have running
FOSS4G 2013, and I'm sure that the external offers of help from
Jachym, Peter and others will be key to spreading the load and
making the cookbook successful.<br>
I would also encourage the FOSS4G 2013 committee to keep a running
Lessons Learned wiki as well (which is separate to the Cookbook). It
is easy to write a Lesson Learned as you experience it, but much
harder to go back and try to remember all the details.<br>
<br>
As David and Peter note:<br>
I think the success and also the challenge for the Cookbook will be
to keep it concise.<br>
This means we should reference details from prior Lessons Learned,
but not include the details.<br>
It also means we will need to be ruthless in our continuous editing
of the document, ensuring that we remove old content. (This is a
recipe for writers block, as authors often are reluctant to cut
apart or remove a prior author's efforts).<br>
<br>
<br>
<div class="moz-cite-prefix">On 07/09/12 23:30, David William Bitner
wrote:<br>
</div>
<blockquote
cite="mid:CAEqvsZvuu3T6BAhpObZi=qmn4OWS_6jORED0sBEZgPWk-OnU=A@mail.gmail.com"
type="cite">
<div>I think you are right on target with what I would like to
see. A voluminous guide with samples of this and that from every
conference would get very hard to navigate. A checklist and easy
things like that (having the template budget started in Victoria
was great for us) would be a wonderful tool to have.</div>
<div><br>
</div>
<div>To be honest a lot of the talk about archiving conversations
and drafts of every document or design that goes through the LOC
makes me very hesitant. I certainly agree to tracking those
things, but as a volunteer, that is certainly not at the top of
my priorities and if I can't find another volunteer who can help
with that (which is not exactly the kind of task that others
usually stand up to take on) then it is likely not to get done
at all since that kind of thing tends to fall on the lap of the
person who is overstretching anyway. If we can focus the things
that we try to pull together centrally to the things that really
are more broadly useful to others we might be able to have
better follow through.<br>
<br>
David<br>
<br>
<div class="gmail_quote">On Fri, Sep 7, 2012 at 8:20 AM, Peter
Batty <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:peter@ebatty.com" target="_blank">peter@ebatty.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
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>
</blockquote>
</div>
</div>
</blockquote>
<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>