<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Rob,</p>
<p>Great to see you jump in on the conversation. For those who don't
know Rob already, he is one of the legends of Geospatial thought
leadership and has done a huge amount with Open Source. He has
also been a good friend of mine for close to 20 years.</p>
<p>Having said that: Rob, I accept your point of being too busy to
get deeply involved, but think that staff membership of the OGC
should not be used as an excuse to exclude being involved in Open
Source activities. <br>
</p>
<p>Cheers, Cameron<br>
</p>
<br>
<div class="moz-cite-prefix">On 12/12/17 7:35 am, Rob Atkinson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACfF9Lx_DhMXJWB3ToHZ_hcbPuirFgsXb7nUhZr3nUh5vP8rSA@mail.gmail.com">
<div dir="ltr"><br>
<div>Hi all,</div>
<div><br>
</div>
<div>belated introduction here - following this with interest.</div>
<div><br>
</div>
<div>I'm not in a position to be actively involved this time
round, for both workload and neutrality issues as I am a
part-time member of OGC staff, but I am also actively
developing open-source components for supporting Linked Data
views over spatio-temporal resources - and would like to run a
workshop on these matters come November. </div>
<div><br>
</div>
<div>I'm also keen to hear if there are any requirements from
the community for specific functionality or content to be
available via the emerging OGC knowledge infrastructure, we
will be building a Linked Data explorer for all the OGC
resources such as specifications, best practices, vocabularies
etc.</div>
<div><br>
</div>
<div>Rob Atkinson</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Sun, 10 Dec 2017 at 06:02 Cameron Shorter
<<a href="mailto:cameron.shorter@gmail.com"
moz-do-not-send="true">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>comments inline:<br>
</p>
</div>
<div text="#000000" bgcolor="#FFFFFF"> <br>
<div class="m_-2353685099510793993moz-cite-prefix">On
9/12/17 6:40 pm, John Bryant wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi all,<br>
</div>
<div><br>
</div>
<div>By way of an update on things I'm aware of, a few
items of note:</div>
<div>
<ul>
<li>David Dean is currently seeking support from
OSM Foundation for use of the SOTM trademark.<br>
</li>
<li>A wiki page has been created at <a
href="https://wiki.osgeo.org/wiki/FOSS4G-SOTM-Oceania"
target="_blank" moz-do-not-send="true">https://wiki.osgeo.org/wiki/FOSS4G-SOTM-Oceania</a>
(but it's pretty sparse so far). Please feel
free to edit this page and add content!<br>
</li>
</ul>
</div>
</div>
</blockquote>
</div>
<div text="#000000" bgcolor="#FFFFFF"> Cameron: I suggest
that you use this page as an index/jump page to other
information. <br>
</div>
<div text="#000000" bgcolor="#FFFFFF">
<blockquote type="cite">
<div dir="ltr">
<div>
<ul>
<li>Daniel Silk has a colleague who may be
interested in attempting a logo. Likely others
will want to do this as well. It will probably
pay to be proactive, and create a logo brief...
anyone wish to take a lead on this (Daniel
perhaps?)?<br>
</li>
</ul>
</div>
</div>
</blockquote>
</div>
<div text="#000000" bgcolor="#FFFFFF"> Cameron: Tips on logo
creation here: <a
class="m_-2353685099510793993moz-txt-link-freetext"
href="https://wiki.osgeo.org/wiki/FOSS4G_Handbook#Logo"
target="_blank" moz-do-not-send="true">https://wiki.osgeo.org/wiki/FOSS4G_Handbook#Logo</a></div>
<div text="#000000" bgcolor="#FFFFFF"><br>
<blockquote type="cite">
<div dir="ltr">
<div>
<ul>
<li>We've already started receiving suggestions
for venues, and have been approached by the
Melbourne Convention Bureau. We need to make
early progress on our choice of venue, as it's
potentially a major component of the budget and
we need to understand our costs ASAP.<br>
</li>
</ul>
</div>
<div>We agreed at last week's meeting that we'd aim to
meet again around the 18th (Monday week). Before
this meeting, there are some things we should/could
tackle:<br>
</div>
<div>
<ul>
<li><b>Finalise minutes.</b> The <a
href="https://docs.google.com/document/d/1wBys9xsDxm7rFFBiQFqjQxyAhn5QspNqbcgNYjArcks"
target="_blank" moz-do-not-send="true">Google
Doc</a> is a good place to edit minutes, but I
think we need a more permanent record of
decisions and meeting notes. Can everyone who
attending this meeting please review the
minutes, and discuss/comment/edit as needed, by
this coming Monday 11th? Once finalised, we can
then grab a static copy of the minutes and post
them on the wiki.<br>
</li>
</ul>
</div>
</div>
</blockquote>
</div>
<div text="#000000" bgcolor="#FFFFFF"> Cameron: I suggest
that you minimise the work you create for yourself. Re
keeping records - you typically have chat logs or email
threads which are archived for you. You might want to
summarise key decisions only in a minutes page. <br>
<br>
I've added to the comments in the Google Doc.</div>
<div text="#000000" bgcolor="#FFFFFF"><br>
<blockquote type="cite">
<div dir="ltr">
<div>
<ul>
<li><b>Discuss conference length</b>. At the last
meeting, there was some discussion about whether
the conference (exclusive of workshops and code
sprint/hackathon/mapathon) should be 1 day or 2
(for a total event length of 3 or 4 days). This
wasn't resolved then, but again, as a major
factor in determining the shape of the event
(and thus cost, logistics, venue etc), we need
to come to terms with this. I suggest we discuss
by mailing list leading up to the meeting, and
try to make a decision at the meeting.</li>
<li><b>Discuss dates</b>. Currently, this stands
at 'some time in November(ish)'. There is a <a
href="https://docs.google.com/spreadsheets/d/1-bueIooYwUH6q8PQIH0J0Ou_KOpWhmJQl9Qa690z_Ao"
target="_blank" moz-do-not-send="true">document
in the Google Drive</a> with a number of other
relevant events on the calendar, and a <a
href="https://docs.google.com/spreadsheets/d/1-bueIooYwUH6q8PQIH0J0Ou_KOpWhmJQl9Qa690z_Ao/edit#gid=1314617119"
target="_blank" moz-do-not-send="true">sheet
to help us</a> narrow down dates. Having a set
date will allow us to begin promoting the event
in earnest, and get people to save the date in
their own calendars. I suggest we review &
discuss these dates, and attempt to choose a
week either at the meeting, or beforehand.</li>
<li><b>Review & discuss roles</b>. There is a
preliminary list of roles (or committees)
identified in the <a
href="https://docs.google.com/document/d/1YPF3fOsClnYrMXe68_01eF2tc8NwZlDxliWIkWby014/edit#"
target="_blank" moz-do-not-send="true">Planning
Document</a>, this would be a good time for
folks to contribute to discussion around how we
break up & share the work. Some of these
roles can be filled by one person, some might
require a group to take on the relevant tasks.
If you have thoughts around this, please chime
in. And by all means put your hands up for stuff
you want to take on!</li>
</ul>
<div><br>
</div>
</div>
<div>Let's pick a time for the next meeting, Doodle
poll here: <a
href="https://doodle.com/poll/c8tfkxtcqdpw8545"
target="_blank" moz-do-not-send="true">https://doodle.com/poll/c8tfkxtcqdpw8545</a>.
We did say the 18th, but I've also added the 19th in
as an option in case it works better for people.
I'll tally up the votes at the end of the day on
Thursday.</div>
<div><br>
</div>
<div>Suggested agenda (please add items that are on
your mind!):</div>
<div>
<ul>
<li>Decide on conference length</li>
<li>Decide on dates</li>
<li>Discuss roles, in the context of early
priorities (see <a
href="https://docs.google.com/spreadsheets/d/1mU6beJA7NteqCNQ6iW7LpCL-06lwwxnESnvcRAY6nT8/edit#gid=0"
target="_blank" moz-do-not-send="true">timeline</a>,
and please feel free to edit it)</li>
<li>...</li>
</ul>
</div>
<div>It might be an idea to open new threads on this
mailing list for specific discussions. Looking
forward to hearing what's on people's minds!</div>
<div><br>
</div>
<div>Cheers</div>
<div>John</div>
<div><br>
</div>
</div>
<br>
<fieldset
class="m_-2353685099510793993mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
Aust-NZ mailing list
<a class="m_-2353685099510793993moz-txt-link-abbreviated" href="mailto:Aust-NZ@lists.osgeo.org" target="_blank" moz-do-not-send="true">Aust-NZ@lists.osgeo.org</a>
<a class="m_-2353685099510793993moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/aust-nz" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/aust-nz</a></pre>
</blockquote>
<br>
</div>
<div text="#000000" bgcolor="#FFFFFF">
<pre class="m_-2353685099510793993moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier, Learnosity
Open Technologies Consultant
M <a href="tel:0419%20142%20254" value="+61419142254" target="_blank" moz-do-not-send="true">+61 (0) 419 142 254</a></pre>
</div>
_______________________________________________<br>
Aust-NZ mailing list<br>
<a href="mailto:Aust-NZ@lists.osgeo.org" target="_blank"
moz-do-not-send="true">Aust-NZ@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/aust-nz"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/aust-nz</a></blockquote>
</div>
</div>
</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>