<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>My thoughts on the first regional FOSS4G conference (in a long
while) is that the primary goal is to make sure it is successful.
With FOSS4G 2009 we over-estimated the number of attendees by
close to a factor of 2. There were multiple reasons for this [1],
but a key lesson was to make sure the conference goals are
achievable and sustainable.</p>
<p>As such, I'd err on selecting shorter, lower cost, lower barrier
to entry (which results in being more selective of presentations
and providing less higher quality presentations rather than more).
I'd prefer to be sold out rather than having a conference full of
empty seats.</p>
<p>Lets see how many people we can attract into the conference in
the first year before over-committing. We can build up numbers in
following years.</p>
<p>Cheers, Cameron<br>
</p>
[1] <a class="moz-txt-link-freetext" href="https://wiki.osgeo.org/wiki/FOSS4G_2009_Lessons_Learned">https://wiki.osgeo.org/wiki/FOSS4G_2009_Lessons_Learned</a><br>
<br>
<div class="moz-cite-prefix">On 13/12/17 8:24 am, John Bryant wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHY5hn-n+y7qv9DKtrdZy6=AxNUctLsrbah+8mbu44s-4knoYg@mail.gmail.com">
<div dir="ltr">Hi all,
<div><br>
</div>
<div>At our upcoming committee meeting, we'll hopefully come to
some kind of decision on:</div>
<div>
<ul>
<li>conference length (for the 'conference' component,
exclusive of pre-conf workshops and post-conf code
sprint/hackathon/mapathon)</li>
<li>conference dates</li>
</ul>
<div>Discussion around length, so far, has focused on 2
options, either one day or two (for a total event length of
either 3 or 4 days).</div>
</div>
<div><br>
</div>
<div>My personal preference would be to see two days for the
conference proper, as I think with both FOSS4G and SOTM
components, and a broad region (Oceania), there is the
potential for a lot of content... I think one day wouldn't be
enough time to cover it without spreading across too many
competing streams/sessions.</div>
<div><br>
</div>
<div>One argument for one day is that it would be less of an
organisational burden, which is a fair point.</div>
<div><br>
</div>
<div>Surely there are other arguments for one or the other
option, or perhaps even additional options that haven't come
up... it would be great to have some input on this mailing
list before we meet next week to make a decision.</div>
<div><br>
</div>
<div>Thoughts?</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Aust-NZ mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Aust-NZ@lists.osgeo.org">Aust-NZ@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/aust-nz">https://lists.osgeo.org/mailman/listinfo/aust-nz</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier, Learnosity
Open Technologies Consultant
M +61 (0) 419 142 254</pre>
</body>
</html>