<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-AU" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB">Can we also check what is the accepted practice in the general FOSS4G series ( NA, Europe, global, etc)? This may give us arguments for one arrangement against another.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">My +1 for Adam’s solution still holds.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">M.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></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 <foss4g-oceania-bounces@lists.osgeo.org> on behalf of adam steer <adam.d.steer@gmail.com><br>
<b>Date: </b>Monday, 25 March 2019 at 9:08 am<br>
<b>To: </b>Cameron Shorter <cameron.shorter@gmail.com><br>
<b>Cc: </b>foss4g-oceania <foss4g-oceania@lists.osgeo.org><br>
<b>Subject: </b>Re: [FOSS4G-Oceania] process for sponsor-submitted talks at F4G SotM 2019<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Hi Cameron <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">‘should we have a sponsor pitch session’ is another motion / discussion. I personally don’t like these - and feel that the plenary intro / sponsor thanks spiel will point people in the direction of where to find them for more information.
In this case I feel tipping the balance consciously toward a ‘community feel’ as far as possible is the best approach.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Having said that, there’s a lot of conversation with the sponsorship team to have over how to operate this stuff for 2019. The programme is still very much vaporware.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I felt the balance people struck in talks (even from a few biggishcorporation folks) was about right in 2018; mostly aiming to educate with a bit of ‘heres the company I work for and what we do’.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">It’s a good point to raise, and we can certainly include that intention in the CfP.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Adam<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, 25 Mar 2019 at 06:20, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com">cameron.shorter@gmail.com</a>> wrote:<o:p></o:p></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>This is a delicate balance question.<o:p></o:p></p>
<p>We really appreciate sponsors as they enable us to attract community by keeping costs to attendees down, pay for travel grant programs, and cover the community day. We should say that ourselves. I think we should follow that with a 60 second pitch session
for big roller sponsors to pitch their company, and then refer back to their booth for more info. (That should be at the start of the conference within a plenary).<o:p></o:p></p>
<p>We should then state that our strong preference for talks (as per our selection criteria) is no sales pitches. Yes, you can say where you work, yes you can apply a very subtle reference back to you company, but that should be it. (Paul Ramsey is very good
at getting this balance right.)<o:p></o:p></p>
<p>+1, For all other talks, we should select based on existing merit criteria (and not on how much you pay).<o:p></o:p></p>
<p>Cameron<o:p></o:p></p>
<div>
<p class="MsoNormal">On 24/3/19 1:37 pm, adam steer wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">Hi all <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In our latest FOSS4G SotM 2019 committee meeting there was a short discussion about how to manage talks submitted by sponsors (minutes will come soon, the 2019 conference wiki page at
<a href="http://osgeo.org" target="_blank">
osgeo.org</a> is just being started)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In 2018, we decided that sponsor-submitted talks should go through the normal process - that is, there is no guaranteed talk slot for sponsors; and any talks submitted by sponsors need to go through the normal community review + committee
filter.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">On reflection, we failed to communicate this adequately to some sponsors, and this year will aim to do so in the prospectus. However, in an open-ended feedback survey, none of the sponsors who responded indicated that they would prefer
‘guaranteed content’.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Before we go ahead and set words in stone for 2019:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Do you think that we should stick to the 2018 model - meaning that sponsor-submitted talks should go through the normal review process; and there are no guaranteed talk slots for sponsors?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">+1 says ‘yes’; and that’s my personal vote/preference as programme coordinator.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Please vote, ask questions if you need more clarity, discuss - our next conference committee meeting is scheduled for early April; and we’d like to have a prospectus nearing ‘ready’ shortly after that.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks, and regards<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Adam<o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>FOSS4G-Oceania mailing list<o:p></o:p></pre>
<pre><a href="mailto:FOSS4G-Oceania@lists.osgeo.org" target="_blank">FOSS4G-Oceania@lists.osgeo.org</a><o:p></o:p></pre>
<pre><a href="https://lists.osgeo.org/mailman/listinfo/foss4g-oceania" target="_blank">https://lists.osgeo.org/mailman/listinfo/foss4g-oceania</a><o:p></o:p></pre>
</blockquote>
<pre>-- <o:p></o:p></pre>
<pre>Cameron Shorter<o:p></o:p></pre>
<pre>Technology Demystifier<o:p></o:p></pre>
<pre>Open Technologies and Geospatial Consultant<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>M +61 (0) 419 142 254<o:p></o:p></pre>
</div>
<p class="MsoNormal">_______________________________________________<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/mailman/listinfo/foss4g-oceania</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Dr. Adam Steer<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="http://spatialised.net" target="_blank">http://spatialised.net</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><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><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><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<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">tweet: @adamdsteer<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>