<div dir="ltr">A bit late to the party, but another +1 for Adam's point on choosing a panellist from existing attendees.<div><br><div>I'm not actually sure what the panel topic of conversation is. It would be good to narrow down what we want to address with the panel. <a href="https://docs.google.com/document/d/1wz8tJyVhmThjEvpwQ2htt8n1NwmTBJ5bnu827DO0GfU/edit">I know it's in the works</a>, but a general conversation on diversity would be very dull for me. I would rather a specific topic. Diversity could be a core element of these topics.</div><div><br></div><div>Examples:<br></div><div><ul><li><b>Fostering the next generation of spatial professionals</b> - This could include questions on all sorts of diversity and trends that current professionals have noticed.</li><li><b>Emerging applications of spatial - </b>Not the best name, but the idea would be to choose a diverse group of people who have been applying their expertise in new ways/places. Projects in remote locations throughout Oceania. Applications that address a marginalised group. Session would hopefully get others in the room thinking about the application of their skills in new ways.</li><li><b>The history of OpenStreetMap in Australia </b>- Might be interesting to take a look back an OpenStreetMap in Australia and get longtime contributors to discuss the way data, community and methods have been changing. This could include a few insights from companies that have been changing the way contributions to OSM take place. E.g. Microsoft. Not a direct connection to diversity, but we could look at the kind of people who have been contributing and ask questions about how the objects that have been mapped reflect that. Alyssa Wright has spoken on this topic.</li></ul><div>Agree with the others that a panellist makes sense after the topic has been discussed. Deanna may very well have registered by then.</div></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 23 July 2018 at 10:56, Martin Tomko <span dir="ltr"><<a href="mailto:tomkom@unimelb.edu.au" target="_blank">tomkom@unimelb.edu.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-AU" link="blue" vlink="purple">
<div class="m_1448753836269176410WordSection1">
<p class="MsoNormal"><span lang="EN-GB">+1 with Adam.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">+, we do not have the topic yet – I would not automatically assume that keynotes are the best to chair or sit on the panel. Keynotes are ( byt definition )often tabngentially outside the community or domain, to provide
a perspective. For some panels this may be ok, but for others not.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">I would reach to Deanna ( Alex?) and invite her to participate, support and come to the event. If she registers, we could ask her for sitting on the panel. Chairing the panel is a mundane, (but hard) job. I would argue
you get more value from the panellist if they do not chair it, but participate. The chair of the panel should be an organiser of the conference or someone well established IN the community already, at least that is more usual experience.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">M.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">FOSS4G-Oceania <<a href="mailto:foss4g-oceania-bounces@lists.osgeo.org" target="_blank">foss4g-oceania-bounces@lists.<wbr>osgeo.org</a>> on behalf of adam steer <<a href="mailto:adam.d.steer@gmail.com" target="_blank">adam.d.steer@gmail.com</a>><br>
<b>Date: </b>Monday, 23 July 2018 at 10:38 am<br>
<b>To: </b>Alex Leith <<a href="mailto:alexgleith@gmail.com" target="_blank">alexgleith@gmail.com</a>><br>
<b>Cc: </b>"<a href="mailto:foss4g-oceania@lists.osgeo.org" target="_blank">foss4g-oceania@lists.osgeo.<wbr>org</a>" <<a href="mailto:foss4g-oceania@lists.osgeo.org" target="_blank">foss4g-oceania@lists.osgeo.<wbr>org</a>><br>
<b>Subject: </b>Re: [FOSS4G-Oceania] Plenary Panel Session<u></u><u></u></span></p>
</div><div><div class="h5">
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Hi Alex, all <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I strongly suggest that Deanna is invited to attend this event and listen in; and if she chooses to engage, then we can reassess how we engage next year. I don’t doubt that she has a wealth of experience and knowledge; and as CEO of SIBA
she has an excellent platform from which to influence the spatial industry.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">However - I also see a deep set of experience, knowledge and engagement on this committee; and in the people who have already signed up for the event. For every person we cherrypick/parachute in, we remove an opportunity for one of those
established community members and drivers to stand in the spotlight.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I’d go as far as to argue that keynotes have the opportunity to have their say in their talks - and panels should selected from attendees. Perhaps keynotes could chair sessions? …and would anyone on this committee group say no to an invitation
to sit on a panel and contribute to a discussion? Probably not...<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<div>
<p class="MsoNormal">Getting to be more like my $2.50 rather than $0.02… happy to hear other ideas.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Mon, 23 Jul 2018 at 06:43, Alex Leith <<a href="mailto:alexgleith@gmail.com" target="_blank">alexgleith@gmail.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">Hi All <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I agree around panelists, but this suggestion is specifically for the chair.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Panelists will likely be formed partly of keynotes, but some others too (for example, Cameron has said that he would be interested in being on a diversity panel).<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Anyhow, seems that the consensus is that we shouldn't invite a panel chair, we should pick one from attendees. I do disagree with this, in this case. Here is an opportunity to bring someone along from the broader community, in this case,
someone leading the spatial business community, and she will bring with her some diversity of opinion, and some deep insights. It is quite likely that she would register for the event, too, we just can't be sure about that!<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Cheers,<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Sun, 22 Jul 2018 at 22:07 Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p>+1 Lets first look for panelist from attendees. I'm confident we will have plenty to choose from. (We have good candidates within the our conference committee).<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On 22/7/18 9:18 pm, adam steer wrote:<u></u><u></u></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">dang, I missed that one. I think I was in the swiss mountains not caring about anything electronic.
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">We don’t offer one day, or one session registrations (with the exception of workshops). We’re expecting general community members to turn up, we should expect that people we shine the spotlight on (as panelists, chairs, speakers, plenaries,
keynotes) to turn up as well. Otherwise it’s a crappy message.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Are we afraid that we won’t fill a program? Are we worried that there is not enough expertise in the community that *does* turn up?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I’m not.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">…and +1 to Martin’s thoughts.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">:D<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Sun, 22 Jul 2018 at 21:07, John Bryant <<a href="mailto:johnwbryant@gmail.com" target="_blank">johnwbryant@gmail.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">Good point. I agree this is 'for the community, by the community' and we should aim in that direction.
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">But recall that we did have an email discussion about non-attending speakers (<a href="http://osgeo-org.1560.x6.nabble.com/Conference-Presenters-and-their-Attendance-td5369372.html" target="_blank">email thread: <i>Conference Presenters
and their Attendance, </i>27 June</a>), where this was suggested as a way to mitigate concerns around speakers not getting a discount:
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><i><span style="font-size:12.0pt;background:white">“We are aiming for an engaging and participatory conference, with minimal distinction between presenters and attendees. While we really appreciate all our presenters and would love to provide
them with a free ticket, we have opted instead to try and keep registration prices low and are asking presenters to purchase a registration. If that is not possible for a presenter, they may attend free of charge for the session they are presenting in, and
the break immediately afterwards.”</span></i> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I very much agree that the ideal is to have speakers attend, and for attendees to speak. But for those that can't/won't, we've made this accommodation. I'm supposing that this will apply to a very small number of people, in any case.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">So the question at hand is - do we apply this principle to a panel chair? Or do we aim for a higher standard for this level of participation?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
<p class="MsoNormal">______________________________<wbr>_________________<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" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/foss4g-<wbr>oceania</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">Adam Steer<br>
<a href="https://www.researchgate.net/profile/Adam_Steer" target="_blank">https://www.researchgate.net/<wbr>profile/Adam_Steer</a><br>
<a href="http://au.linkedin.com/in/adamsteer" target="_blank">http://au.linkedin.com/in/<wbr>adamsteer</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="http://orcid.org/0000-0003-0046-7236" target="_blank">http://orcid.org/0000-0003-<wbr>0046-7236</a><br>
<a href="tel:+61%20427%20091%20712" target="_blank">+61 427 091 712</a><br>
skype: adam.d.steer<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">tweet: @adamdsteer<u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br>
<u></u><u></u></p>
<pre>______________________________<wbr>_________________<u></u><u></u></pre>
<pre>FOSS4G-Oceania mailing list<u></u><u></u></pre>
<pre><a href="mailto:FOSS4G-Oceania@lists.osgeo.org" target="_blank">FOSS4G-Oceania@lists.osgeo.org</a><u></u><u></u></pre>
<pre><a href="https://lists.osgeo.org/mailman/listinfo/foss4g-oceania" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/foss4g-<wbr>oceania</a><u></u><u></u></pre>
</blockquote>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<pre>-- <u></u><u></u></pre>
<pre>Cameron Shorter<u></u><u></u></pre>
<pre>Technology Demystifier<u></u><u></u></pre>
<pre>Open Technologies and Geospatial Consultant<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>M <a href="tel:+61%20419%20142%20254" target="_blank">+61 (0) 419 142 254</a><u></u><u></u></pre>
</div>
<p class="MsoNormal">______________________________<wbr>_________________<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" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/foss4g-<wbr>oceania</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">Alex Leith <u></u><u></u></p>
<div>
<p class="MsoNormal">0419 189 050<u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal">______________________________<wbr>_________________<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" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/foss4g-<wbr>oceania</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">Adam Steer<br>
<a href="https://www.researchgate.net/profile/Adam_Steer" target="_blank">https://www.researchgate.net/<wbr>profile/Adam_Steer</a><br>
<a href="http://au.linkedin.com/in/adamsteer" target="_blank">http://au.linkedin.com/in/<wbr>adamsteer</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="http://orcid.org/0000-0003-0046-7236" target="_blank">http://orcid.org/0000-0003-<wbr>0046-7236</a><br>
+61 427 091 712<br>
skype: adam.d.steer<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">tweet: @adamdsteer<u></u><u></u></p>
</div>
</div>
</div>
</div></div></div>
</div>
<br>______________________________<wbr>_________________<br>
FOSS4G-Oceania mailing list<br>
<a href="mailto:FOSS4G-Oceania@lists.osgeo.org">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/<wbr>mailman/listinfo/foss4g-<wbr>oceania</a><br>
<br></blockquote></div><br></div>