+1 from me<br><br>And I’m keen to have some role on the next committee for sure 🙂<br><br>Let’s see those proposals!<br><div class="gmail_quote"><div dir="ltr">On Fri, 2 Nov 2018 at 2:37 pm, adam steer <<a href="mailto:adam.d.steer@gmail.com">adam.d.steer@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>Hi all<div dir="auto"><br></div><div dir="auto">+1 to Cameron's suggestions.</div><div dir="auto"><br></div><div dir="auto">...and also pre-volunteering to join an organising committee if they're happy to have me :)</div><div dir="auto"><br></div><div dir="auto">Only one request: please keep letters of intent absolutely on point, the committee are flat out!<br><br>Cheers</div><div dir="auto"><br></div><div dir="auto">Adam<br><br><br><div data-smartmail="gmail_signature" dir="auto">--<br>Dr. Adam Steer<br><a href="https://www.researchgate.net/profile/Adam_Steer" target="_blank">https://www.researchgate.net/profile/Adam_Steer</a><br><a href="http://au.linkedin.com/in/adamsteer" target="_blank">http://au.linkedin.com/in/adamsteer</a><br><a href="http://orcid.org/0000-0003-0046-7236" target="_blank">http://orcid.org/0000-0003-0046-7236</a><br>+61 427 091 712<br>skype: adam.d.steer<br>tweet: @adamdsteer</div></div></div></div><div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr">On Fri., 2 Nov. 2018, 14:18 Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>And here are my thoughts:</p>
<p>+1 for running FOSS4G-Oceania in 2019<br>
</p>
<p>I think there are two core factors which are setting up FOSS4G
Oceania to be successful this year:<br>
1. The University of Melbourne has provided a free venue, which
has significantly minimised attendance costs.<br>
2. We have had a large, very engaged organising committee, led by
a very active chair (thanks John).</p>
<p>In selecting a future venue, I'd be hopeful that these two
criteria are considered.</p>
<p>With regards to who should decide:<br>
* We haven't defined a decision making process or decided decision
makers for selecting future event venues.<br>
* But, I've seen our existing FOSS4G committee to be committed,
ethical, and competent. I'd suggest selecting our next venue
should be delegated to this committee, and we can refine the
process for future years.<br>
</p>
<p>I'd suggest that people wishing to propose a venue for foss4g
2019 discuss their ideas on this email list, paying particular
attention to the two points above.</p>
<p>I'd think an initial proposal should be of similar depth to the
international FOSS4G "Letter of Intent" stage, with the FOSS4G
international list of questions being used as a something to
consider.
<a class="m_4677025392973798272m_1335306944066045225moz-txt-link-freetext" href="https://wiki.osgeo.org/wiki/FOSS4G_2019_Bid_Process#Letters_of_Intent" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/FOSS4G_2019_Bid_Process#Letters_of_Intent</a><br>
</p>
<p><i>“Letters of Intent" are limited to a maximum of two (2) pages,
and should answer the following questions:</i><i><br>
</i><i>1. Who is your conference chair?</i><i><br>
</i><i>2. Who else is on your local organizing committee (LOC)?</i><i><br>
</i><i>3. What is the experience of your committee members with
similar events?</i><i><br>
</i><i>4. What is your proposed venue? (include access to
Internet, room sizes, maximum attendees)</i><i><br>
</i><i>5. What are your provisional dates for the conference?</i><i><br>
</i><i>6. Early thoughts on prices of conference attendance?
(indicative estimates)</i><i><br>
</i><i>7. What is the price range and general location of your
proposed accommodations and how is the</i><i><br>
</i><i>price-level in your area in general (e.g. costs for food,
drinks)</i><i><br>
</i><i>8. Are you partnering with other local organizations?</i><i><br>
</i><i>9. What makes FOSS4G in your proposed location and with
your team compelling?</i><br>
</p>
<p><br>
</p>
<br>
<div class="m_4677025392973798272m_1335306944066045225moz-cite-prefix">On 2/11/18 2:14 pm, Cameron Shorter
wrote:<br>
</div>
<blockquote type="cite">Our
FOSS4G-Oceania conference is shaping up to be much bigger than
originally planned. We have attracted significantly more sponsors,
attendees, and committee members than originally anticipated.
<br>
<br>
So the question raised at today's committee meeting is:
<br>
<br>
* Should we hold this event again next year?
<br>
<br>
* If so, where should we hold it?
<br>
<br>
* And how should we go about deciding?"
<br>
<br>
It would be a bonus if we could announce next years FOSS4G-Oceania
event as we close this year, which doesn't leave much time. Within
this email thread I suggest we discuss these and related
questions.
<br>
<br>
</blockquote>
<br>
<pre class="m_4677025392973798272m_1335306944066045225moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</div>
_______________________________________________<br>
FOSS4G-Oceania mailing list<br>
<a href="mailto:FOSS4G-Oceania@lists.osgeo.org" rel="noreferrer" target="_blank">FOSS4G-Oceania@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/foss4g-oceania" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/foss4g-oceania</a><br>
</blockquote></div></div></div>
_______________________________________________<br>
FOSS4G-Oceania mailing list<br>
<a href="mailto:FOSS4G-Oceania@lists.osgeo.org" target="_blank">FOSS4G-Oceania@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/foss4g-oceania" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/foss4g-oceania</a><br>
</blockquote></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><br></div>Alex Leith<div>0419 189 050</div></div></div>