<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 12 (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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.E-mailStijl20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:862934718;
mso-list-template-ids:-17926064;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1095244915;
mso-list-template-ids:504954320;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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=NL link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi all, <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>This discussion encouraged me to re-read this the 2017-RfP [1]<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The RfP says a lot about FOSS4G's history, but not much about expectations, nor about the roles (board, conf. committee, LOC, PCO) and the relationship between OSGeo and FOSS4G.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thus, the conference goals and involved organisations roles remain relatively vague, and remain open to personal interpretation (mainly based on a common sense and the ways things got organized in previous years).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>(I even get the idea that anyone can apply to organize the FOSS4G, so I wonder why a large geospatial company from the Golden State hasn't made a bid so far)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>As a comparison, one could have a look at the conference organisation guidelines of the IASA [2] and those of the OWASP [3].<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The advantage of such a general RfP is that LOCs have the freedom to bring on new ideas and goals as well as new collaborations for the organisation, in which the traditional roles (board, conf.comm. LOC, PCO) have shifted.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>On the downside, the disadvantage of a such general RfP is that the selection process is mainly a subjective matter. Requirements are not marked as knock-out criteria, nor are points rewarded per criteria (such as in a commercial tender)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I therefore wish all the conf.comm. members wisdom in their verdict ;-)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I agree with Steven that's it's worth a discussion. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>However, since the three 2017-bids are based upon an RfP that hasn't got strict guidelines or requirements on this point, it would be like changing the rules while the game is being on if this discussion is meant to judge the 3 bids.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>It is food for thought, not just for the FOSS4G-2017, but also more general for our role in the entire open and/or geospatial ecocsystem. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>regards, <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Gert-Jan<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[1] https://svn.osgeo.org/osgeo/foss4g/rfp/2017/osgeo-conference-2017-request-for-proposal.pdf<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[2] http://www.iasa-web.org/want-host-conference<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[3] https://www.owasp.org/index.php/How_to_Host_a_Conference<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-GB style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Van:</span></b><span lang=EN-GB style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Conferenc</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>e_dev [mailto:conference_dev-bounces@lists.osgeo.org] <b>Namens </b>Steven Feldman<br><b>Verzonden:</b> zondag 8 november 2015 10:05<br><b>Aan:</b> Bart van den Eijnden<br><b>CC:</b> conference<br><b>Onderwerp:</b> Re: [OSGeo-Conf] Call to discuss FOSS4G 2017 proposals prior to voting<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Bart<o:p></o:p></p></div><div id=AppleMailSignature><p class=MsoNormal><o:p> </o:p></p></div><div id=AppleMailSignature><p class=MsoNormal>PCO's don't usually fund conferences, take on the financial risks or position themselves as co-organisers with logos etc.<o:p></o:p></p></div><div id=AppleMailSignature><p class=MsoNormal><o:p> </o:p></p></div><div id=AppleMailSignature><p class=MsoNormal>As you say in the past the PCO was an invisible supplier of services to the LOC, this year it appears that may not be the case. Surely that is worth discussing?<o:p></o:p></p></div><div id=AppleMailSignature><p class=MsoNormal><br>Steven <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>On 8 Nov 2015, at 08:01, Bart van den Eijnden <<a href="mailto:bartvde@osgis.nl">bartvde@osgis.nl</a>> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>This is starting to feel like a PCO selection process instead of a FOSS4G selection process to me.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Let’s have some faith in the LOCs here as well to make the right decisions along the way. Not everything can be known in advance. I remember many years where the name of the PCO was not even known in advance.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Otherwise OSGeo should simply put in the RFP document they don’t want LocationTech as the PCO, and save all these good people their energy and time.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Best regards,<o:p></o:p></p></div><div><p class=MsoNormal>Bart<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On 08 Nov 2015, at 00:35, Steven Feldman <<a href="mailto:shfeldman@gmail.com">shfeldman@gmail.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Dave<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>You say “for the sake of clarity and transparency ...” I may be a lone voice here but I don’t fee that there is clarity or transparency about the relationship between the Ottawa and Philadelphia bids and Location Tech. Several questions and concerns have been expressed regarding branding, finances, influence, the coincidences of identical sections of text in both bids etc. From my personal perspective I do not have ‘clarity’<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><p class=MsoNormal><span class=apple-style-span><span style='font-family:"Helvetica","sans-serif"'>______</span></span><span style='font-family:"Helvetica","sans-serif"'><br><span class=apple-style-span>Steven</span><br><br><br></span><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On 7 Nov 2015, at 22:30, Dave McIlhagga <<a href="mailto:dmcilhagga@mapsherpa.com">dmcilhagga@mapsherpa.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal>After reading Michael’s summary - I realized that there are quite different perspectives on taking on the responsibility of hosting FOSS4G for OSGeo, so for the sake of clarity and transparency felt compelled to provide the perspective of the Ottawa LOC on taking this on.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>When some of our keen and active members of the Ottawa OSGeo Local Chapter approached me about participating in this event, a lot of great memories of hosting the precursor we did in 2004 came back to me, but so did the memories of the mountains of work, unexpected twists and turns, and complete underestimation we had of the job at hand. Over the years I’ve had conversations with many of the hosts of this event, who even with the assistance of an experienced PCO, and with all the energy and best intentions in the world, have been overwhelmed by the amount of work required, particularly due to some of the unique needs that come with putting on an open source geospatial event.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>With this in mind, I joined our LOC, with an eye to advising and supporting from my experience with this event. When the group asked if I would be willing to Chair — I said I would, but the condition of that was that we had to have a very strong PCO to work with, as I was well aware of what the alternative would look like in terms of impacts on our team, and our ability to pull off a world class professional event.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>At this point I approached LocationTech to see if they would be interested in acting as our PCO in our bid to OSGeo to host FOSS4G for the foundation. I had several reasons for this which I will explain below - but before this, want to share the next step of our process in selecting a PCO. In order to ensure due diligence, we invited another prominent PCO from Ottawa to offer their services so that we could compare options. The end point of this was a three way discussion among the Ottawa PCO, LocationTech and the Ottawa LOC. It was an interesting experiment in collaborative discussion on this - and the result was the other PCO we were speaking with suggested it really made most sense for us to work with LocationTech on our bid. That provided for me the reassurance that this was the right way for us to approach this.<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>For us, the advantages of this approach come down to the following:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>1. Eclipse has long experience and infrastructure specifically designed for hosting international open source events and all the uniqueness that implies. No need to re-invent the wheel for Technical Workshop sign-ups, incorporating BOFs, Sprints, and the many other elements of this event.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>2. I remember how much time Sponsorship recruitment took — something typically grossly underestimated. With LocationTech involved we get a group that already has a strong institutional membership base, and key relationships to the organizations that are likely to be sponsors for this event. That’s both a tremendous amount of work that doesn’t have to depend on volunteer time, with a far greater chance of success in securing sponsorships that financially de-risk this event.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>3. With LocationTech involved, I feel we have a much greater chance of securing higher attendance due to the direct marketing access that comes with this to the LocationTech and Eclipse community.<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>4. LocationTech has a unique motivation to make this a great event — which is advancing the open source geospatial technology movement, something that is core to their raison-d’etre, and as such, I know they would put their heart and soul into this in a way we could not expect from any other PCO. <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>Finally, I just want to re-iterate in case there is any confusion here, that we as an LOC have put this bid forward from the get-go with a goal of putting on a great OSGeo event. This is the LOCs bid to host this event, and not Eclipse. It is the LOC that will be the driver of what this whole event will look like, and the LOC will be working with OSGeo to ensure this is a great world class event reflective of OSGeo’s needs. Our choice of a PCO is because it makes the most sense to us logistically to pull this off.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>There were good questions about branding, and I think we’ve made it clear — this is the OSGeo Global FOSS4G event, that’s what we want it to be as the LOC and what we’re committed to putting on. LocationTech will have presence of course as we indicated, in a similar manner to their past participation at FOSS4G.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I’ve been involved in this personally for a long time, as one of the original founders of OSGeo and our Local Chapter, former Board Member and Treasurer, and continuing member of this conference committee. By being the chair of this event, I’m putting my reputation on the line here to put on a great show for the Foundation, it’s projects, and it’s members. I hope that can be sufficient to put any concerns about our PCO to rest.<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>Best of luck to the committee with your deliberations. You have some very good proposals and keen LOCs to choose from. No matter what, I’m sure OSGeo is going to get a great event in 2017 - we look forward to your decision.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Dave<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><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><p class=MsoNormal><o:p> </o:p></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On Nov 6, 2015, at 5:16 PM, Michael Terner <<a href="mailto:mgt@appgeo.com">mgt@appgeo.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Tahoma","sans-serif"'>Steven:<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Tahoma","sans-serif"'>Thanks for revising spreadsheet based on the input you've received. Just to address the points that Robert and David have raised vis a vis our workshop pricing and the PCO and associated costs.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Tahoma","sans-serif"'>1. YES, our workshop costs are $100/day. We believe it is important to give attendees the option of having the right number of workshops that fits their schedule (i.e., Monday <i>and </i>Tuesday; Tuesday only). That is why our workshop pricing is itemized. That said, it is a good idea to have a bundled and discounted workshop price along with the main conference and we will strongly consider that if we are chosen.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Tahoma","sans-serif"'><br>2. YES, we did not include an original, itemized line item for our PCO and our PCO was embedded in the $149K "Production" line item. Based on a question, we presented the $60K PCO price separately. Our $60K PCO price is <i>all inclusive </i>and like Philadelphia includes marketing support and other labor activities. We did our research and this pricing is comfortably consistent with successful previous global North American events. And, as shown throughout the proposal process, our full BLOC is prepared to be energetically involved in producing the conference.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Tahoma","sans-serif"'><br>Boston's PCO approach is different than both Philadelphia's and Ottawa's. We were approached by Location Tech, heard their pitch, and selected a PCO partner that did not require branding and who we felt would best reflect the BLOC's vision for the conference. We consciously gave up the underwriting that Location Tech generously offered and instead chose the formula that has worked for previous FOSS4G global conferences with OSGeo and the LOC directly partnering and sharing risks and rewards. And very importantly, we wanted some of the rewards (i.e., the 20%, or $20k of profits, whichever is smaller) to be reinvested in further building the Boston community through a new OSGeo Chapter.</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Tahoma","sans-serif"'>3. While the spreadsheet is incredibly helpful and I presume will be very valuable to the selection committee there is agreement across all three teams that it does not reflect a pure apples-to-apples comparison. Some significant things differ including:</span><o:p></o:p></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1'><span style='font-size:9.5pt;font-family:"Tahoma","sans-serif"'>The anticipated attendance in each city</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1'><span style='font-size:9.5pt;font-family:"Tahoma","sans-serif"'>The PCO approach and underwriting</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1'><span style='font-size:9.5pt;font-family:"Tahoma","sans-serif"'>The allocation approach for profits</span><o:p></o:p></li></ul></div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Tahoma","sans-serif"'>This is fine and appropriate as the proposals do reflect a variety of legitimate approaches. It just means the numbers in the spreadsheet need to be reviewed with an eye to some of the fundamental choices the committee faces, not just the numbers in the grid.</span><o:p></o:p></p><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Tahoma","sans-serif"'>Thanks again for pulling the material together and giving us an opportunity to better explain our proposals. And best of luck in your deliberations and voting.</span><o:p></o:p></p><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Tahoma","sans-serif"'>MT & the BLOC</span><span style='font-size:9.5pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p></div></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Fri, Nov 6, 2015 at 2:04 PM, Dave McIlhagga <<a href="mailto:dmcilhagga@mapsherpa.com" target="_blank">dmcilhagga@mapsherpa.com</a>> wrote:<o:p></o:p></p><div><div><p class=MsoNormal>Steven,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Some additions from Ottawa:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Room Rates - Because we are not tied into a particular hotel, and the event is right downtown - attendees would have flexibility on where to stay. Ottawa rates at the high end for that time of year would be about $175 per night, with many reasonable options available in the $100-$150 range.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I’d echo the apples-to-apples comparison issue regarding line items for PCO / Production costs — they are bundled for Philadelphia and Ottawa, de-coupled for Boston.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Workshops - same as Philadelphia<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='background:white'>Maximum capacity is 2,000+</span><br><span style='background:white'>Concurrent tracks = 10</span><br><span style='background:white'>Wifi = free</span><br><span style='background:white'>Venue conditions - none</span><br><br><br>Thanks,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Dave<o:p></o:p></p></div><div><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><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On Nov 6, 2015, at 1:01 PM, Robert Cheetham <<a href="mailto:cheetham@azavea.com" target="_blank">cheetham@azavea.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Steve,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks for pulling together a summary table. A few suggestions and some additional info for Philadelphia:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> * Maximum capacity: 2000+<o:p></o:p></p></div><div><p class=MsoNormal> * Concurrent tracks supported: 10<o:p></o:p></p></div><div><p class=MsoNormal> * free wifi: yes<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Some additional suggestions:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> * Add a row for hotel rates - affordability was a significant concern in the pre-proposal questions. Philadelphia's rate is $209<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> * "Workshops" should be "Workshops Only" and "Workshops Only EB" as the actual workshop price will likely be only $100/half day ($200 total) for anyone that attends the full conference. It's not clear from the Boston proposal, but I think $100 workshop fee is a per half day number added to the regular conference price, which suggests it should be listed as $200 added to the conference fee in the "Conf + Workshop" and "Conf + Workshop EB" lines, rather than $100 in the "Workshop Only" line, but perhaps Michael Terner can clarify.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> * In order to support an apples-to-apples comparison, the "PCO" line should probably be re-labeled "Production" or "Operations" with a line each for PCO fee and "Other Production Costs". The Eclipse Foundation included marketing efforts and other labor activities in the PCO fee, and it's not clear to me how best to compare this fee between the three bids, but the the Philadelphia and Ottawa proposals broke out the PCO fee from other operations and production costs while the Boston bid included the PCO in a $149k production costs.<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>Robert<o:p></o:p></p></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><div><div><div><p class=MsoNormal><br>------------------<o:p></o:p></p><div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Fri, Nov 6, 2015 at 10:37 AM, Steven Feldman <<a href="mailto:shfeldman@gmail.com" target="_blank">shfeldman@gmail.com</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal>Michael<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks for the clarifications and suggestions. I have updated the comparison.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Any other changes?<o:p></o:p></p><div><p class=MsoNormal><span style='font-family:"Helvetica","sans-serif"'>______<span style='color:#888888'><br>Steven<br><br><br></span></span><o:p></o:p></p></div><div><div><p class=MsoNormal><o:p> </o:p></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On 6 Nov 2015, at 03:53, Michael Terner <<a href="mailto:mgt@appgeo.com" target="_blank">mgt@appgeo.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal><span style='font-family:"Tahoma","sans-serif"'>Steven:<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Tahoma","sans-serif"'>Thanks for generating and distributing the summary. It is very helpful to see everything lined up in one place. As per your request I would like to offer the following clarification/observations to some of your data:<o:p></o:p></span></p></div><div><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2'><b><span style='font-family:"Tahoma","sans-serif"'>Code Sprint:</span></b><span style='font-family:"Tahoma","sans-serif"'> As per our proposal and subsequent Q&A response, we have identified the code sprint as a "co-located" event that we would potentially hold during the workshop days (8/14-8/15). We would like to have a co-located code sprint and will work energetically with community organizers of the event to find the right time and place.</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2'><b><span style='font-family:"Tahoma","sans-serif"'>Venue Max Capacity:</span></b><span style='font-family:"Tahoma","sans-serif"'> Our venue could potentially exceed 1,200, if needed. It would take some additional planning but we are considering attracting 1200 people an excellent goal, and it would be a "good problem" and feasible to be stretched a bit beyond that.</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2'><b><span style='font-family:"Tahoma","sans-serif"'>Venue Condition: </span></b><span style='font-family:"Tahoma","sans-serif"'>As per earlier Q&A, the 810 room block is what has been offered. Specific conditions and any potential penalties are subject to negotiation if we are awarded the conference. The current proposal we have from the hotel does <u>not</u> mention any penalties, only that this is the maximum block of rooms that is being held for the conference.</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2'><b><span style='font-family:"Tahoma","sans-serif"'>Distribution to OSGeo:</span></b><span style='font-family:"Tahoma","sans-serif"'> Yes, Boston has committed <i>at least </i>80% of net revenues to OSGeo (with the balance being used to establish/endow a Boston Chapter of OSGeo). We also capped the amount of that endowment to $20,000 so if we were to net our estimated profit of $145,000, OSGeo would receive $125,000, or 86.2%. We would respectfully suggest that your table also include the "net distribution" to OSGeo, not just the % as that may be misleading. Per the Philadelphia proposal's 1000 attendee number, even providing 90%, the total net return to OSGeo is $75,000, compared to Boston's $125,000 at the same attendance level. Even at an attendance of 850, Boston would still provide $73,900 to OSGeo. At 700 people, Boston would provide $31,860 to OSGeo, while Philadelphia estimates they would break even - i.e., no return to OSGeo - at 785 attendees (per the Q&A). Boston's net numbers also compare favorably to Ottawa's when looked at not only by %, but by the net, estimated contribution to OSGeo, although Ottawa anticipates holding a smaller conference in terms of attendees. In short, the budgetary comparison in the table is not "apples-to-apples" and we encourage the selection committee to closely review the nuanced differences in the "distribution to OSGeo" approaches and estimated outcomes.</span><o:p></o:p></li></ul><div><p class=MsoNormal><span style='font-family:"Tahoma","sans-serif"'>Thanks again for preparing this very helpful summary table and encouraging our comments/fact checking.</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Tahoma","sans-serif"'>MT</span><o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Thu, Nov 5, 2015 at 7:12 PM, Steven Feldman <<a href="mailto:shfeldman@gmail.com" target="_blank">shfeldman@gmail.com</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal>I thought it might be helpful to prepare a short summary of the bids (primarily financial).<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Bidders let me know if I have misinterpreted or have errors<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Cheers<o:p></o:p></p><div><p class=MsoNormal><span style='font-family:"Helvetica","sans-serif"'>______<span style='color:#888888'><br>Steven<br><br><br></span></span><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><br>_______________________________________________<br>Conference_dev mailing list<br><a href="mailto:Conference_dev@lists.osgeo.org" target="_blank">Conference_dev@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/conference_dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><o:p></o:p></p></div><p class=MsoNormal><br><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><p class=MsoNormal><strong><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Michael Terner</span></strong><span style='font-family:"Arial","sans-serif"'><br></span><em><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Executive Vice President</span></em><br><span style='font-size:7.0pt'><a href="tel:617-447-2468" target="_blank">617-447-2468</a> Direct | <a href="tel:617-447-2400" target="_blank">617-447-2400</a> Main</span><br><span style='font-size:7.0pt;font-family:"Arial","sans-serif"'>Applied Geographics, Inc.</span><span style='font-size:7.0pt'><br></span><span style='font-size:7.0pt;font-family:"Arial","sans-serif"'>24 School Street, Suite 500<br>Boston, MA 02108</span><span style='font-size:7.0pt'><br><a href="http://www.appgeo.com/" target="_blank"><span style='color:#009933'>www.AppGeo.com</span></a><br><strong> </strong> </span><o:p></o:p></p></div></div></div><p class=MsoNormal><br><span style='font-size:7.5pt;font-family:"Courier New";color:gray;background:white'>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><o:p></o:p></p></div></blockquote></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><br>_______________________________________________<br>Conference_dev mailing list<br><a href="mailto:Conference_dev@lists.osgeo.org" target="_blank">Conference_dev@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/conference_dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal>_______________________________________________<br>Conference_dev mailing list<br><a href="mailto:Conference_dev@lists.osgeo.org" target="_blank">Conference_dev@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/conference_dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></div><p class=MsoNormal><br>_______________________________________________<br>Conference_dev mailing list<br><a href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/conference_dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><o:p></o:p></p></div><p class=MsoNormal><br><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><p class=MsoNormal><strong><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Michael Terner</span></strong><span style='font-family:"Arial","sans-serif"'><br></span><em><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Executive Vice President</span></em><br><span style='font-size:7.0pt'>617-447-2468 Direct | 617-447-2400 Main</span><br><span style='font-size:7.0pt;font-family:"Arial","sans-serif"'>Applied Geographics, Inc.</span><span style='font-size:7.0pt'><br></span><span style='font-size:7.0pt;font-family:"Arial","sans-serif"'>24 School Street, Suite 500<br>Boston, MA 02108</span><span style='font-size:7.0pt'><br><a href="http://www.appgeo.com/" target="_blank"><span style='color:#009933'>www.AppGeo.com</span></a><br><strong> </strong> </span><o:p></o:p></p></div></div><p class=MsoNormal><br><span style='font-size:7.5pt;font-family:"Courier New";color:gray;background:white'>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><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>_______________________________________________<br>Conference_dev mailing list<br><a href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal>_______________________________________________<br>Conference_dev mailing list<br><a href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></blockquote><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>_______________________________________________<br>Conference_dev mailing list<br><a href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/conference_dev">http://lists.osgeo.org/mailman/listinfo/conference_dev</a><o:p></o:p></p></div></blockquote></div></body></html>