<html xmlns:v="urn:schemas-microsoft-com:vml" 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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1131704669;
mso-list-type:hybrid;
mso-list-template-ids:1953768056 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi Steven, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think you raise a good question, and COVID-19 has created the space to ask it. I didn’t attend FOSS4GUKOnline unfortunately, as it seems like a great success, and I think virtual events have their place in the spectrum.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I would rank them like this: <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">0: No event <o:p></o:p></p>
<p class="MsoNormal">|<o:p></o:p></p>
<p class="MsoNormal">|<o:p></o:p></p>
<p class="MsoNormal">5: Virtual Event <o:p></o:p></p>
<p class="MsoNormal">|<o:p></o:p></p>
<p class="MsoNormal">|<o:p></o:p></p>
<p class="MsoNormal">10: In-person event<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In my limited FOSS4G experience the biggest value to the event is meeting new people, creating new connections, and receiving a booster-shot of that I’m-doing-the-right-thing-with-the-right-people” feeling. Content comes second to this,
even though it’s notionally the reason that we’re all there. If I think about the FOSS4G events I’ve attended, we spent more time socializing and creating social bonds than we did in lectures or workshops. This isn’t to devalue the lectures and workshops,
as I don’t think it would work to host a purely social event either. After a few months of video-meetings, and video-calls, and video-socialization, I’m getting weary of seeing people in 2D; it’s no match for an in-person experience.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I could see evolving the model to something where you host Local/Regional/online events on the odd years, and then a global in-person FOSS4G on the even years.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There is a magic fire in the FOSS4G gatherings, and my suggestions below to the CC and OSGeo Board are meant to recognize that it’s a large global movement (with large global benefits and risks) and to feed the flames accordingly.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cheers<o:p></o:p></p>
<p class="MsoNormal">Jon <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Steven Feldman <shfeldman@gmail.com> <br>
<b>Sent:</b> Thursday, June 18, 2020 3:48 AM<br>
<b>To:</b> Jonathan Neufeld <jneufeld@tecterra.com><br>
<b>Cc:</b> Conference Dev <conference_dev@lists.osgeo.org>; osgeo-board List <board@lists.osgeo.org><br>
<b>Subject:</b> Re: [OSGeo-Conf] Lessons Learned from FOSS4G Calgary 2020 and Recommendations for the future<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jon thanks for a great summary of the questions that we need to address and for your recommendations which I largely agree with.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I would add a further question - given the challenges of accessibility, the financial risks and the environmental impact of running a >1,000 person global event should we re-evaluate our whole events programme as part of our strategy for
community building, outreach and financially sustaining OSGeo? I covered some of this in my keynote yesterday at FOSS4GUK, my slides are here <a href="https://docs.google.com/presentation/d/1VhViqXxRUQjMwc4ubVPrjE0dec31uwR12yVQBfVesc4/edit?usp=sharing">https://docs.google.com/presentation/d/1VhViqXxRUQjMwc4ubVPrjE0dec31uwR12yVQBfVesc4/edit?usp=sharing</a> (you
will need to read the speaker notes)<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I would ask the board to consider Jon’s thoughts and recommendations and provide some guidance to CC as to how you want us to proceed<o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Helvetica",sans-serif;color:black">______<br>
Steven<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif;color:black">Unusual maps in strange places - <a href="http://mappery.org">mappery.org</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Subscribe to my weekly “<a href="http://eepurl.com/dKStT-/">Maps in the Wild</a>” newsletter<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 18 Jun 2020, at 05:05, Jonathan Neufeld <<a href="mailto:jneufeld@tecterra.com">jneufeld@tecterra.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hi CC, <br>
<br>
I saw the thread on updating the RfP docs ahead of the next large FOSS event, and I figured it was a good time to share my lessons learned from FOSS4G Calgary 2020. I think that the experience with Calgary should be a strong call to action to evaluate FOSS4G
from the ground-up and look at ways that OSGeo and the community can build out a successful conference for the next decade.
<br>
<br>
========= Intro =========<br>
2020 will forever be known as the year that COVID19 changed the way that we live, work, and interact. This global pandemic has led to millions of infections, thousands of deaths, and affected every single person on the planet.
<br>
2020 was also supposed to be the year that Calgary hosted the Free and Open Source Software for Geospatial (FOSS4G) event, a global event that we subsequently canceled due to the ongoing pandemic.
<br>
<br>
In the interest of openness and transparency I am sharing with everyone the lessons I have learned along the way and my opinions on how to better the FOSS process. I want to be clear that these are my personal thoughts and opinions and may not be shared by
others on the Calgary local organizing committee (LOC). <br>
<br>
== Context: Fast facts about FOSS4G 2020 == <br>
- Planning Time: 2 years (Oct 2018 to Aug 2020)<br>
- Target Attendance: 1,200 to 1,500 people <br>
-- Break even attendance: 800 people <br>
- Total conference budget: $1M+<br>
- Actual Financial Loss: ~$62k CAD (~$48k USD) <br>
<br>
========= The growing pains of a Global FOSS4G =========<br>
I wasn’t there where FOSS4G started out, but like most things it started small. In 2002 (<a href="https://wiki.osgeo.org/wiki/FOSS4G">https://wiki.osgeo.org/wiki/FOSS4G</a>) there were 140 people gathering in Italy to discuss GRASS GIS. By 2006 it was officially
named FOSS4G and 560 people attended in Switzerland. Organizing an early FOSS4G would have taken months of work, money for venues, and lots of thought. The events were grassroots and probably felt like you were getting together with your close friends for
a few days of conversation. <br>
<br>
By contrast, the 2020 Calgary LOC started planning 2 years in advance, with a budget over $1M, and a target of 1,500 attendees from around the world.
<br>
As a co-chair for the 2020 conference I feel that the bidding and engagement process is still rooted in the idea that this a small, grassroots event that can be done off the side of one’s desk.
<br>
<br>
The reality is that FOSS4G has now reached the point where it is a major yearly global event that comes with a planning cycle >1 year. This means it also comes with a major budget, cash flow management challenges, and major risks.
<br>
<br>
== Recommendation: ===<br>
- OSGeo should recognize that FOSS4G is a major global event and update the thinking, processes, and treatment of it to match.
<br>
<br>
========= Long Term Thinking vs Build-and-burn =========<br>
Each year FOSS4G is hosted by a new LOC, in a new location. The upside of this is that the community can engage new people, including people who would not have the means or opportunity to travel internationally.
<br>
<br>
The downside is that each year a new LOC must build a FOSS4G from the ground up. I can’t name any other global event with 1,000+ attendees that starts over each year. By starting over, we lose knowledge, relationships, and the long-term vision for FOSS4G.
<br>
Building new relationships with potential sponsors each year means that neither the sponsor, nor the LOC, can get the best deal. Since regional FOSS4G events are also running each year we all end up competing for limited sponsor dollars. If there was coordination
and planning, then the regional and global events could work together to build better packages for sponsors and approach with one ask instead of multiple. With long-term thinking perhaps sponsors may be interested in long-term agreements to sponsor a range
of events or activities with clear goals and benefits. <br>
<br>
This lack of continuity means that there is no long-term vision or strategy for FOSS4G, and LOCs can effectively build an event to their own parameters or choosing. If unchecked FOSS4G could drift radically from the intentions of the community, and risk ruining
the reputation of this successful and long-running event. <br>
<br>
As I understand it, the main source of funding for OSGeo is some portion of the profits from FOSS4G which are donated by the LOC back to OSGeo. This assumes that the LOC a) chooses to make a profit on their event, and b) is able to make a profit on their event.
Sponsor relationships are delicate and need to be maintained over time so that both parties can benefit. The Calgary LOC needed to raise $271,000 in sponsorship to host a successful FOSS4G. This is substantial amount of money to ask for, especially when you
need to build these relationships from the ground up, and we were fortunate that many sponsors were willing to come on board (and as a show of good faith we are fully refunding them). Fundraising is a time consuming effort and could be greatly improved if
these relationships were maintained by one or two individuals year to year. <br>
<br>
== Recommendations: ==<br>
-<span class="apple-tab-span"> </span>OSGeo needs a clear long-term vision for FOSS4G, and should expect each year’s event to build on this vision
<br>
-<span class="apple-tab-span"> </span>OSGeo should employ a part- or full-time person to work with LOCs for all regional and larger events. This person would hold the vision, maintain sponsor relationships, and provide continuity on learnings from
year to year <br>
<br>
========= Conference Bidding: A Game of Contradictory Desires =========<br>
The bidding process to host a FOSS4G comes with opposing pressures to:<br>
1. Keep ticket prices as low as possible, boosting the openness and accessibility of the event
<br>
2. Make as much profit as possible, boosting the amount returned to OSGeo <br>
<br>
OSGeo and the community need to decide which priority is the most important. Does OSGeo want an event that maximizes accessibility, or profit? Neither is a wrong choice, however each choice will lead to a different type of event. LOCs can’t be expected to win
the bid on low price, and then return a huge profit to OSGeo. From past conversations on the conf_dev list I would suggest that profitability is a higher interest than many people would be willing to admit, especially if OSGeo depends on the surplus each year
to fund operations. <br>
<br>
== Recommendation: ==<br>
- OSGeo should have a clear priority or target for balancing profits and accessibility
<br>
<br>
<br>
========= On Risk and Expectations =========<br>
Winning the right to host FOSS4G comes with a “gentleman’s agreement” handshake deal of implied benefits and conditions. The benefits are that you are the one and only group hosting the global event, that you have the support of the community, and the ability
to access seed funding through OSGeo. The conditions are that you need to donate some percentage of the profits (if any) back to OSGeo at the conclusion of the event, and that you hold most of the risk.
<br>
The primary risks when hosting a conference are the contracts with the venue, the hotels, and other vendors and suppliers. Many of these agreements have minimum amounts that rachet up as you approach the event, and canceling an event <6 months out means that
the minimums add up to over $250k+<br>
<br>
The challenge with all of these benefits and conditions is that none of this is codified in a written agreement.
<br>
<br>
== Recommendation: == <br>
- OSGeo needs to create a written agreement between themselves and the winning LOC that clearly outlines the sharing of profit and risk
<br>
- OSGeo needs to recognize that LOCs are taking on major financial risks to host these events, and these risks will grow as the event grows
<br>
<br>
========= Centralization vs Decentralized =========<br>
I recognize that these recommendations create tension between a centralized and decentralized approach. This may be uncomfortable for some readers as the decentralized approach has been the standard way. In these recommendations I am suggesting that OSGeo and
the community could benefit by centralizing the core and critical aspects of FOSS4G so that each year's event would not need to start from the ground up. This does not mean elimination of LOCs or engaging the wider community in building a shared experience,
indeed, being able to access a large community of engaged participants is a strength.
<br>
<br>
<br>
========= Conclusion =========<br>
I am grateful to the FOSS4G community, and to the past FOSS4G Chairs for the wisdom, knowledge, and help that they provided along the way. I am obviously disappointed and frustrated that we cannot host the event we have been working on for the past two years,
and I am sad that we will not be able to have the wonderful FOSS4G community here in Calgary.
<br>
<br>
Through this experience I have met incredible people, learned a few hard lessons, and remain an enthusiastic supporter of open geospatial technology. I hope that OSGeo and the entire community can learn from our experience and make the necessary changes to
strengthen and improve future FOSS4G events. <br>
<br>
I also want to thank and recognize the OSGeo Board for reimbursing the Calgary LOC for 95% of the financial losses we incurred. This is a tremendous show of support during a difficult and unpredictable time, and I very much appreciate it.
<br>
<br>
Thanks,<br>
Jon<br>
<br>
========= TL;DR =========<br>
FOSS4G has evolved from a grassroots get together into a major international event and it's time to evolve the thinking about FOSS4G.
<br>
It would benefit the community to increase continuity between events and move away from a build-and-burn mentality
<br>
<br>
<br>
========= Summary of Recommendations =========<br>
All my recommendations in one place <br>
Recommendation: <br>
- OSGeo should recognize that FOSS4G is a major global event and update the thinking, processes, and treatment of it to match.
<br>
- OSGeo needs a clear long-term vision for FOSS4G, and should expect each year’s event to build on this vision
<br>
- OSGeo should employ a part- or full-time person to work with LOCs for all regional and larger events. This person would hold the vision, maintain sponsor relationships, and provide continuity on learnings from year to year
<br>
- OSGeo should have a clear priority or target for balancing profits and accessibility
<br>
- OSGeo needs to create a written agreement between themselves and the winning LOC that clearly outlines the sharing of profit and risk
<br>
- OSGeo needs to recognize that LOCs are taking on major financial risks to host these events, and these risks will grow as the event grows
<br>
<br>
_______________________________________________<br>
Conference_dev mailing list<br>
<a href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/conference_dev">https://lists.osgeo.org/mailman/listinfo/conference_dev</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>