<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Michael,</p>
<p>Sorry for the delayed response. You have done some really good
work cleaning up these metrics. I haven't got any suggestions of
improvement to note. The old metrics page has been showing its age
and you have made it easier to maintain long term. Well done! </p>
<p>I have to confess that I haven't been giving the metrics page the
love it deserves over the last few years, and with a my change of
job that is not likely to change. So it is great to see you pick
up the ball and take these metrics to the next level.</p>
<p>I think that your metrics should become the point of truth from
now on, and move the original one I started into a archive status.
I'd be interested to hear your thoughts on how we do this. Maybe:</p>
<p>1. Trawl the web for references to the old metrics page and
update to point at your new page?</p>
<p>2. Or, keep the URL of the old page, move your content into the
old URL, and copy out the old content into an archived page.</p>
<p>Warm regards, Cameron<br>
</p>
<br>
<div class="moz-cite-prefix">On 22/1/18 4:53 am, Michael Terner
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAEFvZu7cvZZJfNL0ehk=ESqHYi8zJ5PzKeQztSnFAns=f8WK6Q@mail.gmail.com">
<div dir="ltr">
<div class="gmail_default" style="font-family:tahoma,sans-serif">The
Boston Team would like to let people know that we are actively
engaged in rounding out our final documentation on lessons
learned and presenting our data in ways that will hopefully be
useful to future planning teams. There are two areas where we
have focused our efforts:</div>
<div class="gmail_default">
<ol>
<li><font face="tahoma, sans-serif">As per an earlier thread
with <b>Cameron</b>, I have forked and updated the
historic registration tracking spreadsheet that has been
contributed to since 2006. I have renamed the sheet "<a
href="https://docs.google.com/spreadsheets/d/1UzMhTia60QvWDtnZ9maGBfnaRCdj0r__Li07lG4WgIg/edit?usp=sharing"
moz-do-not-send="true"><b>FOSS4G Registration Tracking
New 2018</b></a>". More information on the changes
to this sheet, and recommendations for further
improvement are found <span
style="background-color:rgb(255,229,153)">below</span>
(as many of you are likely to find this additional info
TL;DR).</font></li>
<li><font face="tahoma, sans-serif">As per encouragement
from <b>Jeff</b>, our team has also begun to fill out
the<b> <a
href="https://wiki.osgeo.org/wiki/FOSS4G_2017_Lessons_Learned"
moz-do-not-send="true">FOSS4G 2017 Lessons Learned
page on the Wiki</a></b>. We're not done, but it's
taking shape and one of our goals is to use this page as
place to provide linkages to other materials that remain
on our website, or to Google docs that contain our data.</font></li>
</ol>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif">And
of course, we welcome direct outreach from the Dar es Salaam
and Bucharest teams if there is anything we can do to help in
a more direct way. Indeed, that's how all other teams we
reached out to treated us.<br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif">All
the best, and most sincerely,</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif">MT
& The BLOC</div>
<div>-- <br>
</div>
<div class="gmail_signature">
<div dir="ltr">
<div dir="ltr">
<div><font face="tahoma, sans-serif"><span
style="font-size:small">Michael Terner</span><br>
</font></div>
<div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif"><font size="1">FOSS4G
Boston 2017 Conference Chair</font></div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif"><font size="1">EVP
<a href="http://www.appgeo.com"
moz-do-not-send="true">AppGeo</a></font></div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif">~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</div>
</div>
<div><br>
</div>
<div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif"><span
style="background-color:rgb(255,229,153)"><font
size="4"><b>Further Info on the New Registration
Tracking Sheet</b></font></span></div>
<br>
</div>
<div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif">As per that
sidebar with Cameron, that sheet was quite old and
while chalk-full of good info it also contains a
variety of approaches to presenting the info and some
information that had not been maintained. In short,
there's a fair amount of detritus in there too. As
such, I have refactored the sheet in a way that I
think encourages consistent information gathering and
is is also a bit more scalable for collecting this
information for the long term. Here's what it looks
like and what was done:</div>
<div class="gmail_default" style="">
<ul style="">
<li style=""><font face="tahoma, sans-serif">The new
sheet opens to a new <b>summary table</b> which
presents the core data from every conference
since 2006. The data for this summary table
originates from individual spreadsheet tabs, one
for each conference.</font></li>
<li style=""><font face="tahoma, sans-serif">There <b>are
some holes in the data</b> in this table based
on the data collected by each conference team
(as presented in the original spreadsheet).
These include:</font></li>
<ul>
<li style=""><font face="tahoma, sans-serif"><b>Lausanne</b>,
not reporting on Early Bird</font></li>
<li style=""><font face="tahoma, sans-serif"><b>Nottingham
</b>and <b>Portland</b>, not reporting on
"host country" or "international"</font></li>
<li style=""><font face="tahoma, sans-serif"><b>Bonn</b>,
not yet reporting out their numbers</font></li>
</ul>
<li>Hopefully, some of those missing numbers can be
added into those tabs, and then made available
through this summary sheet. If not, now the bar is
set for future conference teams on the information
that has been most consistently gathered over
time.<br>
</li>
<li><font face="tahoma, sans-serif">I have created a
couple of <b>"example" charts</b> from the
summary table showing the potential benefits of
gathering our data in a summary fashion.</font></li>
<ul>
<li><font face="tahoma, sans-serif">I will also
note that there aren't clear trends (e.g., in
terms of the conference growing every year)
due to the rotating nature of the venue (i.e.,
the "other regions" conferences might be
better measured next to one another, rather
than next to all conferences).</font></li>
</ul>
<li><font face="tahoma, sans-serif">As you look at
the individual tabs, you will see conference
teams tracked their data in different ways,
which is fine and appropriate. The goals is to
get the same raw numbers for the summary table
to track over time, i.e., these 4 columns:</font></li>
<ul>
<li><font face="tahoma, sans-serif"><b>Total</b>
registrations</font></li>
<li><font face="tahoma, sans-serif"><b>Early bird
</b>registrations</font></li>
<li><font face="tahoma, sans-serif"><b>Host
country</b> registrations</font></li>
<li><font face="tahoma, sans-serif"><b>International
</b>registrations</font></li>
</ul>
<li><font face="tahoma, sans-serif">The tab titled <b>RegDate</b> represents
what was shared with our team via the last
formulation of the older sheet. My hope was that
I could remove that tab, as well as the other <i>18
tabs </i>to the right of it. This proved
harder than I thought as the data in RegDate was
linked to those 18 tabs; and the charts in
RegDate were linked to those data.</font></li>
<li><font face="tahoma, sans-serif">In copying the
data from RegDate to the individual tabs, I did
break the linkage to the older tabs by using
"Paste Special" for the <i>numbers.</i> But the
charts found in those tabs are still linked to
RegDate data so those older 18 tabs still
remain. Those charts could be rebuilt from the
new, "pasted special" data, but we have not done
that yet.</font></li>
<li><font face="tahoma, sans-serif">Indeed, <b>we
wanted to get others' impressions</b> on
whether the approach we're taking makes sense
and should be continued. If so, we can break the
linkage to RegDate, recreate the charts in each
tab, and move forward in this direction. And, of
course, we'll have, and keep a copy of the
RegDate sheet for posterity.</font></li>
<li><font face="tahoma, sans-serif">Last, those 18
tabs also contain valuable information on things
like sponsorship. Those data weren't collected
for every conference so full historic tracking
is still quite difficult. We would argue/propose
that other key things like <b>workshops </b>and<b>
sponsorship </b>should<b> have their own
tracking sheets</b> and that future conference
teams share their data to those sheets.</font></li>
<li><font face="tahoma, sans-serif">Toward that end,
and as you will find on the <a
href="https://wiki.osgeo.org/wiki/FOSS4G_2017_Lessons_Learned#Sponsorship"
moz-do-not-send="true">OSGeo Wiki under our
Lessons Learned in the Sponsors section</a>,
we have compiled a <b><a
href="https://docs.google.com/spreadsheets/d/1o7_J3Tmq70mgsdxrfsiL0rAi1EEojaCF1HrcWmUiydw/edit#gid=0"
moz-do-not-send="true">Sponsor Tracking
sheet</a></b> that dates back to Barcelona,
2010 and includes any sponsor that supported
either a Global FOSS4G, or a FOSS4G North
America. These data were assembled by reviewing
the archived web-sites from past conferences and
simply counting logos. If others are interested
in helping to maintain this sheet, we would be
pleased to modify the current "View Only"
sharing settings with interested parties.</font></li>
<li><font face="tahoma, sans-serif">As appropriate,
we have our<b> workshop data</b> and would be
willing to work with other previous conference
teams <b>to create a shared, workshop summary
spreadsheet of key data</b>. Indeed, in our
planning, uncovering past information on
workshops was surprisingly difficult. For
workshops, key data might include:</font></li>
<ul>
<li><font face="tahoma, sans-serif">Number of
workshops</font></li>
<li><font face="tahoma, sans-serif">Number of
workshop attendees</font></li>
<li><font face="tahoma, sans-serif">Costs for
attending workshops</font></li>
<li><font face="tahoma, sans-serif">Costs for
compensating workshop instructors (whether via
cash; or free registration)</font></li>
</ul>
</ul>
<div><font face="tahoma, sans-serif">Let us know if
you have any questions; and also what you all
think about the new formatting and data.</font></div>
<div><font face="tahoma, sans-serif"><br>
</font></div>
<div><font face="tahoma, sans-serif">MT</font></div>
<font face="tahoma, sans-serif"><br>
</font></div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif"><br>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
<br>
<span style="color:rgb(128,128,128);font-family:'Courier
New';font-size:10px;background-color:rgb(255,255,255)">This
e-mail message and any attachments may contain confidential or
legally privileged information. If you are not an intended
recipient or otherwise authorized to receive this message, you
should not use, copy, distribute, disclose or take any action
based on the information contained in this e-mail or any
attachments. If you have received this message and material in
error, please advise the sender immediately by reply e-mail and
delete this message. Thank you on behalf of Applied Geographics,
Inc. (AppGeo).</span>
</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>